Skip to main content
Skip table of contents

Release note Digital Access component 6.0.6

Version: 6.0.6

Release Date: 2021-06-23


Smart ID Digital Access component 6.0.6 has been released today.

This version of Digital Access is included in the release of Smart ID 21.04.1.

Important note

Added Docker Swarm for Digital Access in 6.0.5 and the only way to upgrade to 6.0.5 or above is by following the upgrade documents mentioned under Upgrade Digital Access componentAlso after upgrading to 6.0.5 or above, the orchestrator and v-apps menu is removed from the virtual machine.

Also note that MS SQL Server 2008 is no longer supported after Digital Access 6.0.6.

Detailed feature list


Jira ticket noDescription

Added ability to upgrade directly from 5.13.x to 6.0.5 or above using docker-swarm. The same script also can also migrate Digital Access from appliance to other system by following steps mentioned in the document. See Upgrade Digital Access from 5.13.1 and above to 6.0.5 and above.

Corrected bugs

Jira ticket noDescription


Improved the CLI script to relink/delete users from internal Digital Access database if the users are deleted in AD or have broken links.

  1. Run the command export prefix=/etc/nexus
  2. Run the script inside the administrator service container using CLI.


Added support for multiple assertion consumer service URLs specified in AuthnRequest and redirect according to the AssertionConsumerServiceIndex.


When provisioning from Digital Access to Hermod, and if the display name contains a space or other characters, the encoding for the same in the URL is now fixed.

Also, if the value of ‘Issuer’ field is changed, the same will reflect in the provisioned profile (which was not the case before).


Fixed the Digital Access Admin crash while adding SAML resource with blank Relay state.


Added validation for User ID to not allow leading or trailing spaces in Digital Access Admin and in XPI calls. The users already added with spaces will remain unaffected.


Fixed TLS/SSL vulnerabilities in admin, policy, authentication, and distribution services.

TLS 1.0 and 1.1 are not supported anymore. It will not work if a client tries to connect to Digital Access using TLS 1.0 or TLS 1.1.


Fixed the issue where administration service considers non-local oath database server as local database server.


Added the configuration for encoding so that users can set in the customize.conf the type of encoding for SMS and Email notifications, default is UTF-8.


Fixed the issue with empty diagnostics when SMB logging is enabled.


Contact Information

For information regarding support, training and other services in your area, please visit our website at

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.