Expose a token revocation endpoint for OAuth2 access and refresh tokens
Open
porcellus
opened this issue 1 year ago
•
0 comments
We expect it to match: https://datatracker.ietf.org/doc/html/rfc7009
It should forward the token to the core which will handle revocation in db
Also add a related index function (to expose this to users) and recipe interface function (to allow overriding) and API interface function (to allow API overrides)
Internally, we want to match our own naming conventions, but when loading info from the request we need to match the RFC