InteractiveBrowserCredential Class
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
A TokenCredential implementation which launches the system default browser to interactively authenticate a user, and obtain an access token. The browser will only be launched to authenticate the user once, then will silently acquire access tokens through the users refresh token as long as it's valid.
public class InteractiveBrowserCredential : Azure.Core.TokenCredential
public class InteractiveBrowserCredential : Azure.Core.TokenCredential, Azure.Core.ISupportsProofOfPossession
type InteractiveBrowserCredential = class
inherit TokenCredential
type InteractiveBrowserCredential = class
inherit TokenCredential
interface ISupportsProofOfPossession
Public Class InteractiveBrowserCredential
Inherits TokenCredential
Public Class InteractiveBrowserCredential
Inherits TokenCredential
Implements ISupportsProofOfPossession
- Inheritance
- Implements
Constructors
InteractiveBrowserCredential() |
Creates a new InteractiveBrowserCredential with the specified options, which will authenticate users. |
InteractiveBrowserCredential(InteractiveBrowserCredentialOptions) |
Creates a new InteractiveBrowserCredential with the specified options, which will authenticate users with the specified application. |
Methods
Authenticate(CancellationToken) |
Interactively authenticates a user via the default browser. |
Authenticate(PopTokenRequestContext, CancellationToken) |
Interactively authenticates a user via the default browser. The resulting AuthenticationRecord will automatically be used in subsequent calls to GetToken(TokenRequestContext, CancellationToken). |
Authenticate(TokenRequestContext, CancellationToken) |
Interactively authenticates a user via the default browser. The resulting AuthenticationRecord will automatically be used in subsequent calls to GetToken(TokenRequestContext, CancellationToken). |
AuthenticateAsync(CancellationToken) |
Interactively authenticates a user via the default browser. The resulting AuthenticationRecord will automatically be used in subsequent calls to GetTokenAsync(TokenRequestContext, CancellationToken). |
AuthenticateAsync(PopTokenRequestContext, CancellationToken) |
Interactively authenticates a user via the default browser. |
AuthenticateAsync(TokenRequestContext, CancellationToken) |
Interactively authenticates a user via the default browser. |
GetToken(PopTokenRequestContext, CancellationToken) |
Obtains an AccessToken token for a user account silently if the user has already authenticated, otherwise the default browser is launched to authenticate the user. Acquired tokens are cached by the credential instance. Token lifetime and refreshing is handled automatically. Where possible, reuse credential instances to optimize cache effectiveness. |
GetToken(TokenRequestContext, CancellationToken) |
Obtains an AccessToken token for a user account silently if the user has already authenticated, otherwise the default browser is launched to authenticate the user. Acquired tokens are cached by the credential instance. Token lifetime and refreshing is handled automatically. Where possible, reuse credential instances to optimize cache effectiveness. |
GetTokenAsync(PopTokenRequestContext, CancellationToken) |
Obtains an AccessToken token for a user account silently if the user has already authenticated, otherwise the default browser is launched to authenticate the user. Acquired tokens are cached by the credential instance. Token lifetime and refreshing is handled automatically. Where possible, reuse credential instances to optimize cache effectiveness. |
GetTokenAsync(TokenRequestContext, CancellationToken) |
Obtains an AccessToken token for a user account silently if the user has already authenticated, otherwise the default browser is launched to authenticate the user. Acquired tokens are cached by the credential instance. Token lifetime and refreshing is handled automatically. Where possible, reuse credential instances to optimize cache effectiveness. |
Applies to
Commenti e suggerimenti
https://aka.ms/ContentUserFeedback.
Presto disponibile: Nel corso del 2024 verranno gradualmente disattivati i problemi di GitHub come meccanismo di feedback per il contenuto e ciò verrà sostituito con un nuovo sistema di feedback. Per altre informazioni, vedereInvia e visualizza il feedback per