-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Adding ClientCertificateCredential to Azure.Idenity #6636
Conversation
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.
Looks good to me.
|
||
request.Method = HttpPipelineMethod.Post; | ||
|
||
request.Headers.SetValue("Content-Type", "application/x-www-form-urlencoded"); |
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.
nit: Is there a member in Azure.Core
for form types? If not, maybe we should consider adding it there to keep building that out.
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.
Agreed. I've added and issue to track this, #6646. I'll make this change in a separate PR since it's a change to Azure.Core and requires rebuilding everything.
@@ -23,7 +25,8 @@ internal class IdentityClient | |||
private readonly IdentityClientOptions _options; | |||
private readonly HttpPipeline _pipeline; | |||
private readonly Uri ImdsEndptoint = new Uri("http://169.254.169.254/metadata/identity/oauth2/token"); | |||
private readonly string MsiApiVersion = "2018-02-01"; | |||
private const string MsiApiVersion = "2018-02-01"; |
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.
Irrelevant to this PR but this is the IMDS version. App Service MSI will 400 if you use it there (expects 2017-09-01).
No description provided.