-
Notifications
You must be signed in to change notification settings - Fork 258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introspection endpoint uncaught exception on get_token_info #502
Comments
The |
tpazderka
added a commit
that referenced
this issue
Apr 18, 2018
IntrospectionEndpoint should return regular response with active=False if it cannot verify the activity of the token for any reason. Close #502
2 tasks
tpazderka
added a commit
that referenced
this issue
Apr 19, 2018
IntrospectionEndpoint should return regular response with active=False if it cannot verify the activity of the token for any reason. Close #502
tpazderka
added a commit
that referenced
this issue
Apr 19, 2018
IntrospectionEndpoint should return regular response with active=False if it cannot verify the activity of the token for any reason. Close #502
tpazderka
added a commit
that referenced
this issue
Apr 19, 2018
IntrospectionEndpoint should return regular response with active=False if it cannot verify the activity of the token for any reason. Close #502
andrewkrug
pushed a commit
to mozilla-iam/pyoidc
that referenced
this issue
Jun 6, 2019
IntrospectionEndpoint should return regular response with active=False if it cannot verify the activity of the token for any reason. Close CZ-NIC#502
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://github.com/OpenIDC/pyoidc/blob/3f21791df99aad8764b3ce796ba5689241ca86c4/src/oic/extension/provider.py#L804
On unpack token can got jwkest.jws.NoSuitableSigningKeys
The text was updated successfully, but these errors were encountered: