-
Notifications
You must be signed in to change notification settings - Fork 34
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
[provider] Fix OIDC support #2086
Conversation
Add parameters to the client configuration used by the provider so that the provider supports OIDC authentication.
Does the PR have any schema changes?Looking good! No breaking changes found. Looking good! No API changes found. |
Fixes #1324 |
@pgavlin awesome! Just the issue I started running into a couple of days ago. Any Idea when this will be released? |
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.
This depends on moving the core authentication library from ADAL to MSAL. @thomas11 has made good progress in this area but there's still more investment needed to get it over the line yet.
Feel free to close this @pgavlin and we'll re-integrate this work once the core auth libray has been upgraded |
Any luck on this front, would be awesome to use MSI w/ workload identity federation support with Pulumi! |
Hi @illusional, there are some complications to work through, but the good news is we're working on it. |
superseded by #2320 |
Add parameters to the client configuration used by the provider so that the provider supports OIDC authentication.