Switch from ELOauth to ELO Modern Authentication

The previous ELOauth plug-in has been replaced with the introduction of ELO 25. ELO Modern Authentication (Auth2) is completely responsible for managing the authentication process, relying on state-of-the-art authentication standards.

New in ELO Modern Authentication:

• Central, standardized logon: Authentication is integrated fully into ELO, and is no longer an additional, separate module Thanks to the configuration of single sign-on (SSO), all clients automatically benefit from central authentication.

• Easier configuration via the ELO Administration Console Support for modern OpenID protocols ensures flexibility and compatibility.

• Individual branding: Customization options for the logon design, logo integration, and custom background images

• Compatibility with OAuth2: ELO Modern Authentication is based on OAuth2, the established standard, which is supported by providers such as Microsoft, Google, and Keycloak.

• Elimination of legacy protocols:With the introduction of ELO Modern Authentication, ELO is focusing on future-proof technologies.

  The new standard is based on OpenID and OAuth2, which platforms such as Microsoft, Google, and Keycloak also favor.

  Please note

  The authentication protocol SAML is no longer supported.

Migration of the configuration

If the ELOauth plug-in is in use, several important steps are mandatory for migration.

Changes for the connection via other identity providers

Existing authentication settings have to be transferred to ELO Modern Authentication (Auth2).

If authentication via Microsoft Azure is configured, you will have to change the app in Microsoft Entra ID that you previously used for authentication with ELOauth. Alternatively, you can create a new app. Refer to the chapter Microsoft Azure configuration to learn how to configure the app.

Changes in the clients and web applications

With ELO Modern Authentication, no changes to the URLs are required for logging on the ELO clients and ELO apps.

Configure the URL for each logon profile or web application according to the standard format.

• For ELO Java Client and ELO Desktop Client:

  http(s)://<server name>:<port>;/ix-<repository name>/ix
  

• For web applications (e.g. the ELO Web Client, ELO apps):

  http(s)://<server name>:<port name>/ix-<repository name>/plugin/de.elo.ix.plugin.proxy/web/