Add support for more AAD auth credentials
See original GitHub issueIs your feature request related to a problem? Please describe.
Currently the AAD auth only support ClientSecretCredential
, ClientCertificateCredential
and ManagedIdentityCredential
providers but the Azure.Identity library allows for more providers which are usually used during local development like Azure CLI or Visual Studio providers.
Describe the solution you’d like
Allow developers to use more providers from Azure.Identity through configuration in connection string or by allowing to pass their TokenCredential instance in options or constructor.
Additional context
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Azure Active Directory authentication overview
In Azure Active Directory (Azure AD), authentication involves more than just the verification of a username and password.
Read more >Azure AD authentication comes to Ubuntu Desktop 23.04
Ubuntu Desktop 23.04 is the first and only Linux distribution to enable native user authentication with Azure Active Directory (Azure AD).
Read more >Azure AD authentication troubleshooting: Known problems ...
This page is part of the Azure AD authentication troubleshooting guide: Known problems and solutions. This troubleshooting guide provides:.
Read more >Configure Azure AD OAuth2 authentication
To enable the Azure AD OAuth2, register your application with Azure AD. Log in to Azure Portal, then click Azure Active Directory in...
Read more >User Prompted for Credentials on Workspace URLs When ...
Users may be prompted for additional authentication when navigating to Citrix Workspace URLS if Workspace is configured to use a federated identity provider....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@qetza Sorry it is a bug. We will fix it in the next release.
1.10.0 released