-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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 managed identity with OpenID Connect for Azure login #2182
base: staging
Are you sure you want to change the base?
Conversation
Signed-off-by: Simon Zhao <[email protected]>
32c1f43
to
01fbea5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SimonYansenZhao I added the federated credential, let me know if it works
@SimonYansenZhao it seems it is working now. I had to go to the Azure portal and add a federated credential with the name of your branch. I tried with the pull request option, and didn't work, and tried to add
Replace {application-id} with your Azure AD application's object ID and {access-token} with a valid Microsoft Graph access token with the required permissions. Request Body Example One unkonwn still is how to enable this solution to execute the nightly builds in staging and main. |
There is a new error, but not of authentication:
|
Not sure what's going on. I downloaded the artifact generated by the test, and did find std_log.txt in it. 🤣 |
Ah, I see. This PR does not trigger the workflow, so manual triggering does not match the subject |
Signed-off-by: Simon Zhao <[email protected]>
Signed-off-by: Simon Zhao <[email protected]>
Signed-off-by: Simon Zhao <[email protected]>
Signed-off-by: Simon Zhao <[email protected]>
Description
This PR resolves the issue #2171 by updating the testing workflows to use the Azure managed identity with OpenID Connect for login.
Related Issues
References
Checklist:
git commit -s -m "your commit message"
.staging branch
AND NOT TOmain branch
.