@mashroom/mashroom-storage - npm Package Versions

Sandbox App, Admin Toolbar: Make sure the chunks get new names when the content changes to avoid problems with browser caching
Error Pages: Don't show an error page if the response has content type application/json
Core: The health and readiness probes return now a JSON with the actual errors

2.1.1

Diff

jkofler

published 2.1.1 • 2 years ago

Changelog

Source

2.1.1 (June 13, 2022)

Admin Toolbar: Fixed validation of route '/'

2.1.0

Diff

jkofler

published 2.1.0 • 2 years ago

Changelog

Source

2.1.0 (June 13, 2022)

Portal: Re-check authentication expiration at least every 60sec, so, if the session for some reason expires (or gets revoked) the user will get notified faster.
Core: Dropped Node.js 12.x support
Portal: Prevent a loop if error messages can not be sent to the server

MongoDB Session Provider: BREAKING CHANGE: Changed config structure to be able to pass parameters to connect-mongo, such as ttl and autoRemove.

Before:

{
  "uri": "mongodb://username:password@localhost:27017/mashroom_session_db?connectTimeoutMS=1000&socketTimeoutMS=2500",
  "collection": "sessions",
  "connectionOptions": {
    "poolSize": 5
  }
}

After:

{
  "client": {
    "uri": "mongodb://username:password@localhost:27017/mashroom_session_db?connectTimeoutMS=1000&socketTimeoutMS=2500",
    "connectionOptions": {
       "poolSize": 5
    }
  },
  "collectionName": "sessions",
  "ttl": 86400
}

Redis Session Provider: BREAKING CHANGE: Changed config structure to be able to pass parameters to connect-redis, such as prefix and ttl. Setting prefix on this level instead of the Redis client level fixed the session count metric, which was broken.

Before:

{
  "redisOptions": {
    "host": "localhost",
    "port": "6379",
    "keyPrefix": "mashroom:sess:"
  },
  "cluster": false
}

After:

{
  "client": {
    "redisOptions": {
      "host": "localhost",
      "port": "6379",
    },
    "cluster": false
  },
  "prefix": "mashroom:sess:",
  "ttl": 86400
}

Admin Toolbar: Only allow valid characters (according to RFC 3986) in Routes
Admin Toolbar: Added checkbox for client-side routing and renamed friendlyUrl to Route because that's more what it is.
Portal: Added support for client-side routing. If you enable it everything appended to the page URL is ignored.
Portal: Added new property portalAppHost to the log context of Remote Portal Apps

2.0.7

Diff

jkofler

published 2.0.7 • 2 years ago

Changelog

Source

2.0.7 (June 2, 2022)

Portal: Switched to cache-control public for App resources, even for authenticated users
Portal: Fixed cache busting. The v=xxx query parameter is now constant for a plugin version (if the Portal ist not in dev mode). You should now replace lastThemeReloadTs with themeVersionHash in your themes.
Security Service: Don't log an error for AJAX requests to restricted resources (just return 403)

2.0.6

Diff

jkofler

published 2.0.6 • 2 years ago

Changelog

Source

2.0.6 (June 1, 2022)

Remote App Registry and K8S Remote App Registry: Fixed registering Apps of type portal-app2 without SSR capability
HTTP Proxy: Added a retry if the target resets or drops the connection (ECONNRESET) which can happen when:
- keepAlive is activated and a reused connection is broken already (see https://nodejs.org/api/http.html#requestreusedsocket)
- a Pod/instance is no longer/not yet available
HTTP Proxy: Fixed handling of client connection termination. Among others the misleading error message 'Target endpoint did not send a response within xxxxx' will no longer be logged in the case the client dropped the connection.
Portal: State encoded in URL via MashroomPortalStateService is encoded/decoded now

2.0.5

Diff

jkofler

published 2.0.5 • 2 years ago

Changelog

Source

2.0.5 (Mai 20, 2022)

Portal: The resource and the proxy target URLs of Remote Apps can now overlap as long as requested resources have an extension. E.g.: If your plugin definition looks like this:
```
 {
   "name": "My Remote App",
   "type": "portal-app2",
   "remote": {
     "resourcesRoot": "/"
   },
   "defaultConfig": {
     "proxies": {
       "bff": {
         "targetUri": "http://localhost:6089"
       }
     }
   }
 }
```
the Portal will calculate a resource base URL http://yourhost.com/ and a base URL for the bff proxy of http://yourhost.com/, so they overlap. Now you can request a resource /index.js with this setup, previously you couldn't, because the Portal has treated it as an attempt to fetch API data via (potentially less protected) resource request.
Security Service: Start authentication flow (e.g. redirect to the login page) only for GET and non-Ajax requests

2.0.4

Diff

jkofler

published 2.0.4 • 2 years ago

Changelog

Source

2.0.4 (Mai 9, 2022)

Remote App Registry and K8S Remote App Registry: Show Apps with errors on top of the list in the Admin UI
K8S Remote App Registry: The Admin UI shows now all successfully registered Apps even if scanning some namespaces fails due to missing permissions

2.0.3

Diff

jkofler

published 2.0.3 • 2 years ago

Changelog

Source

2.0.3 (Mai 6, 2022)

Portal: Fixed Express.js view caching if multiple Themes are involved. If NODE_ENV = production it was possible that views from the wrong Theme were used.

2.0.2

Diff

jkofler

published 2.0.2 • 2 years ago

Changelog

Source

2.0.2 (Mai 2, 2022)

K8S Remote App Registry: The admin UI shows now the scanned namespaces
Portal: If an App on a page cannot be found (if it is not registered (yet)), an error message will be displayed now instead of just showing nothing. The old behaviour can be restored by setting the Mashroom Portal WebApp config property ignoreMissingAppsOnPages. On the client side you can check if an App is in error state because the plugin does not exist with
```
     clientServices.portalAppService.loadedPortalApps[0].errorPluginMissing;
```
Portal: Fixed SSR cache key to avoid possible collisions
Portal: Added possibility to turn of the SSR cache (even if @mashroom/mashroom-memory-cache is present)
OpenID Connect Security Provider: Removed the options httpRequestRejectUnauthorized and httpRequestRetry because they are no longer supported by openid-client
Vue Demo App: Upgrade to Vue3 and server-side rendering added
Sandbox: Show all Apps for the Administrator role, even if defaultRestrictViewToRoles is set