-
Notifications
You must be signed in to change notification settings - Fork 330
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
GetAuthorizationRequestUrlParameterBuilder.ExecuteAsync() method returns wrong datatype #1184
Comments
@bgavrilMS fyi |
Fix will be available in 4.0 release |
@Rick-Kirkham Fixed in MSAL 4.0.0 release |
@jennyf19 Has 4.0 officially GAed or is it still preview/beta? |
@Rick-Kirkham We actually GA'ed w/3.0.8, so 4.0 is also GA. |
??? You GAed two versions at once? Why? I can't make sense of that. |
@Rick-Kirkham we GA'ed w/3.0.8 and 4.0 is not in preview or beta. We GA'ed at the beginning of May. |
@jennyf19 Just last week I installed the NuGet package for MSAL in a Visual Studio project. The most recent version available was 3.0.8. There was no 4.0. |
@Rick-Kirkham
|
@jmprieur |
@Rick-Kirkham It's available now msal 4.0.0 |
Got it. Thanks. |
Which Version of MSAL are you using ?
Latest 3.x.x
Platform
net45
What authentication flow has the issue?
Is this a new or existing app?
c. This is a new app
Repro
Expected behavior
According to ConfidentialClientApplication.GetAuthorizationRequestUrl, the method:
So, in the code in Repro above, the object returned by
GetAuthorizationRequestUrlParameterBuilder.ExecuteAsync()
should return a URL or an object with a property that is a URL.Actual behavior
The
GetAuthorizationRequestUrlParameterBuilder.ExecuteAsync()
method returns anAuthorizationResult
which is not a URL and has no property with a URL in it.The text was updated successfully, but these errors were encountered: