Add Support for Opaque OAuth2 Tokens to Resource Server - #6352
Conversation
3830e0b to
02faaa8
Compare
0f1fc4d to
5faa47b
Compare
|
@rwinch I've updated to use |
978482f to
ebadab9
Compare
There was a problem hiding this comment.
Just want to ensure we think about if/how this aligns with OAuth2 Log In. Do we support discovery? If an application is supporting oauth2 log in and resource server do we want them to have to configure the client id/secret twice?
There was a problem hiding this comment.
Yes, I think discovery makes sense through the issuer-uri once it supports the /.well-known/oauth-authorization-server endpoint, which defines introspection_endpoint as an attribute.
As for the client, ideally, the user wouldn't need to specify the same client twice as I imagine that the 95% case is that they are the same. If there is only one client in client registration, it seems reasonable to infer that client is the same for the introspection endpoint.
fe6a7bc to
a0a08d9
Compare
89693f0 to
eb80815
Compare
|
Thanks @jzheaux. Good to go on my end. As an FYI, it's best to not force push while in the review process as it's difficult to keep track of changes between review steps. I would just keep adding commits as you update based on feedback. |
|
This is now merged into |
No description provided.