@mashroom/mashroom-browser-cache - npm Package Versions

• X-USER-DISPLAY-NAME
• X-USER-EMAIL

Added a virtual host path mapper plugin: Allows it to map internal paths based on virtual hosts and web apps to get the actual "frontend path" to generate absolute links at the same time. Can be used to expose Portal Sites to virtual hosts like so:

https://www.my-company.com/new-portal -> http://internal-portal-host/portal/web

For this example configure your reverse proxy to forward calls from https://www.my-company.com/public to http://internal-portal-host/ and additionally configure the new plugin like this:

"Mashroom VHost Path Mapper Middleware": {
  "hosts": {
    "www.my-company.com": {
      "frontendBasePath": "/new-portal",
        "mapping": {
          "/login": "/login",
          "/": "/portal/web"
        }
     }
  }
}

  {
    "/portal/public-site/**": {
      "*": {
        "allow": "any"
      }
  }
  "/portal/**": {
    "*": {
      "allow": {
        "roles": ["Authenticated"]
      }
    }
  }
}

• "any" is now a possible value for allow/deny; this matches also anonymous users which is useful for public sub-pages
• it is now possible to pass an object to allow/deny with a list of roles and ip addresses

{
  "/portal/**": {
    "*": {
      "allow": {
        "roles": ["Authenticated"],
        "ips": ["10.1.2.*", "168.**"]
      },
      "deny": {
        "ips": ["1.2.3.4"]
      }
    }
  }
}

"Mashroom Security Services": {
   "provider": "Mashroom Security Simple Provider",
   "forwardQueryHintsToProvider": ["kc_idp_hint"]
}

{
    "name": "${env.USER}'s Mashroom Server",
    "port": 5050
}

  // index.ts
  import {MashroomPortalAppPluginBootstrapFunction} from '@mashroom/mashroom-portal/type-definitions';
  const bootstrap: MashroomPortalAppPluginBootstrapFunction = (hostElement, portalAppSetup, portalClientServices) => {
    // ...
  }