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

Create an Amazing Dev-time Credential Experience for Azure.Identity #6602

Closed
4 of 7 tasks
joshfree opened this issue Jan 3, 2020 · 9 comments
Closed
4 of 7 tasks
Assignees
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library.

Comments

@joshfree
Copy link
Member

joshfree commented Jan 3, 2020

Tracking issue for feature work specific to Developer-time Azure.Identity Credential Experience

  • Bring back file based auth for Management Plane: https://docs.microsoft.com/en-us/dotnet/azure/dotnet-sdk-azure-authenticate?view=azure-dotnet#mgmt-auth AZURE_AUTH_LOCATION (see Support AZURE_AUTH_LOCATION azure-sdk-for-net#9312) (@ellismg driving design requirements)

  • Add Support for writing back to the SharedTokenCache (@schaabs driving design requirements)

  • Add Linux and Mac SharedTokenCache Support (@jianghaolu driving design requirements)

  • Improve DefaultAzureCredential/ChainedTokenCredential - e.g., tell me what Credential I'm using for dev debug scenarios (@catalinaperalta driving design requirements)

  • Have ManagedIdentityCredential utilize the AZURE_CLIENT_ID environment variable. To allow user assigned identities to utilize DefaultAzureCredential (@jongio driving implementation with vendor team)

  • Have TokenCredentialOptions utilize AZURE_AUTHORITY_HOST environment variable. To allow other clouds to use DefaultAzureCredential. (@jongio driving implementation with vendor team)

  • CliCredentials / Better support for dev creds: CLI, PSH, VS, VS CODE, VS ONLINE, CLOUD SHELL

    • devCredentials (@schaabs driving design requirements)
    • CliCredential (@jongio driving implementation with vendor team)
@chlowell
Copy link
Member

Closing this as complete, we've either implemented or decided not to implement each item

@weinong
Copy link

weinong commented Feb 4, 2022

Closing this as complete, we've either implemented or decided not to implement each item

@chlowell, so it is implemented or not? 😂

@chlowell
Copy link
Member

chlowell commented Feb 4, 2022

Are you interested in a particular item? Of the ones above, these are implemented:

  • authentication via Azure CLI, Cloud Shell
  • better error messages for DefaultAzureCredential and ChainedTokenCredential
  • credentials observe AZURE_AUTHORITY_HOST

@weinong
Copy link

weinong commented Feb 4, 2022

@chlowell we need token cache support for interactive browser credential. Is it implemented?

@chlowell
Copy link
Member

chlowell commented Feb 4, 2022

Depends on the sort of cache you want. That credential has an in-memory cache today. We plan to add an optional persistent cache but have no ETA for that.

@weinong
Copy link

weinong commented Feb 4, 2022

any chance to accelerate that? i'm the maintainer of https://github.com/Azure/kubelogin which is a client side tool just like az cli. in memory cache will not help

@chlowell
Copy link
Member

chlowell commented Feb 4, 2022

I really don't know when we could ship persistent caching. We're waiting on AzureAD/microsoft-authentication-library-for-go#58. I'll take your comment as a vote for increasing its priority and pass it along to the MSAL team (feel free to comment on the MSAL issue as well). I expect they will still want to implement their current high priority features first though.

@weinong
Copy link

weinong commented Feb 4, 2022

should we open an issue for this particular feature?

@chlowell
Copy link
Member

chlowell commented Feb 4, 2022

We're already tracking it with #16643

@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Azure.Identity Client This issue points to a problem in the data-plane of the library.
Projects
None yet
Development

No branches or pull requests

5 participants