nikPast

Sure, please note that I'm hiding client_id and tenant_id for policy. const configuration = { client_id: '**************************', redirect_uri: window.location.origin + '/authentication/callback', silent_redirect_uri: window.location.origin + '/authentication/silent-callback', // Optional activate silent-signin that...

I did it and in neither the cases I found any error

I can't see any active service worker. I tried with the official msal library and it works

Hi, I don't log events, to reproduce it just create a new app registration in azure and follow the basic authentication process to that application. Azure offers a free account...

I don't know if it can help, but through the callback url from azure it returns {code, state, sessionstate}, no issuer, no scopes in the url. Following the demo with...

The process is: Create a new app in azure portal. Retrieve clientID and tenantID from there. The authority url is: https://login.microsoftonline.com/tenantID/v2.0. you can use any scope including the one included...