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
Azure SDK for .NET
피드백
https://aka.ms/ContentUserFeedback
출시 예정: 2024년 내내 콘텐츠에 대한 피드백 메커니즘으로 GitHub 문제를 단계적으로 폐지하고 이를 새로운 피드백 시스템으로 바꿀 예정입니다. 자세한 내용은 다음을 참조하세요.다음에 대한 사용자 의견 제출 및 보기