Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQ] Azure.Identity/DAC should log ClientId for user-assigned managed identities #1978

Open
christothes opened this issue Jan 8, 2025 · 0 comments
Labels
Azure.Identity The azure_identity crate Client This issue points to a problem in the data-plane of the library. feature-request This issue requires a new behavior in the product in order be resolved.

Comments

@christothes
Copy link
Member

Library name

Azure.Identity

Please describe the feature.

Today we don't directly log the ClientId when selecting a user-assigned identity to use with ManagedIdentityCredential. Customers instead need to change verbosity and dig into MSAL logs instead which isn't nearly as obvious.

We expect multiple user-assigned managed identity scenarios to become much more common with future Aspire work, so surfacing the ClientId will make it a lot easier to spot config problems (i.e., am I trying to access Storage with an identity scoped to just reading photos? or the identity created for the logical container? or ...?).

@christothes christothes added Azure.Identity The azure_identity crate Client This issue points to a problem in the data-plane of the library. feature-request This issue requires a new behavior in the product in order be resolved. labels Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure.Identity The azure_identity crate Client This issue points to a problem in the data-plane of the library. feature-request This issue requires a new behavior in the product in order be resolved.
Projects
Status: Untriaged
Development

No branches or pull requests

1 participant