bpwwer Posted June 12, 2023 Posted June 12, 2023 Hello all, We are very happy to introduce PG3x v3.1.29 for eisy and Polisy. With these releases, there are changes to how Portal access tokens are managed. Prior releases attempted to manage the Portal access token in the web UI code. This tied the access toke to the PG3x login/logout functions requiring a new access token every time you logged into PG3x via the web. With version 3.1.27, the management of the Portal access token has moved into the PG3x server code. PG3x will request the WebUI to obtain a Portal access token only when it needs a new token. The server side will maintain the token indefinitely so you will no longer need to provide PG3x with a new access token when logging in to PG3x via the WebUI. The eisy is using a new version of Polyglot version three called PG3x. PG3x has infrastructure changes to make node servers (and PG3x) more secure and enable features based on remote access. Polisy users may update their systems to use PG3x if they want access to the new features. PG3 will continue to get updates for the foreseeable future. To upgrade PG3x: In the Admin Console, click on Configuration, Upgrade Packages (note, this can take many minutes, depending on how long it's been since you last updated.). After the upgrade is complete you should restart/reboot the eisy. Do this from the Admin Console, Configuration, Reboot. Once PG3x has restarted, reload /refresh the browser page. Changelog for 3.1.29 - If refresh token expires, request UI get a new token. - Add menu item to UI system menu to reset portal credentials. Changelog for 3.1.28 - Remove unnecessary log messages. - Update local globalsettings when db is updated. - Add log message to warn of missing key if a key that doesn't exist is queried. - Handle 'seq' field in incoming messages from frontend clients - Synchronize settings with frontend. - Clean up error and log message for portal based queries. - Force devMode to be 0 or 1 2
Recommended Posts