Configure B2C sample to work with PathLocationStrategy instead of HashLocationStrategy

Library

• @azure/msal-angular@2.0.0-alpha.5

Description

How can I replicate the angular11-b2c-sample project without turning on the HashLocationStrategy ?

The issue I’m facing is that redirect URIs from Azure AD B2C always start with # which misses up the application because I’m using PathLocationStrategy instead of HashLocationStrategy.

I can set the useHash: false instead of useHash: true like this:

RouterModule.forRoot(routes, { useHash: false, // Don’t perform initial navigation in iframes initialNavigation: !isIframe ? ‘enabled’ : ‘disabled’, }),

But still, how can I interact with the redirect URIs starting with # ?

Source

• Customer request

[jo-arroyo]

@eluchsinger Thank you for your feedback regarding our samples. As we aim to provide samples that cover a wide range of use cases, we will look into updating our samples to demonstrate using the PathLocationStrategy as well as the HashLocationStrategy. We are also currently working on improving our documentation with better guidance regarding the nuances of using each strategy.

In the meantime, if you are wanting help with your app, it would be great if you either send us a link to your repo, or open an issue with your configuration, usage, MSAL version and logs. We would be happy to help figure out why the redirects are not working for you.

[jo-arroyo]

@shadyabouelmakarem PathLocationStrategy is fully supported by msal-angular. However, MSAL does not support redirectUris that have a hash, because that is where the response from the server is. MSAL will automatically handle parsing the response hash for you.

But still, how can I interact with the redirect URIs starting with # ?

Could you clarify what you mean by this?