Merge branch 'development' into kv-react-client

Author: Karuna-Mendix

content/en/docs/apidocs-mxsdk/apidocs/studio-pro-11/pluggable-widgets/pluggable-widgets-client-apis/_index.md

@@ -516,7 +516,7 @@ interface FormatValueConfig {
 }
 ```
 
-For the reference of the API, you can refer to the [API documentation](/apidocs-mxsdk/apidocs/pluggable-widgets-client-apis-parser/).
+For the reference of the API, you can refer to the [API documentation](https://apidocs.rnd.mendix.com/11/client-mx-api/module-mx-api_parser.html).
 
 ### Icon {#icon}
 

content/en/docs/developerportal/project-management/jira-connector.md

@@ -23,7 +23,7 @@ If you are a Scrum Master of a Mendix app, you can link your app to Jira if you
     * For a team-managed board, the **Stories** pane shows all stories from your board, which may include your backlog. If you do not wish to see backlog stories in Studio Pro, consider setting up your board without a backlog, and using a separate board to manage your backlog.
 
 * Allows you to change the status of a story or mark a task as **Done** from the [Stories pane](/refguide/stories-pane/) in Studio Pro.
-* Converting your [feedback items](/developerportal/app-insights/feedback/) in App Insights will result in a story in Jira.
+* Converting your [feedback items](/developerportal/app-insights/feedback/) in App Insights results in a story in Jira.
 
 ## Limitations
 
@@ -32,15 +32,16 @@ As we further develop this feature, we may lift these limitations with future re
 {{% /alert %}}
 
 * Feedback issues, and stories from Epics are not migrated to Jira.
-* When a feedback item is being converted to an issue, the story type, title, and description of the issue will be set. If your Jira configuration requires additional mandatory fields, this process might not work.
+* When a feedback item is being converted to an issue, the story type, title, and description of the issue are set. If your Jira configuration requires additional mandatory fields, this process might not work.
 
 ## Prerequisites
 
 * You need to have the [Scrum Master](/developerportal/general/app-roles/#team-roles) role for the app.
 * You need to have an active subscription to Jira Software Cloud.
+      {{% alert color="info" %}} Local or on-premises installations are not supported.{{% /alert %}}
 * You need to have a project in Jira with a Scrum board, a Kanban board, or a team-managed board.
-* You need to have a user account and API token with administration rights to the project in Jira. For more information on how to get this API token, see [Manage API tokens for your Atlassian account](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).
-* To convert feedback items to stories in Jira, your project in Jira must have the issue types "Story" and "Bug". For more information on how to set up issue types for your project, see [Associate issue types with projects](https://support.atlassian.com/jira-cloud-administration/docs/associate-issue-types-with-projects/).
+* You need to have a user account and API token with administration rights to the project in Jira. For more information on how to get this API token, refer to [Manage API tokens for your Atlassian account](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).
+* To convert feedback items to stories in Jira, your project in Jira must have the issue types **Story** and **Bug**. For more information on how to set up issue types for your project, refer to [Associate issue types with projects](https://support.atlassian.com/jira-cloud-administration/docs/associate-issue-types-with-projects/).
 
 ## Procedure
 
@@ -55,10 +56,10 @@ To connect your app to Jira, perform the following steps:
 4. Click **Connect Jira**. The **Set Up Jira Configuration** dialog box opens.    
    Fill in the information as follows:
 
-    * **URL Jira Environment**: This is the URL of your company’s environment within the Jira platform, as provided by Jira. This URL usually looks like this: `https://my-company.atlassian.net`.
-    * **Project Key**: This is the unique key of your project within the Jira platform.
-    * **Admin User**: This is the login name of a user on the Jira platform with project administration rights.
-    * **API Token**: This is a valid API token issued by the Jira platform and assigned to the above-mentioned admin user. For more information on how to get this API token, see [Manage API tokens for your Atlassian account](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).
+    * **URL Jira Environment** – This is the URL of your company’s environment within the Jira platform, as provided by Jira. This URL usually looks like this: `https://my-company.atlassian.net`.
+    * **Project Key** – This is the unique key of your project within the Jira platform.
+    * **Admin User** – This is the login name of a user on the Jira platform with project administration rights.
+    * **API Token** – This is a valid API token issued by the Jira platform and assigned to the above-mentioned admin user. For more information on how to get this API token, refer to [Manage API tokens for your Atlassian account](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).
 
 5. Click **Next**. 
 
@@ -72,7 +73,7 @@ Once the activation is completed, your app is connected to Jira. You can see the
 
     * If you connect your app to a Scrum board in Jira, the **Stories** pane shows all stories from all your active Sprints.
     * If you connect your app to a Kanban board, the **Stories** pane shows all stories from your board, taking the filter and sub-query of the board settings into account, ordered by story key.
