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
{{ message }}
This repository has been archived by the owner on May 31, 2022. It is now read-only.
Note that a properly formed and authorized query for an inactive or
otherwise invalid token (or a token the protected resource is not
allowed to know about) is not considered an error response by this
specification. In these cases, the authorization server MUST instead
respond with an introspection response with the "active" field set to
"false" as described in Section 2.2.
CheckTokenEndpoint throws an InvalidTokenException in this case, but should instead respond with:
{
"active" : false
}
Given that no further releases are planned for this project, I'm logging this simply as a point of reference to help address spring-projects/spring-security#10038.
The text was updated successfully, but these errors were encountered:
The Introspection spec states (emphasis mine):
CheckTokenEndpoint
throws anInvalidTokenException
in this case, but should instead respond with:Given that no further releases are planned for this project, I'm logging this simply as a point of reference to help address spring-projects/spring-security#10038.
The text was updated successfully, but these errors were encountered: