Describe the feature
Tokensmith (and the middleware) are aware of key ids and nonces for replay protection and token invalidation. We don't currently expose an endpoint or webhook to control that invalidation. We need to connect those dots.
Why do you want this feature?
Many sites have a requirement to disable access within a shorter duration than a standard access token lifetime. The standard way to handle this is by invalidating all key-ids and/or nonces associated with a user or session. All of the plumbing exists for this feature except the control endpoint.
Alternatives you've considered
I considered doing...
Additional context
No response
Code of Conduct
Describe the feature
Tokensmith (and the middleware) are aware of key ids and nonces for replay protection and token invalidation. We don't currently expose an endpoint or webhook to control that invalidation. We need to connect those dots.
Why do you want this feature?
Many sites have a requirement to disable access within a shorter duration than a standard access token lifetime. The standard way to handle this is by invalidating all key-ids and/or nonces associated with a user or session. All of the plumbing exists for this feature except the control endpoint.
Alternatives you've considered
I considered doing...
Additional context
No response
Code of Conduct