Can portal use objectGUID for ume.ldap.unique_user_attribubute?

[former_member18193]

Hi,

Per SAP Note 777640 "If you switch to this configuration after you

have already maintained data in the portal, all portal and UME data

(like role assignment or user mapping) is lost for LDAP users."

Can we configure "ume.ldap.unique_user_attribute" to use 'objectGUID'

instead of 'samaccountname' in portal.

regards,

[renefeisterSAP]

Hi Lisandro,

The note covers an issue from the past, long time ago the UME was utilizing the DN instead of samaccountname when connecting to AD and storing user related data in UME. Now the new configuration is using samaccountname and that means everything is fine also when a user moves from one OU to another. The note warns that when you switch the configuration from using "DN" to using "samaccountname" you will loose certain data (locally stored in the UME database).

Is that an issue for you?

I do not think that using objectGUID is an option here that should be recommended. I even fear that it would not work, objectGUID is NOT a clear text attribute, it is an encoded one. And my assumption is that there is no coding existing in the UME that takes care of such a speciality.

Regards,

René