Contents
Token-based authentication is a protocol which allows users to verify their identity, and in return receive a unique access token. Once the user logs out or quits an app, the token is invalidated. Token-based authentication is different from traditional password-based or server-based authentication techniques.
The tokens are designed to be compact, URL-safe and usable especially in web browser single sign-on (SSO) context. It’s just hash which is associated with user in database or some other way. That token can be used to authenticate and then authorize a user access related contents of the application.
What do you need to know about token authentication?
Token authentication requires users to obtain a computer-generated code (or token) before they’re granted network entry. Token authentication is typically used in conjunction with password authentication for an added layer of security. This is what we refer to as two-factor authentication (2FA).
What does token authentication do for Azure CDN?
For a full comparison of CDN features, see Azure CDN product features. Token authentication is a mechanism that allows you to prevent the Azure Content Delivery Network (CDN) from serving assets to unauthorized clients.
How is Access Granted or denied based on a token?
Access is granted or denied based on the token. Administrators set limits on tokens. You could allow a one-use token that is immediately destroyed when the person logs out. Or you could set the token to self-destruct at the end of a specified time period.
What does it mean when a server issues a token?
With token authentication, a secondary service verifies a server request. When verification is complete, the server issues a token and responds to the request. The user may still have one password to remember, but the token offers another form of access that’s much harder to steal or overcome.