Credential lifecycle

The Lifecycle

Transitions Explained

Supplying authentication creates a fresh credential and replaces the current one. Disconnection revokes the selected credential. Maintenance records destruction only after storage no longer contains the value, so deletion scheduling and database state can temporarily differ.

What Cannot Happen

A destroyed value cannot supply authentication again. The old record is not restored; supplying credentials creates another record.

Concurrency and Timing

Secret creation precedes the database credential transaction. A refused database change requests cleanup of the new secret, while successful replacement requests recoverable deletion of the old one. Refresh locking serializes token requests per account.