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

Question: component-metadata-bundle.json #3013

Closed
guergabo opened this issue Jul 25, 2023 · 2 comments
Closed

Question: component-metadata-bundle.json #3013

guergabo opened this issue Jul 25, 2023 · 2 comments
Labels
kind/bug Something isn't working

Comments

@guergabo
Copy link

guergabo commented Jul 25, 2023

Ref:

Question

Shouldn't "Azure AD: Managed identity" auth profile have at least one required field? In general, is it safe to assume all fields in an auth profile are required?

@ItalyPaleAle

@guergabo guergabo added the kind/bug Something isn't working label Jul 25, 2023
@ItalyPaleAle
Copy link
Contributor

ItalyPaleAle commented Jul 25, 2023

@guergabo I cannot open the link you shared [REMOVED]

However, no, Azure AD when using MI doesn't have any required field. It's recommended to set the ClientID, but it's not always required (it may be required in some environments but not all). See docs: https://docs.dapr.io/developing-applications/integrations/azure/azure-authentication/authenticating-azure/#credentials-metadata-fields

@guergabo
Copy link
Author

Sorry, I pasted the wrong link! But, you already answered my question in the second paragraph. Thanks for the quick response!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants