-
Notifications
You must be signed in to change notification settings - Fork 300
OAuth 2.0 Token Introspection - RFC 7662 #92
Comments
@Robbilie The above is a Google approach to a somewhat similar requirement, however rfc7662's spec is quite more detailed, with guidelines & requirements missing in this project's implementation. |
At the time of implementation, this RFC 7662 did not exist yet, therefore On 19 June 2016 at 19:18, Javier Rivera-Acosta [email protected]
|
I've done an initial implementation of the RFC 7662 spec (thiagozf/apis#10), based on the current token verification feature. My idea is to deprecate the current endpoint ( I will submit a pull request as soon as it gets more complete and stable. Feedback and/or contributions for this task are appreciated. |
Hi, Yet another question: is it planned for APIs to implement RFC 7662 (OAuth 2.0 Token Introspection, see https://tools.ietf.org/html/rfc7662)? If yes, which would be the planning horizon?
Thanks,
Martin
The text was updated successfully, but these errors were encountered: