Release note Digital Access component 6.3.0
Version: 6.3.0
Release Date: 2023-01-23
Upgrade docker
Upgrade docker to a version >= 20.10.10 before you upgrade Digital Access to this or higher versions, since docker <= 20.10.9 has compatibility issues with used the OpenJDK version.
Minor improvements
Jira ticket no | Description |
---|---|
DA-470 | Added a third option (None) for the auto-linking accounts notifications section. Selecting None will not send any notifications when the user accounts are auto-linked by Digital Access. |
DA-911 | UX improvements while publishing changes to services in Digital Access. It is now possible to see the status of each service while it is waiting to connect, and the updates once it gets successfully published. The Publish button will change color to gray during the publish progress. |
DA-1149 | Added support to bridge network for Smart ID deployment in case of distributed or High Availability (HA) setup. For more information about configuring high availability or distributed architecture, see Set up high availability for Digital Access deployment (bridge network). |
DA-940 | Ability to add LoA translation groups. LoA translation groups define the conditions when to convert the AuthNContextClassRef in the SAML response to a new value. For more information, see Set up SAML authentication context in Digital Access. |
DA-1156 | Added a Listen on all Interfaces checkbox for administration service to support bridge network. This checkbox should be selected only while using the bridge network. |
Corrected bugsÂ
Jira ticket no | Description |
---|---|
DA-930 | Upgraded some libraries to fix a few detected vulnerabilities. |
DA-1027 | There was an issue where the user accounts selection was not retained after saving roles in the delegate management. This has been fixed. |
DA-1127 | Added documentation around Personal desktop in the help section for the authentication method. |
DA-716 | Upgraded SMTP plugin to javax.mail 1.6.2 to support TLS 1.2. |
DA-913 | There was an issue where an unintentional authentication-loop occurred when Nexus Digital Access acted as IDP-proxy for two federations. This has been fixed. |
DA-923 | There was an issue where an incorrect content-type for JPG caused Internet Explorer (and Intune for Linux) to prevent loading Personal mobile authentication images. This has been fixed. |
Contact Information
For information regarding support, training and other services in your area, please visit our website at www.nexusgroup.com/.Â
Copyright 2024 Technology Nexus Secured Business Solutions AB. All rights reserved.
Contact Nexus | https://www.nexusgroup.com | Disclaimer | Terms & Conditions