Version 5.0.6

This version simplifies the user enrollment experience, streamlines the installation process, and enhances audit logging details. 

Version highlights include:

  • Enhanced OS platforms support: Octopus Authentication Server can now be

    installed on all supported versions (to 8.5) of all Linux platforms (Red Hat, Oracle, Rocky and


  • Audit logs enhancement: Audit details now include workstation IDs, allowing the
    Admin to easily locate workstations in the Octopus Management Console.

  • Log4j vulnerability prevention: Octopus AuthenEcaAuthentication Server version 5.0.6
    includes the market-recommended solution for mitigating the Log4j vulnerability

Version 5.0

This major version introduces several new authentications flows, offers significant enhancements to the User Portal, including branding options and more self-service actions, supports increased flexibility and better control of service workflows, and provides numerous features to simplify the enrollment process and promote greater security and confidentiality. 

Some of the version highlights include:

  • Adaptive Authentication (available for Octopus authentication) helps prevent user identity hijacking by requiring stronger authentication for login attempts from unrecognized workstations and browsers. When Adaptive Authentication is enabled, users authenticating for the first time from an unknown device are required to enter the verification code displayed in the Octopus Authenticator mobile app. Following the first successful strong authentication, users are no longer required to enter a code if the browser or workstation is designated as a Trusted device.
  • User Portal branding settings allow customers to design a unique look and feel for the Portal using colors, images, and organization-specific texts. Available branding features include Portal name and logo, background image, status bar, terms-of-use message, and more.
  • New Portal self-service actions allow users to view a list of all browsers used for authentication and enable them to clear data stored on a browser, such as the previously selected authentication method. The Reset Password action allows Local users (who aren’t members of integrated directories) to easily change the user verification password needed to authenticate to services that require MFA.
  • The Portal Auto Launch option for SAML services offers streamlining and convenience by having these services open automatically when users authenticate to the Portal. The global Auto Launch setting defined at the service level can be overridden at either the group or user level, enabling flexibility and support for specific user requirements.
  • The Resend To Another Address option allows invitation emails to be sent to an address other than the one recorded for the user in the system. This significantly facilitates the first enrollment process, as it allows new users who do not yet have access to the system to receive enrollment emails and start registering devices.
  • Users without access to the mobile app now have the option to log into organizational platforms and services using a temporary token, avoiding the need for the Admin to provide them with the actual AD password. To maintain token confidentiality, the token can be sent to the user by email. The token may also be designated for one-time use only, as required.
  • The Services list now includes prominently displayed service validity information to avoid errors and interruptions in service workflows. If any required service settings are missing, or if one or more settings are invalid, a warning icon appears. Clicking the icon opens a clearly organized list of the settings that are missing/invalid.
  • The Clone Service action existing service certificate or, available for all service types, lets the Admin quickly and easily create a new instance of an existing service. All service settings are copied, except for SAML service URLs (which are replaced with random UUIDs) and LDAP/RADIUS service port numbers (which are left blank). The Admin can choose whether to use the existing service certificate or generate a new certificate for the cloned service.

Attached please find the Release Notes containing the complete list of all new features in the version.