Last updated on DECEMBER 05, 2016
Applies to:Oracle Adaptive Access Manager - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
The problem is that new users cannot login after the custom-otp policy is put in place to be triggered for all users. Works fine for users who have previously registered. So, seems that likelihood is that the failure occurs because OTP token cannot be sent since the user was never registered (and the system doesn't know where to send the token). Now, need to figure out a way to change the policy so that it only kicks in if a user has previously registered.
Once a new user attempts to login, they face an error message after submitting their username/password stating there has been a technical problem.
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