Identity Provisioning Service(IPS)-Assigning Custom Attributes to IAS Users with Transformation Expr

IPS Transformation Expression for Custom Attributes

To assign custom attributes during provisioning, IPS uses transformation expressions in the target system configuration(Identity Authentication). Here’s an example of how to assign customAttribute1:

{
“constant”: “Germany”,
“optional”: true,
“targetPath”: “$[‘urn:sap:cloud:scim:schemas:extension:custom:2.0:User’][‘attributes’][0][‘value’]”
},
{
“constant”: “customAttribute1”,
“targetPath”: “$[‘urn:sap:cloud:scim:schemas:extension:custom:2.0:User’][‘attributes’][0][‘name’]”
}

Explanation:

constant: The value to be assigned. This can be dynamic (e.g., from source attributes) or static.targetPath: The JSON path in the SCIM schema where the value should be placed.optional: Indicates whether the attribute is optional.

The attributes array index ([0] in this case) corresponds to the position of the custom attribute. For example:

attributes[0] → customAttribute1attributes[1] → customAttribute2…attributes[9] → customAttribute10

Assigning Multiple Custom Attributes

To assign up to 10 custom attributes, repeat the transformation block with the appropriate index and attribute name. Here’s a template for assigning customAttribute2:

Repeat this pattern for attributes 3 through 10.

{
“constant”: “customAttribute2”,
“optional”: true,
“targetPath”: “$[‘urn:sap:cloud:scim:schemas:extension:custom:2.0:User’][‘attributes’][1][‘value’]”
},
{
“constant”: “customAttribute2”,
“targetPath”: “$[‘urn:sap:cloud:scim:schemas:extension:custom:2.0:User’][‘attributes’][1][‘name’]”
}

📌SAC Teams Mapping

The first five customAttributes (customAttribute1 to customAttribute5) are typically reserved for SAC Teams mapping. Ensure these are populated correctly to enable seamless integration with SAC.

Best Practices

Use meaningful names for custom attributes to maintain clarity.Validate the transformation expressions in IPS before deploying.Document the attribute usage to avoid conflicts across systems.Test provisioning flows with sample users to ensure correct attribute mapping.

Conclusion

Using IPS transformation expressions to assign customAttributes to IAS users provides a scalable and flexible way to enrich user profiles. Whether for SAC integration or other custom use cases, this approach ensures your identity provisioning is both robust and adaptable.

This blog explores how to assign up to 10 customAttributes to IAS users, with the first 5 reserved for SAP Analytics Cloud (SAC) Teams mapping, and how to configure this using IPS transformation expressions.IPS Transformation Expression for Custom AttributesTo assign custom attributes during provisioning, IPS uses transformation expressions in the target system configuration(Identity Authentication). Here’s an example of how to assign customAttribute1:{
“constant”: “Germany”,
“optional”: true,
“targetPath”: “$[‘urn:sap:cloud:scim:schemas:extension:custom:2.0:User’][‘attributes’][0][‘value’]”
},
{
“constant”: “customAttribute1”,
“targetPath”: “$[‘urn:sap:cloud:scim:schemas:extension:custom:2.0:User’][‘attributes’][0][‘name’]”
}Explanation:constant: The value to be assigned. This can be dynamic (e.g., from source attributes) or static.targetPath: The JSON path in the SCIM schema where the value should be placed.optional: Indicates whether the attribute is optional.The attributes array index ([0] in this case) corresponds to the position of the custom attribute. For example:attributes[0] → customAttribute1attributes[1] → customAttribute2…attributes[9] → customAttribute10Assigning Multiple Custom AttributesTo assign up to 10 custom attributes, repeat the transformation block with the appropriate index and attribute name. Here’s a template for assigning customAttribute2:Repeat this pattern for attributes 3 through 10.{
“constant”: “customAttribute2”,
“optional”: true,
“targetPath”: “$[‘urn:sap:cloud:scim:schemas:extension:custom:2.0:User’][‘attributes’][1][‘value’]”
},
{
“constant”: “customAttribute2”,
“targetPath”: “$[‘urn:sap:cloud:scim:schemas:extension:custom:2.0:User’][‘attributes’][1][‘name’]”
}📌SAC Teams MappingThe first five customAttributes (customAttribute1 to customAttribute5) are typically reserved for SAC Teams mapping. Ensure these are populated correctly to enable seamless integration with SAC.Best PracticesUse meaningful names for custom attributes to maintain clarity.Validate the transformation expressions in IPS before deploying.Document the attribute usage to avoid conflicts across systems.Test provisioning flows with sample users to ensure correct attribute mapping.ConclusionUsing IPS transformation expressions to assign customAttributes to IAS users provides a scalable and flexible way to enrich user profiles. Whether for SAC integration or other custom use cases, this approach ensures your identity provisioning is both robust and adaptable. Read More Technology Blog Posts by SAP articles