Oracle Access Manager (OAM) Oauth - Password Grant Type Issues With Special Characters "Invalid input. Please conform to regex ..."
(Doc ID 2690257.1)
Last updated on SEPTEMBER 20, 2023
Applies to:
Oracle Access Manager - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
When Upgrading OAM 11g to 12c and Implementing Oauth, as there isn't exactly functional parity between the two versions, there are some reported issues.
The design of Oracle Access Manager 12c Oauth (functionality) is completely different than Oracle Access Manager 11g Oauth functionality.
This lead to issues being reported that in Oracle Access Manager (OAM) 12c Oauth, were not present with Oracle Access Manager (OAM) 11g Oauth. These issues are not due to something not working in the upgrade process, as there is no migration path at this time for 11g Oauth the 12c Oauth, put are specific to the 12c implementation of the Oauth functionality.
This note is dealing specifically with OAM 12c Oauth Password Grant Type Issues when the password contains special characters like "%, #, or $".
- When using and OAUTH Token API : http://<OAM_HOSTNAME>:<OAM_PORT>/oauth2/rest/token, to exchange a user's credentials, only users with special characters in their password are not able to authenticate.
- OAM Diagnostic Log
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 |