Check when a token or certificate stops working

Test how HashiCorp Vault, Teleport and Smallstep end access. Check whether a live session stops, a fresh request fails or a certificate can no longer renew.

Before you start

  • Use a disposable credential in a test Vault instance, Teleport cluster or Smallstep certificate authority. Keep separate administrative access and a test resource you can safely reach again.
  • Record the intended expiry and the one test identity or certificate you plan to affect. Keep tokens, private keys and recovery material out of your notes.

Data and access

Shared or checked
The provider checks its issued token or certificate when a caller requests access. The exercise compares active use with a fresh request or renewal.
Check separately
Expiration, renewal and termination of an already-open session are separate checks. Use the same relying service for each comparison.
  1. HashiCorp Vault

    Use a short-lived service token for a read against a test path. Look up its remaining lifetime, whether it is renewable and the policies that apply. Revoke it through the separate administrator and retry the read with the old token. Vault can revoke child tokens and associated leases with the parent, so use a disposable token with no shared dependents.

    Check. The initial read works with the test token. After revocation, the same token no longer reads the test path.

  2. Teleport

    Open a session on a test resource with a disposable user. From a separate administrator account, create a scoped lock on that test user. Check that an active session covered by the lock ends and that a new session is rejected while the lock is in force. Remove the test lock when finished and confirm the test user can start a new session.

    Check. The scoped test session ends and a new one is rejected during the lock. A fresh session works after you remove it.

  3. Smallstep

    Issue a short-lived certificate from a test step-ca authority and record its serial number and expiration. With passive revocation, the CA rejects renewal and the issued certificate can still be accepted until it expires. Check renewal and test the original certificate against the relying service separately. If the service checks active revocation, follow the configuration for that deployment.

    Check. Record renewal and the relying service’s response separately for the same certificate serial number and expiration.

  4. Verify from the client

    Record the result for the exact token, identity or certificate. Note whether a current session ended, a new connection failed, a renewal failed or the original credential remained usable until its expiration.

    Check. Each record identifies the receiver and credential and shows which operation changed at the recorded time.

Check your result

For each relevant action, keep a result from the receiving service with the test identity or certificate serial number and time. Leave a working administrator available.

How to verify your setup

If you get stuck

The credential still works after the change

Check the credential actually presented by the client. For Teleport, verify that the lock targets the correct user and session. For Smallstep, check whether you tested renewal or a certificate that has yet to expire.

Report a problem with this guide

Explore all setup guides →