Environment:
Umbraco version: 17.0.0
Azure host application: https://blah-blah-blah.azurewebsites.net
Client qa host: https://qa.clientdomain.com
(Both domains point to the same application)
Front end service: Cloudflare
“UmbracoApplicationUrl”: “https://qa.clientdomain.com”
“BackOfficeHost”: “https://qa.clientdomain.com”
Website hostnames in CMS
https://qa.clientdomain.com/en (english)
https://qa.clientdomain.com/de (german)
https://blah-blah-blah.azurewebsites.net/en (english)
https://blah-blah-blah.azurewebsites.net/de (german)
Description of the issue:
- After logging in to the backoffice on “ “https://qa.clientdomain.com” the site redirects to “https://blah-blah-blah.azurewebsites.net/umbraco”.
- Qa.clientdomain.com is protected by Cloudflare, which we use to manage access for the client to view the site and access the CMS.
- The problem is that “https://blah-blah-blah.azurewebsites.net” is protected by IP restriction, which is not a feasible method for managing the Client access.
- The front end behaviour is fine - i.e. if you come in on “https://qa.clientdomain.com” you stay on “https://qa.clientdomain.com”
Expected behavior:
BackOffice should Stay on “https://qa.clientdomain.com” after the login process
Steps to reproduce:
Run Umbraco ASP.NET site on azurewebsites.
Create Cloudflare route through to this site using a client subdomain
Set the settings in appsettings.json/CMS host names
Try to access the Umbraco BackOffice via https://qa.clientdomain.com
*** HugeDomains keeps rewriting this post WTF!