Page Comparison

...

• Read: Grants read access to Spaces and all their Configuration Areas except for the Confidential Configuration Areas.

• Read Confidential: Grants read access to Confidential Configuration Areas.

• Create, Modify, Disable: Automatically created for each Component Unit or Configuration Type. Users must possess scoped roles with appropriate permissions to perform these actions.

• Maintain: Includes create, modify, and disable permissions.

• Modify: Grants permission for modification only.

• Delete: Grants permission for deletion only.

• Administrative Permissions: These permissions can only be assigned to a space via a role and include tasks such as maintaining roles, the type system, configuration areas, storage locations, Single Sign-On (SSO) configuration, and Master Data.

...

Access to content within Smartfacts CDCM is determined by the permissions assigned to users:

• Read Access: Users with a role that has the "Read" permissions to at least one Configuration Area permission for a space have read access to all Configuration Areas within the Space, except those marked as "Confidential." non-confidential configuration areas in that space, including all the content of those configuration areas.

• Confidential Access: For "Read" access to a Confidential confidential Configuration Area, users need a role explicitly granting with a "Read Confidential" permissions" permission for that confidential configuration area.

Write Permissions

When a new component unit or configuration type is created in Smartfacts CDCM, Create, Modify, and Disable Delete permissions are automatically generated for that type with the following pattern: <conceptTypeName>Maintain, <conceptTypeName>Modify, <conceptTypeName>Delete. This streamlines the process of managing access rights and ensures consistency across the system. Here's how it works:

• Automatic Permissions: Upon creation of a new component unit or configuration type, the system automatically generates Create, ModifyMaintain, and Disable Delete permissions specifically tailored to that type.

• Scoped Role Requirement: In order for users to perform actions such as creating, modifying, or disabling components deleting units or configurations of a certain type, they must possess a scoped role that grants the necessary permissions.

• Permission Inheritance: Configuration items inherit permissions from the configurations to which they are assigned. This ensures that access rights cascade down appropriately within the hierarchy.

...

• Inherited Permissions: Configuration items inherit permissions from the configurations to which they are associated. This means that the access rights granted to configurations are automatically extended to their associated configuration items.

• Consistency and Efficiency: By inheriting permissions, configuration items maintain consistency with their parent configurations, streamlining the management of access rights and ensuring efficiency in permission management.

Image Removed

Authorization Process

The authorization process in Smartfacts CDCM involves authentication via a central authentication provider, such as Azure AD. Here's how it works:

• Authentication: Users are authenticated via a central authentication provider, such as Azure AD.

• Token: When accessing CDCM, users carry a token containing tuples or triples defining which roles they own in which scope (spaces or configuration areas).

• Role Assignment: The assignment of roles to users is handled outside of Smartfacts CDCM, with support for authorization providers like Azure AD.

So in order to give a user certain permissions these permissions have to be added to a role in CDCM and the token coming from the identity provider has to be configured with the correct scope and the role key for that role (see image below). This page describes the customization options for the token from the identity provider.

...

Managing Roles & Permissions

To configure Roles and Permissions in Smartfacts CDCM, follow these steps:

1. Navigate to Admin Area: Access the admin area of Smartfacts CDCM. (Cogwheel icon at the bottom left in the side menu)

2. Select Roles & Permissions

3. Choose an action

   1. Add a new role by clicking on the + Add Role button at the top right

   2. Edit a roles permission by selecting a role from the list

      1. Assign a permission by clicking on the + button in the list of unassigned permissions

      2. Unassign a permission by clicking on the - button in the list of assigned permissions

      3. Permissions can be filtered by access type, unit type and permission type

Example of a Configuration

The following examples of scoped roles include the token provided by the identitiy provider (=IDP). These examples where done with the default settings for Authorization Customization. For example the separator for the different parts of the token can be changed from the default which is a singe .

Give the user a bare minimum role

Create a role which has the permission Space - Read assigned to it. In this example the space has the key spaceOne and the role has the key bm:

...

Go to the IDP and add the attribute

On log-in the user receives the role “Bare Minimum” in the scope of the space with the key “spaceOne” and is now able to read that space and all containing non-confidential configuration areas.

Assign a role to a user for all configuration areas within a space

Create a role which has certain permissions assigned to it. In this example the space has the key spaceOne and the role has the key user:

...

Go to the IDP and add the attribute

On log-in the user receives the role role “user” (last part of the token value) in the space with the key “spaceOne” (first part of the token value) in all non confidential configuration area (wildcard * in the second part of the token)

Assign a role to a user for a specific configuration area

Create a role which has certain permissions assigned to it. In this example the space has the key spaceOne the configuration area has the key caOne and the role has the key ca-admin:

...

Go to the IDP and add the attribute

On log-in the user receives the role role “user” (last part of the token value) in the space with the key “spaceOne” (first part of the token value) in the configuration area with the key caOne (second part of the token value)

Conclusion

Managing scopes, roles, and permissions in Smartfacts CDCM is crucial for maintaining proper access control and security within the configuration management system. By defining roles within specific scopes and assigning appropriate permissions, organizations can ensure that users have the necessary access to perform their tasks effectively while maintaining data security. For detailed instructions on managing roles and permissions, refer to the administration documentation or contact support for assistance.