OAM 12c - Not Applying Custom Password Policy Assigned For The User, Instead Applying Default Password Policy Rules
(Doc ID 2807885.1)
Last updated on DECEMBER 21, 2022
Applies to:Oracle Access Manager - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 12.2.1.x version,
OAM not applying Custom Password Policy assigned for the User instead applying Default Password Policy rules
OAM APIs are working fine where we are able to create policy with expiry attributes and assign to user. But when we try to change the password for that user, OAM is applying default policy only instead of the custom policy which we created with expiry attributes.
Below are the steps performed.
1. Enabled password management policy in OAM.
2. Created Custom Password Policy constrained by group with expiry attribute set using OAM API.
3. Created group in LDAP and added user to that group.
GET policy detail API for the given User is working fine where its returning properly the highest priority policy assigned to that user.
But when we try to change password for the given user, its validating against the Default Password Policy instead of the Custom Password Policy which GET API is returning.
- to apply the Custom Password Policy
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