Azure / Azure/static-web-apps

Switching on Enterprise Edge breaks Azure AD B2C auth

Open
#704 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
346
Forks
67
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**

When an existing Static Web App using Azure AD B2C for its auth provider and a custom domain has Enterprise Edge switched on, it attempts to redirect the user to the wrong address - wonderful-pebble-blah.origin.staticwebapps etc. This flags an error with Azure AD B2C for not being in the allowed list or redirect URI's - when added to that list the redirect simply sits there and does nothing.

**To Reproduce**
Steps to reproduce the behavior:
1. Set up a static web app with Custom Domain and Azure AD B2C as a custom auth provider
2. Click on Enterprise Edge
3. Attempt to login using the /login route
4. Shows error about redirect URI not being allowed

**Expected behavior**
Azure AD B2C login to continue to work using the custom domain registered with the static web app when Enterprise Edge is switched on
**Screenshots**
![image](https://user-images.githubusercontent.com/75691669/151360401-ec5d3e5f-83be-4df7-973e-1aa9c3465466.png)

**Device info (if applicable):**
Windows
Chrome
Latest

**Additional context**
I switched off the Enterprise Edge feature and the login worked again after ten minutes. It may well also be that this isn't a bug as such, but that I just need to add some more DNS records or something. In which case I guess its more of a documentation thing!

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.