Add Azure AD B2C auth provider compatibility

[Leon-Sam]

Changes:

🚀 Azure AD B2C authentication is now supported

📖 The Azure AD authentication section of the documentation has been amended to provide tips for Azure AD B2C setup

🐛 Fixed a bug in the current form of Redwood's Azure AD auth would cause the MSAL library to lock up with a "interaction_in_progress" error

Logic behind code changes:

The existing Azure AD auth provider implementation almost worked perfectly with the Azure B2C product. 2 small changes had to be made.

1. Added an additional environmental variable for JWT issuer check

I made some small tweaks to the existing Microsoft AD Auth provider to allow for compatibility with Microsoft's Azure AD B2C product. It required some small tweaks to allow for alternative strings to be used during the JWT verification process (Specific Azure AD B2C thing). The changes should be fully backwards compatible with previous Azure AD installs.

2. Removed logic to search browser url for "#code="

Previously when the AuthClient found a "#code=" in the url on mount, then it would trigger the MSAL to handle the redirect. This was brittle for 2 reasons.

1. At least in the B2C Auth Code redirect back from the hosted sign in page, the code parameter format was "&code=" not "#code=".
2. This also caused the "interaction_in_progress" error mentioned previously. If handleRedirectPromise() gets fired everytime AuthClient mounts, then the MSAL library has a chance to clear it's own caches/states before letting the user call any MSAL functions. Official MS Docs also reccomends firing the function on every page load, and then handle the token

Testing Method:

I made a throwaway app on my end with Azure AD B2C credentials/user flows.
The test app can:

• Redirect to hosted Microsoft hosted signin/signup/pw-reset page
• Successfully sign-up/sign-in a new user with successful redirect back to app
• Properly logout
• inspected the {currentUser} from useAuth(), and all the configured claims/data from the Azure B2C User flow is present.

Request:

@jeliasson Could you make sure that this PR doesn't break any Azure AD integrations you already have?

[netlify]

✅ Deploy Preview for redwoodjs-docs ready!

Name	Link
🔨 Latest commit	0ede820
🔍 Latest deploy log	https://app.netlify.com/sites/redwoodjs-docs/deploys/62b34062ad9e5d00098d62d3
😎 Deploy Preview	https://deploy-preview-5781--redwoodjs-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[jeliasson]

Hi and well done, Leon! 👏

1. Does this come with breaking changes? (At a first glance, it does not look like it)
2. Has this been tested with Redwood's Auth playground?
3. There is some linting warnings. I suggest those be fixed first. What do you think?

@dac09 @dthyresson Once above is addressed, can we bring it the PR to main for a canary build? I could update the Auth Playground, unless we want to keep it canary free, and a production app.

[Leon-Sam]

Hey @jeliasson

1. There should be no breaking changes.
2. I just opened up a new PR for the Auth playground and got it working at facevalue. See that specific PR for details
3. Totally forgot about the linter. I just pushed those updates.

[jeliasson]

LGTM.
/cc @dac09 @dthyresson

[dthyresson]

Thanks @Leon-Sam for this!

I looked at your auth playground PR and see that you have it working. We can help in that PR to define some enviers, etc.

Could you resolve the conflicts and I have sorted the PR to run CI now.

Again, many thanks.

[Leon-Sam]

Just fixed the merge conflicts from main due the Auth documentation change. Let me know if I need any other tweaks.

[jeliasson]

I just tried 2.0.1-canary.58 which yields this error.

[dac09]

I just tried 2.0.1-canary.58 which yields this error.

@jeliasson I think this is unrelated, you node_modules probably just needs a clean and reinstall - haven't seen that one in a while! This was an issue in cross-undici-fetch that was resolved a while ago.

[jeliasson]

@dac09 Yeah me too. I just catched David during the RW Office Hours to let him know about it. I did the classic delete/install, but that did not do the trick this time. Currently pushing it to the dev enviorment to see if it yields the same issue here, otherwise borked local env.

[dthyresson]

I just catched David during the RW Office Hours

Right @jeliasson and I just spoke and I knew I recognized that "splice" message from awhile back.

See: #5526

Fwiw I just came across this issue and deleting the lock file seemed to fix it for me too

[jeliasson]

Lockfile was the baddie. Thanks. I'll try out new canary a bit later.

[jeliasson]

From what I can see, canary 2.0.1-canary.59 seems to be working well. Once we have the PR merged to the auth playground, I'll be happy to further validate it there. Let me know.

Thanks @Leon-Sam @dthyresson @dac09