Microsoft.Identity.Client.AcquireTokenOnBehalfOfParameterBuilder
public sealed class AcquireTokenOnBehalfOfParameterBuilder : AbstractConfidentialClientAcquireTokenParameterBuilder<AcquireTokenOnBehalfOfParameterBuilder>
Builder for AcquireTokenOnBehalfOf (OBO flow)
See https://aka.ms/msal-net-on-behalf-of
public AcquireTokenOnBehalfOfParameterBuilder WithCcsRoutingHint(string userObjectIdentifier, string tenantIdentifier)
To help with resiliency, the AAD backup authentication system operates as an AAD backup.
This will provide the AAD backup authentication system with a routing hint to help improve performance during authentication.
To help with resiliency, the AAD backup authentication system operates as an AAD backup.
This will provide the AAD backup authentication system with a routing hint to help improve performance during authentication.
Specifies if the client application should ignore access tokens when reading the token cache.
New tokens will still be written to the token cache.
By default the token is taken from the the user token cache (forceRefresh=false)
Applicable to first-party applications only, this method also allows to specify
if the x5c claim should be sent to Azure AD.
Sending the x5c enables application developers to achieve easy certificate roll-over in Azure AD:
this method will send the certificate chain to Azure AD along with the token request,
so that Azure AD can use it to validate the subject name based on a trusted issuer policy.
This saves the application admin from the need to explicitly manage the certificate rollover
(either via portal or PowerShell/CLI operation). For details see https://aka.ms/msal-net-sni