SAP EP Portal User Needs Password Reset Frequently

[tejpal628]

Hi Team,

We have users from both Database(local users) and LDAP.

The database users are frequently experiencing "Authentication errors"

when they try to login with password. On resetting the password the

user is able to login back into portal. Can you please advise on how to over

come this issues to configure portal to use both LDAP and database

(Local users) as data source for UME database..

Note: LDAP User ID and Local user id are unique or similar. UME data store is Java Stack.

Thanks & Regards,

Tejas

[tejpal628]

Thanks Samuli & Charles,

Yes the same user id Exist in both LDAP and UME database.

But I Tried disabling LDAP user id and checked. then too user is facing the same problem.

Tejas.

[Former Member]

Its better that you delete the user id in the UME not the LDAP.

Then just make sure their LDAP ID has the same roles.

[Former Member]

Hi,

Just to make sure we are clear here.

you have LDAP and UME users, BUT the users are NOT in both places.

So for example if you had USER1 in LDAP he does not exist in UME.

You can't/shouldn't have it in both places.

Obviously for support purposes id's like Administrator exist in UME and should do (for when LDAP is not accessible/maintenance).

if you have users existing in both places, then you will have problems.

Hope that helps.

Tony

[Former Member]

You can't have it both ways. If you have LDAP and local users, LDAP will be the preferred method. If a user is authenticated by LDAP, the UME will match the user in LDAP. I would suggest you find out the reason why local users are getting authentication errors. UME can be configured to react to most conditions, e.g. automatically locking/unlocking/etc. You might also want to look into UME Security Policy Profile configuration.

[tejpal628]

Hi Samuli,

Thanks for your reply,  I will go through trace file of user authentication errors .

I would also like to highlight that when I checked in user management .of UME Database User,

it shows last unsuccessful login field as blank, where I guess it should provide 'time and date'.when there was an incorrect attempt made by user.

Is this because same User ID exist in LDAP location ?

Thanks & Regards,

Tejas

[Former Member]

Date of Last Failed Password Logon is maintained for local users so yes, I suspect when users get authentication errors they are actually authenticated against LDAP. What Charles wrote is also true, you shouldn't have both LDAP and local users by the same ID.