-
Notifications
You must be signed in to change notification settings - Fork 39
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
Support for User Managed Identity #29
Comments
This issue is marked default for generating issues report. |
Hey @bahramr, is this in terms of credentials that are used as parameters to run the action? |
This issue is marked default for generating issues report. |
This issue is stale because it has been open for 7 days with no activity. |
Hi @kanika1894 , this is to use the User Managed Identity object ID as a parameter of the AZ Login action. That way you don't have to store any secret in the cloud. |
This issue is marked default for generating issues report. |
This issue is stale because it has been open for 7 days with no activity. |
@pulkitaggarwl some insights on this? |
Thanks @bahramr. MSI support is on our backlog. We are tracking it here: Azure/login#56 |
This issue is marked default for generating issues report. |
This issue is stale because it has been open for 7 days with no activity. |
As mentioned by @N-Usha , it's in backlog. So, closing this. |
In order to prevent the possible exposure of credentials in the Cloud, we need to use a User Managed Identity to run this action from a self-hosted agent deployed in Azure.
Is there a plan to implement that?
The text was updated successfully, but these errors were encountered: