-
Notifications
You must be signed in to change notification settings - Fork 277
Add properties to TokenIntrospectionResponse for all optional claims defined in RFC 7662 (OAuth 2.0 Token Introspection) #577
Conversation
3d72d7f
to
b6315d7
Compare
#576 has been merged. Could you kindly rebase this PR? Thx. |
We'll look to have it in by early next week (pending a rebase). |
b6315d7
to
70b64f9
Compare
It's rebased. Thanks for merging my other pull requets! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's probably a good idea to model the optional claims from the spec like this, but I think if we're going to do that, we should do all of the claims listed here.
Good point. Should I implement the additional properties as part of this pull request or should it be done in a followup pull request? |
70b64f9
to
738ceff
Compare
I went ahead and implemented properties for all optional claims defined in RFC 7662. |
3822fe2
to
7f53cf1
Compare
As described by [RFC 7662 - OAuth 2.0 Token Introspection][1] [1]: https://datatracker.ietf.org/doc/html/rfc7662
7f53cf1
to
6e089e7
Compare
This PR has been migrated to DuendeSoftware/foss#98 |
As described by RFC 7662 - OAuth 2.0 Token Introspection
Note
This pull request is stacked on top of #576