Azure Authentication, client_id is null and scope now contains client_id

Copper Contributor
Hi all, Doing a Dotnet upgrade for a company project and we're having a strange issue with the auth where in the redirect url to microsoft the scope has been set equal to the client id and the client id is null. https://login.microsoftonline.com/common/oauth2/v2.0/authorize?response_type=id_token&scope=b7f580da... This is only happening after the dotnet upgrade from 3.1 core to 6.0 
 
Any ideas why that would be happening?
 
 
Jack_McBride_0-1698072179103.png

 

 
Jack_McBride_1-1698072179124.png
0 Replies