signing key
The secret key used to sign tokens or messages, together with the key used to verify them, which may be the same secret or the public half of a pair.
Whoever holds a signing key can mint valid tokens for anyone.
In more detail
The verifier, not the token, decides which keys are trusted. Generate signing material under controlled access and rotate it on a schedule with an overlap period.
Related terms
- key rotation — Replacing a password or key with a new one on a schedule or after a suspected leak, and re-encrypting what it protected.
- key identifier — A short name in a token header, kid, that says which of the verifier’s trusted keys was used to sign it.
- JSON Web Key Set — A standard JSON document that publishes a set of public keys, each with a key identifier, so clients can verify tokens.
- digital signature — A value computed from data and a secret key that lets anyone with the matching verification key confirm the data came from the key holder and was not changed.
- JSON Web Token — A compact signed token made of three base64url parts separated by dots: a header, a payload of claims and a signature.
- secret — Any value that grants access, such as a password, access token or private key, and must be kept out of code and version control.
- user secrets — A .NET development tool that stores secrets for a project in your user profile, outside the project folder, so they never reach source control.
- hardware security module — A tamper-resistant device that stores keys and performs cryptography inside itself, so keys cannot be copied out.
- revocation — Cancelling a credential, session or key before its natural expiry so it stops working.
Taught in
- JSON Web Tokens — Modern API Architecture: REST, GraphQL & gRPC
- Scopes And Key Rotation — Modern API Architecture: REST, GraphQL & gRPC
- The Options Pattern: Strongly Typed Configuration — Modern .NET Core, C# & Enterprise Microservices
- Environment Layering and User Secrets — Modern .NET Core, C# & Enterprise Microservices
- Authentication: JWTs and Claims — Modern .NET Core, C# & Enterprise Microservices
- Same Rule, Two Kinds: Controls And Frameworks — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Open To Every Interface: Controller Manager And Scheduler — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Which Benchmark, And Who Checked It? Compliance And Frameworks — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Workload Identity — Application Security & Threat Modeling for Engineers
- Provenance And Signing — Application Security & Threat Modeling for Engineers
References
- RFC 7517: JSON Web Key (JWK)
- RFC 8725: JSON Web Token Best Current Practices
- RFC 7515: JSON Web Signature
- OWASP Secrets Management Cheat Sheet
- Sigstore: signing overview
- NIST SP 800-57 Part 1: key management