-        * You can find the filters and sub-query in the board settings in Jira (for more information, see [Configure a company-managed board](https://support.atlassian.com/jira-software-cloud/docs/configure-a-company-managed-board/)).
+        * You can find the filters and sub-query in the board settings in Jira. For more information, refer to [Configure a company-managed board](https://support.atlassian.com/jira-software-cloud/docs/configure-a-company-managed-board/)).
     * If you connect your app to a team-managed board, the **Stories** pane shows all stories from your board, which may include your backlog.
     * If you do not wish to see backlog stories in Studio Pro, consider setting up your board without a backlog, and using a separate board to manage your backlog.
     * The list of stories is ordered by the Jira story key.
@@ -90,6 +91,6 @@ After you activated the Jira connector, you can review the configuration details
 
 If you need to connect to a different Jira environment, or need to rotate the API key used by the Jira connector, click **Edit Connection Details**. If you want to switch to a different Jira board within the same environment, click **Change Board**.
 
-In order for the Jira connector to work, Mendix caches some information from your Jira board in our system. This include the name of the estimation field that you use to set story points, as well as the status schema that you use in your board. If this information changes in Jira, you may need to refresh the cache by clicking **Reconnect**.
+In order for the Jira connector to work, Mendix caches some information from your Jira board in our system. This includes the name of the estimation field that you use to set story points, as well as the status schema that you use in your board. If this information changes in Jira, you may need to refresh the cache by clicking **Reconnect**.
 
-If you no longer wish to use the Jira connector, simply click **Deactivate Connection**. This will revert your project management tool automatically to [Epics](/developerportal/project-management/epics/).
+If you no longer wish to use the Jira connector, simply click **Deactivate Connection**. This reverts your project management tool automatically to [Epics](/developerportal/project-management/epics/).

content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac01.md

@@ -38,7 +38,7 @@ The organizational risk management strategy is a key factor in establishing poli
 
 The following controls are related to this control:
 
-* PM-9.
+* PM-09
 
 For more information, refer to the NIST Special Publications 800-12 and 800-100.
 

content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac02.md

@@ -44,7 +44,7 @@ The organization:
 
 ### Supplemental Guidance
 
- Information system account types include the following:
+Information system account types include the following:
 
 * Individual
 * Shared
@@ -73,27 +73,27 @@ The organization:
 
  The following controls are related to this control:
 
-* AC-3
-* AC-4
-* AC-5
-* AC-6
+* [AC-03](/private-mendix-platform/nist-controls/ac-03/)
+* AC-04
+* AC-05
+* AC-06
 * AC-10
 * AC-17
 * AC-19
 * AC-20
-* AU-9
-* IA-2
-* IA-4
-* IA-5
-* IA-8
-* CM-5
-* CM-6
-* CM-11
-* MA-3
-* MA-4
-* MA-5
-* PL-4
-* SC-13.
+* AU-09
+* IA-02
+* IA-04
+* IA-05
+* IA-08
+* CM-05
+* CM-06
+* CM-011
+* MA-03
+* MA-04
+* MA-05
+* PL-04
+* SC-13
 
 ## Responsibility
 

content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0202.md

@@ -0,0 +1,42 @@
+---
+title: "AC-02 (02) Account Management - Removal Of Temporary / Emergency Accounts"
+linktitle: "AC-02 (02)"
+url: /private-mendix-platform/nist-controls/ac-0202/
+description: "Documents the Private Mendix Platform's compliance with the AC-02 (02) control of the NIST 800-53 framework."
+weight: 20
+---
+
+## Introduction
+
+This document describes how Private Mendix Platform fulfills the AC-02 (02) control.
+
+| Control ID | AC-02 (02) |
+| --- | --- |
+| Control category | AC - Access Control |
+| Requirement baseline | FEDRAMP MODERATE |
+| Responsibility and ownership | Customer - Org |
+
+## Control
+
+The information system automatically removes or; disables temporary and emergency accounts after an: organization-defined time period for each type of account.
+
+### Supplemental Guidance
+
+This control enhancement requires the removal of both temporary and emergency accounts automatically after a predefined period of time has elapsed, rather than at the convenience of the systems administrator.
+
+## Responsibility
+
+### Customer Responsibility
+
+Private Mendix Platform does not provision temporary or emergency accounts outside of normal pre-provisioning and login (SSO) mechanisms.
+
+## Guidance
+
+### Customer Responsibility
+
+To effectively manage temporary and emergency accounts, organizations should:
+
+* Define specific time limits for each type of account based on operational needs and security requirements.
+* Configure the information system to automatically disable or remove these accounts once the defined period expires.
+* Regularly review account activity and ensure that no temporary or emergency account remains active beyond its authorized timeframe.
+* Document the procedures for account creation, monitoring, and removal to ensure compliance and accountability.

content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac0207.md

@@ -0,0 +1,71 @@
+---
+title: "AC-02 (07) Account Management - Role-Based Schemes"
+linktitle: "AC-02 (07)"
+url: /private-mendix-platform/nist-controls/ac-0207/
+description: "Documents the Private Mendix Platform's compliance with the AC-02 (07) control of the NIST 800-53 framework."
+weight: 20
+---
+
+## Introduction
+
+This document describes how Private Mendix Platform fulfills the AC-02 (07) control.
+
+| Control ID | AC-02 (07) |
+| --- | --- |
+| Control category | AC - Access Control |
+| Requirement baseline | FEDRAMP MODERATE |
+| Responsibility and ownership | Customer - Org |
+
+## Control
+
+The organization:
+
+* Establishes and administers privileged user accounts in accordance with a role-based access scheme that organizes allowed information system access and privileges into roles.
+* Monitors privileged role assignments.
+* Takes organization-defined actions when privileged role assignments are no longer appropriate.
+
+### Supplemental Guidance
+
+Privileged roles are organization-defined roles assigned to individuals that allow those individuals to perform certain security-relevant functions that ordinary users are not authorized to perform. These privileged roles include, for example, key management, account management, network and system administration, database administration, and web administration.
+
+## Responsibility
+
+### Customer Responsibility
+
+Customers are responsible for defining and documenting their organization-specific privileged roles in alignment with job functions and the principle of least privilege, establishing formal processes for requesting, approving, and provisioning privileged access within Private Mendix Platform. They must conduct periodic access reviews to ensure role assignments remain appropriate, and supplement the platform's built-in monitoring audit logging  tools to capture a complete trail of privileged role changes. 
+
+Additionally, customers are responsible for defining and enforcing actions when privileged access is no longer appropriate — including integrating role revocation with Identity Provider (IdP) workflows to ensure timely de-provisioning upon employee offboarding or role changes, and establishing internal SLAs to govern the timeliness of such actions.
+
+## Guidance
+
+### Customer Responsibility
+
+Privileged access to Private Mendix Platform is controlled through Role-Based Access Control (RBAC) that is driven by the customer's Identity Provider (IdP):
+
+#### Authentication
+
+Users authenticate through the customer's IdP (for example, Azure AD, Entra ID, or other SAML 2.0 or OIDC-compliant provider). The platform does not maintain independent credential stores for end users.
+
+#### Role Assignment through IdP Claims or Groups
+
+The customer's IdP asserts group memberships or role claims during authentication. These IdP groups or claims are mapped to corresponding Private Mendix Platform roles. This ensures that the customer retains centralized control over who holds privileged roles. 
+
+#### Access Enforcement
+
+Upon authentication, the platform evaluates the user's IdP-asserted roles and grants or denies access to privileged actions accordingly. Users without the required privileged role mapping cannot access or execute privileged functions.
+
+#### Lifecycle Management
+
+When a user's group membership or role claim is modified or removed in the customer's IdP, their privileged access within Private Mendix Platform and Mendix applications is updated at the next authentication event. This ensures that privilege revocation is handled centrally through the IdP.
+
+## Proof and Remarks
+
+For more information on how Private Mendix Platform manages dynamic roles and groups, see [Dynamic Role Management in Private Mendix Platform](/private-mendix-platform/dynamic-role-management/#role-editing).
+
+{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0207-1.png" class="no-border" >}}
+
+{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0207-2.png" class="no-border" >}}
+
+{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0207-3.png" class="no-border" >}}
+
+{{< figure src="/attachments/private-platform/nist-ac/nist-ac-0207-4.png" class="no-border" >}}

content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac05.md

@@ -34,7 +34,7 @@ Separation of duties addresses the potential for abuse of authorized privileges
 
 The following controls are related to this control:
 
-* AC-3
+* [AC-03](/private-mendix-platform/nist-controls/ac-03/)
 * AC-6
 * PE-3
 * PE-4

content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac17.md

@@ -34,7 +34,7 @@ Remote access controls apply to information systems other than public web server
 The following controls are related to this control:
 
 * AC-2
-* AC-3
+* [AC-03](/private-mendix-platform/nist-controls/ac-03/)
 * AC-18
 * AC-19
 * AC-20

content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac18.md

@@ -30,7 +30,7 @@ Wireless technologies include, for example, microwave, packet radio (UHF/VHF), 8
 The following controls are related to this control:
 
 * AC-2
-* AC-3
+* [AC-03](/private-mendix-platform/nist-controls/ac-03/)
 * AC-17
 * AC-19
 * CA-3

content/en/docs/private-platform/nist-controls/ac/pmp-nist-ac19.md

@@ -51,7 +51,7 @@ Organizations are cautioned that the need to provide adequate security for mobil
 
 The following controls are related to this control:
 
-* AC-3
+* [AC-03](/private-mendix-platform/nist-controls/ac-03/)
 * AC-7
 * AC-18
 * AC-20