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

Missing sendx5c flag in AcquireTokenSilentAsync #1149

Closed
henrik-me opened this issue May 14, 2019 · 1 comment
Closed

Missing sendx5c flag in AcquireTokenSilentAsync #1149

henrik-me opened this issue May 14, 2019 · 1 comment
Assignees
Milestone

Comments

@henrik-me
Copy link
Contributor

henrik-me commented May 14, 2019

Reported issue for ADAL which needs addressing in MSAL to enable move to MSAL: AzureAD/azure-activedirectory-library-for-dotnet#1568

Which Version of ADAL are you using ?
3.19.8

Which platform has the issue?
net45

What authentication flow has the issue?
Web App OBO

Is this a new or existing app?
The app is in production, uses the same version of ADAL, but started seeing this issue

Expected behavior
Given that we can send the x5c via AcquireTokenAsync using a IClientAssertionCertificate overload, I would expect to be able to do the same with AcquireTokenSilentAsync, but this is not currently the case.

Actual behavior
The sendx5c flag is not available in any overload of AcquireTokenSilentAsync.

Possible Solution
Add the sendx5c flag to IClientAssertionCertificate overload of AcquireTokenSilentAsync

@jennyf19
Copy link
Collaborator

jennyf19 commented Jun 4, 2019

Fixed in MSAL 4.0.0 release

@jennyf19 jennyf19 closed this as completed Jun 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants