Glossary
revocation
Revocation cancels a credential so it never works again. OneLifeVibe checks it before serving a key or token.
Updated November 15, 2026
- Standard
- RFC 7009 (OAuth 2.0 Token Revocation)
- Also called
revoke
At OneLifeVibe
- The key has the wrong shape, does not exist, or its secret does not match the stored SHA-256 hash. Keys are checked in this order: shape, existence, hash, expiry, revocation, client status, plan.
Related terms
What it means
Revocation is cancelling a credential so it never works again. The credential can be an API key or a token. In OAuth 2.0, RFC 7009 covers token revocation: a client tells the authorization server that a token should stop being accepted. Revocation is a state change, not a delete. The record can still exist while every later use is rejected.
An API key works the same way in principle. You cancel the key and authentication with it fails from then on. That is different from expiry, which ends a credential at a set time. Revocation ends it now.
How it works
In an OAuth flow, the client sends the token to the authorization server's revocation endpoint. RFC 7009 defines that request. The server marks the token as revoked, and later requests that present it fail. For API keys, the check can be a flag read on each request.
The important part for builders is order. A server should check revocation before it serves a protected resource. If revocation is checked late, or skipped when a key looks valid, a cancelled credential can still get through. Revocation also needs to be the same state that the request path reads. A flag written by one process but ignored by another is not revocation in practice.
How OneLifeVibe uses it
OneLifeVibe checks revocation before serving a key or token. Keys go through a fixed order: shape, existence, hash, expiry, revocation, client status, plan. Revocation is the fifth check. A key that fails shape, existence or the SHA-256 hash check never reaches it. A key that passes expiry can still fail at revocation.
The order matters when you debug a rejected key. Check the earlier steps first: wrong shape, no record, or a secret that does not match the stored SHA-256 hash. If those pass and expiry passes, revocation is the next gate. A revoked key is not served, and neither is a revoked token.
Common mistakes
Treating revocation as deletion is the usual mistake. If you remove your only record of a key, you may lose the ability to recognize it as revoked. Keep the state that says cancelled, and check it on the request path.
Another mistake is relying on expiry. A key with time left can still be revoked. Test a correctly shaped key with a matching secret after you revoke it, not just a malformed key. For OAuth, do not assume a revocation response means every service has already stopped accepting the token. The check has to happen where the token is used.
Questions
Does revoking a token delete it?
No. Revocation cancels the credential so it never works again, while the record can remain. OneLifeVibe checks revocation before serving a key or token.
Where does revocation sit in OneLifeVibe's key checks?
It is fifth, after shape, existence, hash and expiry, and before client status and plan. A key that reaches this step and is revoked is not served.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.