Who is this article for?

IT Administrators and Administrators responsible for managing system settings.

No special access or permissions are needed.

Single Sign-On (SSO) is an authentication process that allows a user to access multiple applications or services with one set of login credentials.

This article outlines the benefits of using the authentication method and prerequisites you need to meet to be able to implement it within your organisation.

1. Overview

There are many reasons to consider implementing SSO in your system, including the fact that many organisations now require SSO to be the main form of user authentication.

Having a single set of credentials reduces the number of attack surfaces available, greatly increasing your system security. It also supports Multi-Factor Authentication (MFA), further reducing the risk of unauthorised access.

It also has practical benefits. From an administration perspective, it makes maintenance easier as access can be managed centrally. From an end user perspective, there is no need to remember several passwords to access the various areas of the system.

You can use SSO to:

• Log into the Windows Client
• Log into the Web interface
• Log into the Mobile app
• Log into Web reporting
• Log into the Document Retrieval Service (DRS)
• Complete electronic signatures (if enabled)

2. Supported providers

Below is a list of the currently supported providers and their system requirements.

We are aware of an incompatibility requiring access to the Okta API Admin feature to set up the provider.
We are working on a fix in future releases, 7.6.2 (December 2024) and 7.7.1 (TBC), to remove this requirement.

Further reading

• Configuring Single Sign-On (SSO)
• [Example] Configuring Okta for Single Sign-On (SSO)
• [Example] Configuring PingOne for Single Sign-On (SSO)
• [Example] Configuring Microsoft Entra ID for Single Sign-On (SSO)