liveBook · Manning

Short-lived token

As explained in Grokking Software Architecture

A credential configured to expire after a brief period, limiting the usefulness of theft or compromise.

A vendor integration should not rely on a permanent API key. Issue an OAuth 2.0 token that expires after 15 minutes: if the vendor is breached and the token is stolen, the attacker’s window of opportunity is small. section 11.7.1

A smaller window

Instead of handing a vendor a permanent credential, issue a 15-minute token. A stolen token then offers an attacker only a brief opportunity. section 11.7.1

How Grokking Software Architecture covers it

How deep it goes
Defines a vendor token’s 15-minute expiration and theft benefit, without detailing token issuance mechanics.
Examples
Contrasts a permanent vendor API key with a 15-minute OAuth 2.0 token.
What you can do after
Configure OAuth 2.0 to issue vendors tokens that expire after 15 minutes.
How it connects
Connects OAuth 2.0, API keys, and third-party integrations.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.