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

[Feature] Azure CLI Credential Provider #537

Open
rwoll opened this issue Dec 5, 2024 · 2 comments
Open

[Feature] Azure CLI Credential Provider #537

rwoll opened this issue Dec 5, 2024 · 2 comments

Comments

@rwoll
Copy link
Member

rwoll commented Dec 5, 2024

In order to avoid any use of PATs on macOS, I'd like to have the Credential Provider get tokens from the azure CLI as that's already logged in and have behavior that's generally inline with the DefaultAzureCredential provider class.

On Windows, the authentication broker works great and PAT-less, but on macOS it looks like there's not a good non-PAT option.

@embetten
Copy link
Contributor

embetten commented Dec 6, 2024

Can you describe your scenario further? Are you trying to use a managed identity as outlined in the DefaultAzureCredential docs or are you a user on a local macOS machine running into device code flow?

Native managed identity is currently supported with the ARTIFACTS_CREDENTIALPROVIDER_FEED_ENDPOINTS listed in our env variables.

@rwoll
Copy link
Member Author

rwoll commented Dec 6, 2024

are you a user on a local macOS machine running into device code flow?

I'm a user on a local macOS screen. I'm not sure if I'm using Device Code Flow. I'm using the default when I do dotnet restore --interactive.

When I do this it kicks off an auth flow in my browser but then it ends up generating a PAT in ADO, and I'd like to avoid any PATs like it does on Windows.

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