-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Description
@Pilchie
Hello, I have built a Blazor Client web assembly application in .net 5 and I'm able to sign in with azure ad. I am trying to upgrade from MSAL 3.2.1 -> 5.0.4 and after I do I am no longer able to sign in.
Before the upgrade, clicking login opens the /authorize with: https://login.microsoftonline.com/9bcaf044-1667-4506-a200-067c204b3ca3/oauth2/v2.0/authorize?response_type=id_token&scope=openid profile&client_id=4618572a-96a4-45da-ad7e-30a457ae69e9&redirect_uri=https://forgedev.cwbgroup.org/authentication/login-callback&state=db6593ef-9989-4329-9996-97c78038d47d|CKcySrCAn4v6-idFwCpSbDwIngZ4Nbai-yvDpd1R274&nonce=b3edec00-d325-4657-8246-f8ca15e5dff7&client_info=1&x-client-SKU=MSAL.JS&x-client-Ver=1.2.1&client-request-id=ad3530b2-e9cc-4262-bb18-d12fefc5042e&response_mode=fragment
After the upgrade of the package, the /authorize looks like this and fails to authenticate due to cors issue:
I can tell that after the upgrade, the response_type=code. Why is that the case? My application is a blazor CLIENT application and has no server!
How can I upgrade the MSAL and keep response_type=id_token? Thanks