cancel
Showing results for 
Search instead for 
Did you mean: 

VDS (LDAP) as UME Data Source

polina_klibanova
Explorer
0 Kudos

Hi,

we have installed the VDS in order to connect the IDM IS as UME Data source (s. http://sapassets.edgesuite.net/sapcom/docs/2015/07/52e9e755-5a7c-0010-82c7-eda71af511fa.pdf).  Before we created the LDAP connection, we have had some users incl. technical users in our local DB. After we have maintained the connection with read/write option,  we get some problems with login to the system. One of the the errors in the developer trace was:

Caused by: com.sap.security.api.DuplicateKeyException: USER_AUTH_FAILED: Logonid "Guest" is not unique!

at com.sap.security.core.imp.AbstractUserAccount.<init>(AbstractUserAccount.java:471)

at com.sap.security.core.imp.DBTextFileUserAccount.<init>(DBTextFileUserAccount.java:44)

at com.sap.security.core.imp.UserAccountFactory.getReadonlyUserAccountByLogonId(UserAccountFactory.java:611)

at com.sap.security.core.imp.UserFactory.getUserByLogonID(UserFactory.java:1367)

at com.sap.security.core.imp.UserFactory.getUserByLogonID(UserFactory.java:1401)

at com.sap.security.core.imp.UserFactory.getUserByLogonID(UserFactory.java:1459)

at com.sap.jms.server.sc.UMESecurityProvider.checkPermission(UMESecurityProvider.java:232)

... 16 more

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Logonid "Guest" is not unique!

... 23 more

What should we configure to prevent this problems?

Best regards

Polina

Accepted Solutions (0)

Answers (2)

Answers (2)

Chenyang
Contributor
0 Kudos

Hi

It says logonuid Guest is not unique.

Perhaps you have too many "guests" visiting you?

Do you have a local guest from UME, and another guest from VDS?

Cheers

Chenyang

former_member2987
Active Contributor
0 Kudos

Hi there,

LDAP does not allow DNs that are not unique. Depending on the Schema, there might be some other attributes that are required to be unique (UID, CN, name are all ones I've seen in the past)

To troubleshoot, change one attribute at a time in one of the affected accounts until you no longer get the error. Then you can go back and figure out how your organization wishes to mitigate these issues.

Regards,

Matt