-
Notifications
You must be signed in to change notification settings - Fork 237
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
review resource, scopes & permissions for TokenCredentials #61
Comments
The Go SDK is currently track 1-based and shouldn't be used as an example. Instead, we focus on track 2. See https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/identity/Azure.Identity/ for the .NET implementations, which is owned by the person driving identity across languages. For example, we don't currently expose scopes but there is an effort happening soon to do something along those lines. |
Pretty sure |
Fairly recently, |
I asked about public MyClient(Uri endpoint, TokenCredential credential, IEnumerable<string> scopes, MyClientOptions options)
: this(new ClientDiagnostics(options), HttpPipelineBuilder.Build(options, new BearerTokenAuthenticationPolicy(credential, scopes)), endpoint)
{
}
public MyClient(Uri endpoint, TokenCredential credential, IEnumerable<string> scopes)
: this(endpoint, credential, scopes, new MyClientOptions())
{
} For #520, I'm going to pass in |
Sounds reasonable for v1, but we'll need to be consistent eventually. I've opened #521 to track. |
#1493 moved to scopes. |
My first thought was that
resource
should be a list of scopes instead to match Microsoft Authentication Library MSAL v2, but I'm not sure.My guess is that
resource
here is modeled after he az command line and is the resource identifier. I think it becomes thescope
query param. In MSAL v2, it is a space delimited list.Links:
The text was updated successfully, but these errors were encountered: