• (@GermanBluefox) Fixed: the link of an adapter that runs as a web extension lost everything behind the host. energiefluss-erweitert points at .../energiefluss-erweitert/?instance=%instance%, and the quick access offered .../energiefluss-erweitert/ - without the page and without the instance. Such an adapter has no own port, so the origin of its link has to come from the web instance that serves it, but the whole address was built anew instead of only its origin being exchanged. The same happened to habpanel, whose index.html disappeared, and to a second link of an adapter that pointed at its documentation on a foreign host: it ended up on the own web server (#3661)
• (@GermanBluefox) Fixed: a card of the quick access belonged to whichever adapter was processed first. Every vis-2 widget adapter registers a link to the vis-2 runtime, and because the instance IDs decide the order, vis-2 itself lost its own card to one of them, together with its name, its icon and its color. The card now belongs to the adapter that serves the page
• (@GermanBluefox) Added: the admin recognizes that it was opened through the remote access of ioBroker Cloud/Pro and moves the links onto the service. The quick access, the instance list and the tabs of the left menu pointed into the local network, which is of no use to somebody who is not in it. Which instances the service publishes is read from the configuration of the cloud or iot adapter, so nothing is guessed: the web instance is reachable at /, the admin at /admin/ and lovelace at /lovelace/. A page the service does not publish - Node-RED or a second admin, for example - is no longer offered as a dead link but shown dimmed with a note that it only works in the local network
• (@GermanBluefox) Added: the identity provider for the single sign-on can be configured. The issuer, the client ID, an optional client secret and the scopes are set in the new "Single sign-on" tab of the admin settings, and the endpoints are read from the discovery document of the issuer, so every provider that follows the standard works. Without a complete configuration the SSO stays off and the login page does not offer it (needs @iobroker/webserver 3.3.0)
• (@GermanBluefox) Fixed: with authentication enabled, the GUI took seconds to come up and sometimes did not come up at all. If the access token had expired while the tab was closed, the websocket was opened with it, the server asked for a new one and then stopped listening on that connection: the token the browser fetched within milliseconds could not be announced, the browser waited for an answer that could not come until its own three second timeout, and the single-use refresh token was burnt for nothing before the whole start began again (needs @iobroker/socket-classes 2.6.2)
• (@GermanBluefox) Changed: mime was replaced by mime-types. mime 4 is ESM only, and version 3 is no longer maintained; mime-types uses the same database, is already part of the dependency tree through express, and three duplicated copies of it disappear from the lockfile. A JavaScript file is now served as text/javascript instead of the deprecated application/javascript