Installing the Back-End

1. In the command prompt window, navigate to the <enaio_install>\service-manager\tools\sam directory.

2. Run the following command: sam install <colab_localfolder>\colab-app\enaio-colab-app.jar.

   A message appears indicating that the configuration has been saved and enaio® coLab installed.

3. Copy the <colab-localfolder>\colab-app\colab-prod.yml file to the <enaio_installation>\service-manager\config directory.

1. Open the C:\Program Files\PostgreSQL\10\data\pg_hba.conf configuration file and search for the host all all 127.0.0.1/32 md5 entry.

2. Copy and paste the line.

3. Replace the IP 127.0.0.1 with your server IP address and save the file.

4. To reload the Postgres configuration, open 'pgAdmin 4' as a Postgres user.

5. Run the following query:

   select pg_reload_conf();

The following entry in colab-prod.yml is also necessary for new installations:

liquibase:
  contexts: legacy

1. Sign in to https://console.developers.google.com.

2. Create a new project and go to the Credentials area.

3. Click Create credentials and choose OAuth client ID.

4. Select Web application as the application type.

5. Retrieve the client ID and client secret and enter this information in the appropriate area in the colab-prod.yml configuration file.

6. Click Authorized JavaScript origins and enter your domain with the protocol where enaio® gateway is installed.

   For example: http://<gateway-IP>:colab

7. Under Authorized redirect URIs enter your domain name, followed by /epr/login/google/.

   For example: http://<gateway-IP>/colab/epr/login/google

8. Modify the <enaio_installation>\service-manager\config\colab-prod.yml file:

spring:
  security:
    oauth2:
      client:
        registration:
          google:
            clientId: client_id
            clientSecret: client_secret
            redirect-uri: ${global.service.baseUrl}/epr/login/google
            scope: openid, email, profile

1. Log in to https://developer.linkedin.com/docs/oauth2 and perform step 1 only. After you have received the authentication keys (client ID and client secret), enter them in the corresponding section of the colab-prod.yml configuration file.

2. Once the application has been created, enter your domain name under Authorized redirect URLs (along with the protocol and port), followed by /epr/login/linkedin.

3. Modify the <enaio_installation>\service-manager\config\colab-prod.yml file:

spring:
  security:
    oauth2:
      client:
        registration:
          linkedin:
            clientId: client_id
            clientSecret: client_secret
            redirect-uri: ${global.service.baseUrl}/epr/login/linkedin
            scope: r_emailaddress, r_liteprofile
            client-authentication-method: post
            authorization-grant-type: authorization_code
        provider:
          linkedin:
            authorization-uri: https://www.linkedin.com/oauth/v2/authorization
            token-uri: https://www.linkedin.com/oauth/v2/accessToken
            user-info-uri: https://api.linkedin.com/v2/me
            user-name-attribute: id

1. Log in to https://portal.azure.com and use the search field to search for App registration.

2. Click 'New registration', enter the relevant information in each of the fields, and click 'Register'.

   The application ID/client ID and object ID are displayed.

3. Click 'Certificates & secrets', followed by 'New client secret'.
4. Copy the value of 'Client secret'.

   Microsoft displays the client secret only once

5. Navigate to 'Authentication', click Add a platform, select Web on the configuration platform, then go to 'RedirectURL' and enter your domain name and protocol, followed by /epr/login/microsoft.

   For example: http://<gatewayIP>/colab/epr/login/microsoft

   When you are finished, enter the client secret along with the app key in the corresponding section of the colab-prod.yml configuration file.

6. Modify the <enaio_installation>\service-manager\config\colab-prod.yml file:

spring:
  security:
    oauth2:
      client:
        registration:
          microsoft:
            client-id: client_id
            client-secret: client_secret
            provider: microsoft
            redirect-uri: ${global.service.baseUrl}/epr/login/microsoft
            scope: openid, profile, email, https://graph.microsoft.com/.default
            client-authentication-method: basic
            authorization-grant-type: authorization_code
        provider:
          microsoft:
            authorization-uri: https://login.microsoftonline.com/common/oauth2/v2.0/authorize
            token-uri: https://login.microsoftonline.com/common/oauth2/v2.0/token
            user-info-uri: https://graph.microsoft.com/v1.0/me
            jwk-set-uri: https://login.microsoftonline.com/common/discovery/v2.0/keys
            user-name-attribute: id