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

Use of Azure Managed Identity for reading secrets from Azure Key Vault #539

Closed
gsvkarteek opened this issue Aug 21, 2023 · 4 comments
Closed

Comments

@gsvkarteek
Copy link

gsvkarteek commented Aug 21, 2023

Is your feature request related to a problem? Please describe.
Considering the organization's security stance, user-friendliness, and resource segregation standpoint, the recommendation aligns with opting for Managed Identities. However, the use of a Service Principal (SPN) is necessary for the ArgoCD Vault Plug-In to retrieve secrets from Key Vault

Describe the solution you'd like
Enable means to connect Vault Plug-In through Managed Identitiy.

@KevinDW-Fluxys
Copy link

As an addition, it would also be nice to make the documentation more clear about this instead of simply linking to the Microsoft docs. When you follow the Microsoft docs (link) it looks like managed identity should work.

@YvesZelros
Copy link
Contributor

YvesZelros commented Aug 31, 2023

Duplicate of #421

@Stolz
Copy link

Stolz commented Nov 11, 2023

The Plugin docs just mention a link to the Azure docs. The Azure docs state

No credentials are needed for managed identity authentication. The application must be running on an Azure resource configured to use managed identities.

Which is not working when using the plugin (using other plugins works fine). That means the plugin must be sending a request with different parameters than the one expected by Azure.

@werne2j
Copy link
Member

werne2j commented May 28, 2024

@werne2j werne2j closed this as completed May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants