Closed peombwa closed 3 days ago
@peombwa Could you use ChainedTokenCredential instead of EnvironmentCredential
? With it, you can form your own custom credential chain, thereby excluding UsernamePasswordCredential
.
//cc: @schaabs
@peombwa Could you use ChainedTokenCredential instead of
EnvironmentCredential
? With it, you can form your own custom credential chain, thereby excludingUsernamePasswordCredential
.
Thanks for the response. Using ChainedTokenCredential
would require us to write our own implementation of environment variable credential as we will need to read the environment variables ourselves to set them to the right TokenCredential
classes. It also adds a maintenance cost as we will need to keep up with new environment variables added in the future.
Using the existing EnvironmentCredential
implementation works well for us, we'd just like to have the option to exclude UsernamePasswordCredential
from the list of TokenCredentials used to acquire a token. This would be something like Exclude*
properties in DefaultAzureCredentialOptions.
Hi @peombwa, we deeply appreciate your input into this project. Regrettably, this issue has remained unresolved for over 2 years and inactive for 30 days, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.
Library name
Azure.Identity
Please describe the feature.
EnvironmentCredential
uses aClientSecretCredential
,ClientCertificateCredential
, orUsernamePasswordCredential
to perform the authentication. For our scenario, we don't supportUsernamePasswordCredential
and we strongly encourage customers not to use password grant type for auth. To support our scenario, it would be nice to provide an option to excludeUsernamePasswordCredential
fromEnvironmentCredential
as we do not support it.