My Oracle Support Banner

Oracle Access Manager (OAM) Oauth Flow Fails When Windows Native Authentication (WNS) Fallback To Form Is Enabled And The "state" Parameter Is Very Long (Doc ID 2893311.1)

Last updated on OCTOBER 24, 2023

Applies to:

Oracle Access Manager - Version and later
Information in this document applies to any platform.


Sending a request to get an OAuth Authorization Code fails if the Consent page is protected by KerberosScheme (Windows Native Authentication), WNA Fallback to FORM is enabled and the "state" parameter is very long (800+ characters).

Sample Request

http(s)://<hostname>:<port>/oauth2/rest/authz?response_type=code&client_id=<client-id>&domain=<domain>&scope=<scope>&redirect_uri=http://<hostname>:<port>&state= <VERY_LONG_VALUE>


Error Stack
[SRC_METHOD: getWNAOptTokenString] Cookie Value: OAM_WNA_OPT_OUT=TRUE;path=/;
[SRC_METHOD: getResourceUrl] ENTRY
=====> Invalid done URL specified during logout - no protocol:<URL>
[SRC_CLASS:] [SRC_METHOD:sanitizeURLInput] RETURN null
=====> Sanitization of the url failed
[SRC_METHOD: checkForCustomErrorPage] RETURN /oam/pages/servererror.jsp
The issue does NOT reproduce if ...
  • WNA Fallback to FORM is disabled and "state" is 800+ characters long
  • WNA Fallback to FORM is enabled and "state" is renamed to something else like "status" and is 800+ characters long
  • WNA Fallback to FORM is enabled and "state" has a short length, like 100 characters









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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.