V14: Allowing custom backoffice host with CORS policy

[elit0451]

Details

• Allows the backoffice to run from a different host than the API host if BackOfficeHost setting is configured:
  • by adding a CORS policy for the custom backoffice host - it respects the middleware order (placed after UseRouting(), but before UseAuthorization())

Test

Setup:

• In Umbraco.Web.UI.New.Client project create a file .env.local and add the following contents:

VITE_UMBRACO_USE_MSW=off # on = turns on MSW, off = disables all mock handlers
VITE_UMBRACO_API_URL=https://localhost:44339
VITE_UMBRACO_INSTALL_STATUS=running # running or must-install or must-upgrade
VITE_MSW_QUIET=off # on = turns off MSW console logs, off = turns on MSW console logs
VITE_UMBRACO_EXTENSION_MOCKS=off # on = turns on extension mocks, off = turns off extension mocks

• Run the npm install, npm run dev into the client project;
• Add the following NewBackOffice setting to your appsettings.json (Umbraco.Web.UI.New project):

"Umbraco": {
    "CMS": {
        "NewBackOffice":{
            "BackOfficeHost": "http://localhost:5173",
            "AuthorizeCallbackPathName": "/"
        },
        . . .

Test:

• Run new Backoffice project: Umbraco.Web.UI.New;
• Go to http://localhost:5173 which will redirect to https://localhost:44339 for authentication and then redirect back to http://localhost:5173;
• Verify that there are no CORS errors in the dev tools.

[kjac]

Looks great and tests great too 👍