Jo Arroyo
Jo Arroyo
@LastTribunal We are aware of this usage, but this requires some changes to the library that will be addressed in a future version of MSAL Angular.
@doug-williamson I see that you've set the `MsalGuard` on the home route. Just curious if you've seen or tried [our solution for handling guarding the home route](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-angular/docs/FAQ.md#how-do-i-log-users-in-when-they-hit-the-application)?
@doug-williamson I am referring to these instructions: > For those using the PathLocationStrategy, we recommend: > - Setting the MsalGuard on your initial page > - Set your redirectUri to...
@doug-williamson Apologies, this fix has not yet been prioritized. We will update this thread when we have a PR.
@yksht Can you please open a new issue [here](https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/new/choose) with your requested fix? This will help with our feature tracking and prioritization. Thank you.
@bpossolo Thanks for your detailed feedback. Have you taken a look at any of the PRs linked on the [previous issue](https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/5748#issuecomment-1466947122) to see whether those documentation upgrades addressed your concerns?...
@grosch-intl @kaangoksal @Drsela Are you using the Windows Account extension to get tokens? Is this extension installed in Chrome and not in Edge? There is a known bug on the...
@ChrisForgie You are right in that the current `MsalInterceptor` does not have a custom header check, and may not fit your particular use case. However, this is an interesting enhancement...
@jesben To clarify, you are looking for service worker support? We don't currently have any examples of this, but we will track this feature request internally and update when it...