Differences

This shows you the differences between two versions of the page.

--- tutorial:adm:systems_identifier-chaos-mismatch-uppercase [2019/07/31 14:48]
kotynekv created
+++ tutorial:adm:systems_identifier-chaos-mismatch-uppercase [2019/07/31 20:41]
kotynekv [System mappings] typo
@@ Line 3: / Line 3: @@
 ===== Motivation =====
-User account identifiers might have a different format in one system than in another, e.g. prefixed, suffixed, uppercase/lowercase. This would be no big deal if CzechIdM was configured only to provision data to this system. However in a situation where we also need to synchronize the data including the identifier (e. g. the system is the only/the most complete source of usernames) from the system to CzechIdM and store the identifier in it's "normalized" form (e. g. without the prefix, suffix or in uppercase/lowercase), you need to use a transformation script both during the synchronization and during the provisioning. In this tutorial you will learn how to configure to work correctly for the Account Management module. This tutorial won't help you with the case with no exact rule of "de-normalization" of the identifier"
+User account identifiers might have a different format in one system than in another, e.g. prefixed, suffixed, uppercase/lowercase. This would be no big deal if CzechIdM was configured only to provision data to this system. However in a situation where we also need to synchronize the data including the identifier (e. g. the system is the only/the most complete source of usernames) from the system to CzechIdM and store the identifier in it's "normalized" form (e. g. without the prefix, suffix or in uppercase/lowercase), you need to use a transformation script both during the synchronization and during the provisioning. In this tutorial you will learn how to configure the mapping to work correctly for the Account Management module. This tutorial won't help you with the case with no exact rule of "de-normalization" of the identifier"
 ===== System mappings =====
-In the synchronization you need to create AccAccount (Accounts tab in the system detail) with an identifier that in the same format as is the identifier of the account on the system. However when you put a transformation script into the mapping of the attribute marked as "identifier", the account identifier will be created in it's "normalized" form. Invoking an account management for that account would cause a creation of a duplicate AccAccount item and would "broke" the mapping for the user.
+In the synchronization you need to create AccAccount (Accounts tab in the system detail) with an identifier that is in the same format as is the identifier of the account on the system. However when you put a transformation script into the mapping of the attribute marked as "identifier", the account identifier will be created in it's "normalized" form. Invoking an account management for that account would cause a creation of a duplicate AccAccount item and would "broke" the mapping for the user.
 ==== Synchronization mapping ====