Additional Information

Extended Explanation of the *.user.roles.overwrite Properties

Job Logs

You have a target or a proxy system of one of the following types:

  • SAP S/4HANA Cloud Public Edition

  • SAP Marketing Cloud

  • SAP Market Communication for Utilities

  • SAP BTP ABAP Environment

  • SAP SAP Integrated Business Planning Cloud

You want to know the correct way to preserve or overwrite user roles on your target or proxy system. Thus, you need to know how to use the relevant *.user.roles.overwrite properties, and whether or not to make additional changes in your transformations.

Scenarios

  1. You want to keep existing user assignments (roles) on the target system

    Meaning:

    During the provisioning, you want to keep existing roles assigned to users on the target system, and add new assignments, if any . That means:
    • Keeping user assignments (roles) that exist only on the target system

    • Keeping user assignments (roles) that exist on both the source and the target system

    • Assigning new roles, which are read from the source system (if any), to users on the target system

    What do you need to do?
    1. Set the relevant *.user.roles.overwrite property to false.

    2. Make sure you have the following mapping in the "user" object of your target/proxy write transformation:

    3. Remove the whole "group" object from your target transformation. That is:

  2. You want to overwrite existing user assignments (roles) on the target system

    Meaning:

    During the provisioning, you want to unassign roles assigned to users on the target system, and assign only roles read from the source system. That means:
    • Unassigning all user assignments (roles) that are assigned to the user on the target system (unassigning roles which exist on both source and target system, as well as roles existing only on the target system)

    • Assigning user assignments (roles) read from the source system to the user on the target system

    What do you need to do?

    1. Set the relevant *.user.roles.overwrite property to true.

    2. Make sure you have the following mapping in the "user" object of your target/proxy write transformation:

    3. Remove the whole "group" object from your target transformation. That is:

  3. You want to update groups, read from the source system, and their assignments (users) on the target system

    Meaning:

    During the provisioning, you want to update groups, read from the source system, and their assignments on the target system. That means:
    • Updating groups, read from the source system, and their assignments (users) on the target system

    • Groups that are not read from the source system (existing only on the target system) and their assignments will not be updated on the target system

      What do you need to do?
      1. Set the relevant *.user.roles.overwrite property to false.

      2. Delete the following mapping in the "user" object from your target/proxy write transformation:

      3. Add the following "group" object to your target transformation.

Negative Condition Statements in Transformations (Examples)

Problem

You want to use negations ("not" conditions) in the transformations of your provisioning systems but you struggle with finding the right way to do it.

Take a look at the examples below - they represent the most frequently used negations, according or regardless of the system type.

Examples

Negative Condition

Meaning

"condition": "$.userName != 'John Smith'"

"If the user name is not John Smith, then..."

"condition": "%s4hana.cloud.hr.switch.active% != null && %s4hana.cloud.hr.switch.active% == true",

"If the s4hana.cloud.hr.switch.active property is set, and its value is TRUE (which means HR integration is enabled), then ..."

"condition": "('${nestedPathVariable}' != '')",

"If the transformation variable <nestedPathVariable> does not have an empty value, then ..."

"condition": "('%ldap.attribute.user.id%' != '%ldap.attribute.dn%')",

"If the system property ldap.attribute.user.id does not have the same value as the system property ldap.attribute.dn, then ..."

"condition": "$.emails[?(@.type != 'work')].value != []",

"If the values of emails of type different than 'work' are different than empty array, then ..."

SAP S/4HANA Based Systems: Business Role Description

Scenario

You have a source or a proxy system of the following types:
  • SAP S/4HANA Cloud Public Edition

  • SAP Marketing Cloud

  • SAP BTP, ABAP Environment

  • SAP Integrated Business Planning Cloud

By default, Identity Provisioning reads group ID (= Business Role ID) and members (= Assigned Business Users).

Now, the service can also read group descriptions (= Business Role Description). To learn how to do this, see the Solution section below.

All this group information can be provisioned to a target system, or read by a consuming application (like SAP Identity Management) in proxy scenarios.

Solution

To make Identity Provisioning read the descriptions of groups (roles), you need to add the following mapping in the "group" resource of your source/proxy system:

Therefore, if you place it for example after the ID mapping, your "group" resource should look like this: