KB Article #181713
OAuth client application is not properly configured | Problem removing stateID 54167....908 from the state cache | java.lang.IllegalStateException: No OAuth State found cache for stateID
Problem
In a newly upgraded environment to 77, this error appear in traces
DEBUG 20/Apr/2021:13:38:39.020 Removing state param:54167ca3-06a6-4597-8872-33190dbee908 from the cache
ERROR 20/Apr/2021:13:38:39.026 Problem removing stateID 54167ca3-06a6-4597-8872-33190dbee908 from the state cache
ERROR 20/Apr/2021:13:38:39.026 OAuth client application is not properly configured; No OAuth State found cache for stateID:54167ca3-06a6-4597-8872-33190dbee908
DEBUG 20/Apr/2021:13:38:39.026 } = 2, filter [Exchange Authorization Code for Token and ID Token]
DEBUG 20/Apr/2021:13:38:39.026 Filter [Exchange Authorization Code for Token and ID Token] completes in 6 milliseconds.
DEBUG 20/Apr/2021:13:38:39.026 ..."ISAMOAuthCallbackPolicy" complete.
ERROR 20/Apr/2021:13:38:39.026 Filter that caused failure: Exchange Authorization Code for Token and ID Token
Policy 'ISAMOAuthCallbackPolicy' {
Filter 'Extract State-Parameter' Status: PASSED
Filter 'Exchange Authorization Code for Token and ID Token' Status: ABORTED
}
OAuth client application is not properly configured
java.lang.IllegalStateException: No OAuth State found cache for stateID:54167ca3-06a6-4597-8872-33190dbee908
at com.vordel.oauth.client.AuthzCodeApplication.<init>(AuthzCodeApplication.java:57)
at com.vordel.oauth.client.AuthzCodeApplication.<init>(AuthzCodeApplication.java:23)
at com.vordel.oauth.client.AuthzCodeApplication$Builder.build(AuthzCodeApplication.java:153)
Resolution
The API Gateway was in Production and it was never restarted since the upgrade.
The restart of the 2 nodes has put the cache in sync again and the issue has disappeared.