Which protocol caches a token after it has been acquired?

Which protocol caches a token after it has been acquired?

• A. MSAL
• B. OAuth 2.0
• C. OpenID Connect
• D. SAML

Answer: (A)

Token caching is about storing tokens after they are issued so they can be reused for future requests without repeating the full sign-in flow. The Microsoft Authentication Library caches tokens automatically once you acquire them. This token cache can hold access tokens, refresh tokens, and ID tokens, and it may be stored in memory or persisted securely to disk depending on the platform. When your app needs to access a protected resource, the library first checks the cache for a valid access token; if one is found and still valid, it’s used directly. If the token has expired, the library can use a refresh token from the cache to obtain a new access token without prompting the user again, keeping the experience seamless. OAuth 2.0 and OpenID Connect describe how tokens are issued and validated but don’t mandate a specific caching mechanism; caching is an implementation detail provided by libraries built on these protocols. SAML operates with different token formats (assertions) and isn’t focused on runtime token caching in the same sense as modern OAuth/OIDC flows.

Token caching is about storing tokens after they are issued so they can be reused for future requests without repeating the full sign-in flow. The Microsoft Authentication Library caches tokens automatically once you acquire them. This token cache can hold access tokens, refresh tokens, and ID tokens, and it may be stored in memory or persisted securely to disk depending on the platform. When your app needs to access a protected resource, the library first checks the cache for a valid access token; if one is found and still valid, it’s used directly. If the token has expired, the library can use a refresh token from the cache to obtain a new access token without prompting the user again, keeping the experience seamless.

OAuth 2.0 and OpenID Connect describe how tokens are issued and validated but don’t mandate a specific caching mechanism; caching is an implementation detail provided by libraries built on these protocols. SAML operates with different token formats (assertions) and isn’t focused on runtime token caching in the same sense as modern OAuth/OIDC flows.