Setting 'samaccountname' in UME <-> LDAP integration

[Former Member]

Hello All,

Portal version = EP7 SP9

We have configured UME with MS Active Directory successfully, except for the setting of 'samaccountname' in the parameter - Use Unique Attribute for UME Unique ID

Could you please guide me as to what will happen if I set this parameter with samaccountname now?

I did check SAP Note # 777640 but it mentions EP 6

Awaiting Reply.

Regards,

Ritu

[Former Member]

I have enabled the 'UniqueId' field on the UME configuration interface & restarted the Java instance. Issue resolved

[Former Member]

hi,

The note is applicable for EP7.0 also.

On applying the note you can over the mismatch happenning with respect to LDAP changes.

The reason for such occurrence was that, the UME (User Management Engine) assigns unique IDs to the LDAP users. By Default the unique ID contains the distinguished name of the user.

If the user is moved to a different location in the LDAP Directory, its distinguished name changes.

For example the unique ID of a user is

USER.CORP_LDAP.cn=testuser, ou=people, o=mycompany

If this user is changed to a different location for which ou=admins then the unique ID of the user is changed to

USER.CORP_LDAP.cn=testuser, ou=admins, o=mycompany

In this case the UME can no longer find any data associated with the user under the old unique ID and the data (role assignment or user mappings) stored in database for such users gets lost. So in this regard we have changed the configuration of the UME so that it no longer uses the distinguished name in the unique ID, instead we use a unique attribute (MindTree mindu2019s ID) that is never changed in the LDAP directory.

once you set the parameter with samaccountname then the behaviour of getting the user roles/worksets misplaced will go off, and changes in LDAP will not reflect your portal TLN.

regards,

Kris