You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setup OIDC provider and OIDC client as per the requirement of the demo.
Start Implicit, login as user, user prompted for consent, and OIDC flow successful for first time.
Redo the Implicit flow again with same browser session, OpenAM will return error to the authorization request
{
"error_description": "Error running OIDC claims script: java.util.concurrent.ExecutionException: javax.script.ScriptException: javax.script.ScriptException: java.lang.SecurityException: Access to Java class "java.util.LinkedHashMap$LinkedKeyIterator" is prohibited.",
"state": "af0ifjsldkj",
"error": "not_found"
}
The issue is not present if user logged out before redoing the OIDC login flow
The text was updated successfully, but these errors were encountered:
…f the user search attribute of the LDAP authentication module does not match that of the data store (OpenIdentityPlatform#134)
* Update Issue 84
* Update Judge Point
* Update copyright
* Update store username attribute
* Update store
* Update userNameValues
* Update SharedState
* Update coypright & comment
closeOpenIdentityPlatform#84
OpenAM version 14.1.8 (OpenAM 14.1.8 Build 900d631 )
Using the openid demo sample from https://github.com/ForgeRock/openid
Setup OIDC provider and OIDC client as per the requirement of the demo.
Start Implicit, login as user, user prompted for consent, and OIDC flow successful for first time.
Redo the Implicit flow again with same browser session, OpenAM will return error to the authorization request
{
"error_description": "Error running OIDC claims script: java.util.concurrent.ExecutionException: javax.script.ScriptException: javax.script.ScriptException: java.lang.SecurityException: Access to Java class "java.util.LinkedHashMap$LinkedKeyIterator" is prohibited.",
"state": "af0ifjsldkj",
"error": "not_found"
}
The issue is not present if user logged out before redoing the OIDC login flow
The text was updated successfully, but these errors were encountered: