Aracılığıyla paylaş

InteractiveBrowserCredential Class

  • Reference

Definition

Namespace:
Azure.Identity
Assembly:
Azure.Identity.dll
Package:
Azure.Identity v1.13.1
Package:
Azure.Identity v1.13.0-beta.2
Source:
InteractiveBrowserCredential.cs
Source:
InteractiveBrowserCredential.cs

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
Object
TokenCredential
InteractiveBrowserCredential
Implements
Azure.Core.ISupportsProofOfPossession

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)

Silently obtains an AccessToken for a user account 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)

Silently obtains an AccessToken for a user account 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)

Silently obtains an AccessToken for a user account 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)

Silently obtains an AccessToken for a user account 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