ClientSecretCredential 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.
Enables authentication to Azure Active Directory using a client secret that was generated for an App Registration. More information on how to configure a client secret can be found here: https://docs.microsoft.com/azure/active-directory/develop/quickstart-configure-app-access-web-apis#add-credentials-to-your-web-application
public class ClientSecretCredential : Azure.Core.TokenCredential
type ClientSecretCredential = class
inherit TokenCredential
Public Class ClientSecretCredential
Inherits TokenCredential
- Inheritance
Constructors
| ClientSecretCredential() |
Protected constructor for mocking. |
| ClientSecretCredential(String, String, String) |
Creates an instance of the ClientSecretCredential with the details needed to authenticate against Azure Active Directory with a client secret. |
| ClientSecretCredential(String, String, String, ClientSecretCredentialOptions) |
Creates an instance of the ClientSecretCredential with the details needed to authenticate against Azure Active Directory with a client secret. |
| ClientSecretCredential(String, String, String, TokenCredentialOptions) |
Creates an instance of the ClientSecretCredential with the details needed to authenticate against Azure Active Directory with a client secret. |
Methods
| GetToken(TokenRequestContext, CancellationToken) |
Obtains a token from the Azure Active Directory service, using the specified client secret to authenticate. 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 a token from the Azure Active Directory service, using the specified client secret to authenticate. 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
Feedback
Submit and view feedback for