Portal: Added support for sharing resources between portal apps (e.g. vendor libraries or styles). A shared resource with a given name will only loaded once, even if multiple Portal Apps declare it. A shared resource can be added like this in the plugin definition:

{
    "name": "Demo Shared DLL App 1",
    "type": "portal-app",
    "bootstrap": "startupDemoSharedDLLApp1",
    "sharedResources": {
        "js": [
            "demo_shared_dll_910502a6fce2f139eff8.js"
        ]
    }
}

Check out the demo project here: https://github.com/nonblocking/mashroom-demo-shared-dll

Portal: A remote Portal App which is not reachable for a long time is now unregistered instead of complete removed from the list of remote Apps
Added MongoDB session provider plugin
Added Redis session provider plugin
Portal: Show a proper error if a configured Portal App on a page cannot be loaded (instead of showing nothing)

1.1.4

Diff

jkofler

published 1.1.4 • 5 years ago

Changelog

Source

1.1.4 (October 23, 2019)

Core: Logger instances created via req.pluginContext.loggerFactory('category') share now the context with all other loggers created from the same request. This can for example be used to output tracing information with each log entry. The following context properties will be added automatically to each request:
- clientIP
- browser (e.g. Chrome, Firefox)
- browserVersion
- os (e.g. Windows)
- sessionID (if a session is available)
- portalAppName (if the request is related to a portal app)
- portalAppVersion (if the request is related to a portal app) To add additional properties to the logger context use the new logger.addContext() method (e.g. within a middleware). If you want to output context properties with the log entries you could configure the log4js appender like this:
```
"console": {
    "type": "console",
    "layout": {
        "type": "pattern",
        "pattern": "%d %p %X{sessionID} %X{browser} %X{browserVersion} %X{username} %X{portalAppName} %X{portalAppVersion} %c - %m"
    }
}
```
HTTP Proxy: White listed Jaeger, OpenZipkin and W3C Trace Context HTTP headers by default
HTTP Proxy: Fixed the problem that all requests headers got forwarded to the target, even cookie and other security relevant ones

1.1.3

Diff

jkofler

published 1.1.3 • 5 years ago

Changelog

Source

1.1.3 (October 15, 2019)

Tabify App: Allow to update the title for a specific app id. This is useful for dynamic cockpits where you might want to load the same App multiple times in a tabbed area.
Portal: Fixed a problem with token highlighting in the add app panel

1.1.2

Diff

jkofler

published 1.1.2 • 5 years ago

Changelog

Source

1.1.2 (September 30, 2019)

Added a middleware plugin that introduces Helmet which sets a bunch of protective HTTP headers on each response
Upgraded some dependencies because of security vulnerabilities

…

7 8

@mashroom/mashroom-helmet - npm Package Versions

1.2.1

.css-1z04cui{margin-bottom:var(--chakra-space-4);font-size:var(--chakra-fontSizes-md);}1.2.1 (November 25, 2019)

1.2.0

1.2.0 (November 15, 2019)

1.1.4

1.1.4 (October 23, 2019)

1.1.3

1.1.3 (October 15, 2019)

1.1.2

1.1.2 (September 30, 2019)

1.2.1 (November 25, 2019)