Adds a claims challenge to the token request. The SDK will bypass the token cache when a claims challenge is specified. Retry the token acquisition, and use this value in the WithClaims method. A claims challenge typically arises when calling the protected downstream API, for example when the tenant administrator revokes credentials. Apps are required to look for a 401 Unauthorized response from the protected api and to parse the WWW-Authenticate response header in order to extract the claims. See https://aka.ms/msal-net-claim-challenge for details.

Specifies client-originated claims to include in the token request. Unlike WithClaims (for server-issued claims challenges), tokens acquired with client claims are cached and keyed on the claims value. Different claim values produce separate cache entries. Use stable, non-dynamic claim values to avoid cache fragmentation.

Specifies if the client application should ignore access tokens when reading the token cache. New tokens will still be written to the application token cache. By default the token is taken from the application token cache (forceRefresh=false)