Question
Can Digital Hive leverage OIDC (OpenID Connect) or Oauth as the authentication source for Digital Hive?
Answer
Digital Hive can be configured to use OIDC and/or Oauth authentication, but some default configuration parameters will have to be modified.

It is highly recommended that OIDC and Oauth integration is configured BEFORE a user has logged into the Digital Hive application. If a user has previously logged into Digital Hive before OIDC/Oauth was configured, please contact the Customer Success team at
support@digitalhive.com.
Note: After completing these steps, the first user to log into Digital Hive will be the Super User so please make sure that the first user to access Digital Hive is the intended Super User.
Specify OIDC authentication type and server
- Using the Windows File Explorer, navigate to the <install directory>\DigitalHive\app\node1\tomcat\conf directory
- Open the theia.properties file in a text editor
- Locate these entries within the file, usually at the bottom of the file (these are the settings for OKTA, Google, and Azure providers)

- Change the spring.security.oidc.client.registration.provider value to either okta, google, or azure. In this example, OKTA will be used as the security provider
- Set the value for spring.security.oidc.client.registration.mergeByEmail to OFF

- Change the values of the okta strings to match your authentication provider

- Save the changes to the file
Configuration settings for Microsoft Azure would look similar to:
Configuration settings for Google would look similar to:
It is possible to configure multiple OIDC/Oauth security providers for Digital Hive authentication. Each section must be completed in the theia.properties (as per the guidance above) and the registration provider string must include the different options separated by a semi-colon ;
When multiple providers are used, when users log in to Digital Hive, they will be forced to first select a provider.

Digital Hive is now configured to use OIDC and/or Oauth providers for authentication.