We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Which version of Microsoft Identity Web are you using? 1.3.0
Where is the issue?
Repro
Call AccountController.Challenge with a loginHint.
AccountController.Challenge
var your = (code) => here;
Expected behavior The call to AAD should show login_hint
Actual behavior It's not
Possible solution Change the value of the LoginHint to login_hint
login_hint
microsoft-identity-web/src/Microsoft.Identity.Web/Constants/Constants.cs
Line 15 in a4bde02
Same for DomainHint which should value domain_hint
domain_hint
Additional context / logs / screenshots Add any other context about the problem here, such as logs and screenshots.
The text was updated successfully, but these errors were encountered:
@jennyf19 do you agree? See also https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/blob/6e7a53e241e4566998d3bf365f03acd0da699a31/src/Microsoft.IdentityModel.Protocols.OpenIdConnect/OpenIdConnectParameterNames.cs#L55
Sorry, something went wrong.
Included in 1.4 Release.
jennyf19
No branches or pull requests
Which version of Microsoft Identity Web are you using?
1.3.0
Where is the issue?
Repro
Call
AccountController.Challenge
with a loginHint.Expected behavior
The call to AAD should show login_hint
Actual behavior
It's not
Possible solution
Change the value of the LoginHint to
login_hint
microsoft-identity-web/src/Microsoft.Identity.Web/Constants/Constants.cs
Line 15 in a4bde02
Same for DomainHint which should value
domain_hint
Additional context / logs / screenshots
Add any other context about the problem here, such as logs and screenshots.
The text was updated successfully, but these errors were encountered: