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
While launching the Admin Portal it tries to connect as: api://{Constants.ApiAppUrlGuid}/access_as_user.
api://{Constants.ApiAppUrlGuid}/access_as_user
After running the Deploy script i have just a "access_as_use" (without final r. See:
What can i do now?
Can i just change the code, from
builder.Services.AddMsalAuthentication(options => { builder.Configuration.Bind("AzureAd", options.ProviderOptions.Authentication); options.ProviderOptions.DefaultAccessTokenScopes.Add($"api://{Constants.ApiAppUrlGuid}/access_as_user"); });
to
builder.Services.AddMsalAuthentication(options => { builder.Configuration.Bind("AzureAd", options.ProviderOptions.Authentication); options.ProviderOptions.DefaultAccessTokenScopes.Add($"api://{Constants.ApiAppUrlGuid}/access_as_use"); });
The text was updated successfully, but these errors were encountered:
No branches or pull requests
While launching the Admin Portal it tries to connect as:
api://{Constants.ApiAppUrlGuid}/access_as_user
.After running the Deploy script i have just a "access_as_use" (without final r. See:
What can i do now?
Can i just change the code, from
builder.Services.AddMsalAuthentication(options => { builder.Configuration.Bind("AzureAd", options.ProviderOptions.Authentication); options.ProviderOptions.DefaultAccessTokenScopes.Add($"api://{Constants.ApiAppUrlGuid}/access_as_user"); });
to
builder.Services.AddMsalAuthentication(options => { builder.Configuration.Bind("AzureAd", options.ProviderOptions.Authentication); options.ProviderOptions.DefaultAccessTokenScopes.Add($"api://{Constants.ApiAppUrlGuid}/access_as_use"); });
The text was updated successfully, but these errors were encountered: