Skip to main content
All glossary terms

Credentials & security

Secret expiry

Secret expiry is a configured point after which a secret should no longer be accepted or used. The effect depends on the system enforcing the expiry; a date stored as metadata does not revoke the credential at an upstream service unless that service or workflow acts on it.

Also known as credential expiration.

Why it matters in practice

Expiry can reduce reliance on long-lived credentials, but dependent jobs need a replacement and a clear renewal owner. Notifications, revocation, and application behavior are separate parts of the lifecycle. Teams should test what happens after expiry instead of assuming every client will fail safely.

Example

A service owner receives an expiry notice, provisions a replacement for api.example.com, and verifies the integration before retiring the old value.

Educational note

This definition is general information, not legal advice. It may omit facts that matter to a specific situation and does not establish or guarantee compliance.