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

Adjusting to Azure policy change related to client_id and client_secret ? #740

Open
fabiansalamo opened this issue Apr 9, 2024 · 2 comments

Comments

@fabiansalamo
Copy link

Hello, due to recent Azure policy changes, we will not be allowed to user client_id and client_secret, and be forced to change to MSI. Is there a recommendation on how to authenticate or maybe a plan to update oauthenticator.azuread to support MSI? Thank you.

Copy link

welcome bot commented Apr 9, 2024

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
welcome
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

@consideRatio
Copy link
Member

From this link I learned that MSI is now called Managed identities for Azure resources, but I've not read up on that yet.

Managed identities for Azure resources is the new name for the service formerly known as Managed Service Identity (MSI).

Do you have a link to the policy change?

@consideRatio consideRatio changed the title Issue on page /reference/api/gen/oauthenticator.azuread.html Adjusting to Azure policy change related to client_id and client_secret ? Sep 1, 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

2 participants