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
Background
It would be super useful to have a full example and or guide to setting up spring authorisation server for use with opaque tokens.
I am currently working on migrating my existing app (Old spring auth server using opaque tokens with a custom PKCE Implementation) to this project and would be happy to write up an example / how-to guide after I have it working.
So far (through a little trial and error) I have gotten to the point where my SPA directs users to login and auth server directs them back with the code. My SPA then exchanges the code for an opaque access token which seems to work as expected.
The part I am currently stuck on is the Introspect endpoint.
Whenever I make an introspect request to the auth server (/oauth2/introspect) I am getting the error response shown below.
{
"error": "invalid_request"
}
The annoying part of this is I can not see in the logs any reason for this and I can see that the token does exists in my DB.
Questions:
Is there any extra configuration needed for the Introspect Endpoint that isn't enabled out of the box?
Does anybody have a working example they can share?
Does anybody have any idea where I am going wrong?
Thanks,
Carl
The text was updated successfully, but these errors were encountered:
CarlRobinsonRAM
changed the title
New example Request: Opaque token version of the "default-authorizationserver" example
How To: Opaque token version of the "default-authorizationserver" example
Jan 20, 2023
CarlRobinsonRAM
changed the title
How To: Opaque token version of the "default-authorizationserver" example
"invalid_request" when sending opaque access token to Introspect endpoint
Jan 21, 2023
Whenever I make an introspect request to the auth server (/oauth2/introspect) I am getting the error
The Introspection Endpoint requires client authentication so this might be the issue? See Configuring Client Authentication for more details.
The annoying part of this is I can not see in the logs any reason for this
You can enable TRACE logging and then you will see where the issue is. Logging was added in gh-159.
I'm going to close this as these are questions that are better suited to Stack Overflow. We prefer to use GitHub issues only for bugs and enhancements.
However, if you feel there is something specific missing in the documentation or you would like to propose a How-to guide, please log a new issue. Thank you.
Background
It would be super useful to have a full example and or guide to setting up spring authorisation server for use with opaque tokens.
I am currently working on migrating my existing app (Old spring auth server using opaque tokens with a custom PKCE Implementation) to this project and would be happy to write up an example / how-to guide after I have it working.
So far (through a little trial and error) I have gotten to the point where my SPA directs users to login and auth server directs them back with the code. My SPA then exchanges the code for an opaque access token which seems to work as expected.
The part I am currently stuck on is the Introspect endpoint.
Whenever I make an introspect request to the auth server (/oauth2/introspect) I am getting the error response shown below.
The annoying part of this is I can not see in the logs any reason for this and I can see that the token does exists in my DB.
Questions:
Is there any extra configuration needed for the Introspect Endpoint that isn't enabled out of the box?
Does anybody have a working example they can share?
Does anybody have any idea where I am going wrong?
Thanks,
Carl
The text was updated successfully, but these errors were encountered: