OAM 11g: Could Not Modify User Attribute obLoginTryCount In OAM-OIM 11.1.1.5 Integrated Environment With OVD
(Doc ID 1369943.1)
Last updated on MARCH 01, 2019
Applies to:
Oracle Access Manager - Version 11.1.1.5.0 and laterInformation in this document applies to any platform.
Symptoms
Oracle Access Manager (OAM) 11.1.1.5 has been integrated with Oracle Identity Manager (OIM) 11.1.1.5.
The integration was performed using Oracle Virtual Directory (OVD) as Identity Store.
When testing integrated OAM-OIM password policy management with repeated login attempts using incorrect password, errors similar to the following are seen in the OAM Managed Server log:
<Oct 5, 2011 9:49:53 AM CEST> <Error> <oracle.oam.user.identity.provider> <OAMSSA-20040> <Could not modify user attribute for user : <USERNAME>, attribute : obLoginTryCount, value : 1 .>
<Oct 5, 2011 9:49:53 AM CEST> <Warning> <oracle.oam.controller> <OAM-02072> <Ignoring failure during Identity Store operation.>
Steps to reproduce
1. Access resource protected by OAM 11g.
2. OAM 11g login page is displayed.
3. Submit correct username with incorrect password.
4. OAM 11g login page is redisplayed. OAM Managed Server log shows error '<OAMSSA-20040> <Could not modify user attribute for user : USERID, attribute : obLoginTryCount, value : 1 .>'
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |