OAMMS Register API Does Not Lock User Account After Max Invalid Password Attempts (Doc ID 1934652.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Mobile and Social - Version 11.1.2.2.0 and later
Information in this document applies to any platform.

Goal

Register API does not lock use account after max invalid apssword attempts.
We have configured new authentication scheme which is using "Password Policy Validation" authentication module. IAMSuite AGent -> OICAuthenticationPolicy refers to new authentication scheme. As a result of this OAMMS authenticate API does update ob* attributes in directory and handles account locka s per password policy defination.
Register API does not seem to trigger authentication scheme using "Password Policy Validation Module" authentication module.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms