Storage and Maintenance of Attribute Mapping in Transformations

[jaksweyn]

From the examples I have seen with SAP IPS, I noticed that the transformations are the ones holding/specifying the mapping of a source system attribute to the roles/groups to be provisioned in the target system. Should the transformation really hold all the mapping between the attributes and values maintained?
If yes, wouldn’t that be difficult to support if we put all the mapping inside the transformation especially for organizations with huge user count and various roles, and considering that the mapping is written in JSON format?
Or is there like a database (or a different service?) where we can put the mapping and SAP IPS reads from that?

[jaksweyn]

Hi, Barnabas!

Thanks for your reply, but this doesn't seem to answer my question.

Perhaps your answer is for a different question?

Best Regards,

Yan

[oppancs]

Dear jaksweyn ,

Yes you are right. It was indeed for a different question. Sorry for that.

Regards,

Barnabás

[GerganaTsakova]

Hello Yan,

Sorry for the belated reply! Regarding your two questions:

1) Should the transformation really hold all the mapping between the attributes and values maintained? - No, these are just default transformations, which contain the full pack of mappings for SCIM-supported entity attributes. Some of these mappings you can modify, and others you can even delete if they are not relevant to your scenario. If you need to add more attributes, you have to manually add more mappings.

2) Is there like a database (or a different service?) where we can put the mapping and SAP IPS reads from that? - No, there is no such a place for holding mappings. The IPS reads and provisions identities only based on the Read & Write JSON transformations.

You can learn more here: Transformation Types

Best regards,

Gergana