liveBook · Manning

One-time code

A one-time code is a temporary authentication credential accepted for a single attempt or operation, or during a limited validity period.

How 3 Manning books explain it

Software Security for Developers

A one-time password is an authentication code that is valid for a single use or a limited period.

How it is used
Supports passwordless login and multifactor authentication by providing a temporary verification key.
How deep it goes
Explains expiration, single use, delivery, risks, and implementation safeguards without descending into cryptographic protocol internals.
Examples
Uses six-digit codes delivered by SMS, email, or authenticator apps such as Google Authenticator, Authy, and Microsoft Authenticator.
What you can do after
Apply it by choosing safer delivery, expiration, generation, rate-limiting, monitoring, and invalidation practices.

Read how Software Security for Developers explains one-time code →

Real-World Cryptography

A one-time password is an authentication code intended to be accepted for only one authentication attempt or a narrowly defined validity period.

How it is used
Enables passwordless user authentication without sending a long-term symmetric key to the service.
How deep it goes
Explains symmetric-key derivation, HOTP counters, TOTP time values, registration, generation, and constant-time validation.
Examples
Uses Google Authenticator, six-digit 30-second codes, QR-code registration, and an example.com TOTP login flow.
What you can do after
Apply it via HOTP or TOTP to authenticate users without exposing their long-term symmetric keys.

Read how Real-World Cryptography explains one-time code →

Authorization in Action

A one-time password is a temporary authentication code intended to be accepted only once or during a limited validity period.

How it is used
Strengthens password-based login by adding possession evidence during multifactor authentication.
How deep it goes
Explains registration, factor binding, delivery methods, and security-usability trade-offs, but does not detail code-generation internals.
Examples
Uses SMS and email PINs, authentication-app codes, push notifications, and an identifier-and-factor login flow.
What you can do after
Apply one-time codes as possession factors and compare their phishing, interception, usability, and MFA-fatigue risks.

Read how Authorization in Action explains one-time code →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.