Login fails, "Unable to authenticate. Please try again later." when attempting to log in to ICDx.

Products

• Integrated Cyber Defense Exchange
• ICDx

Issue/Introduction

You have installed the Integrated Cyber Defense Exchange (ICDx) 1.4.3 or newer but login fails with the result of "Unable to authenticate. Please try again later."

Environment

Integrated Cyber Defense Exchange 1.4.3

Cause

The ICDx 1.4.3 identity service now uses ports 8035 and 8036 by default. If either of these ports are in use by another process then the identity service will not be able to fully start. Attempting to log into the web interface will fail.

 

Resolution

To resolve this issue you will need to do one of the following (either A or B):

1. Ensure no other processes are configured to use either port 8035 or port 8036.
   • The most common way to check for port use in Linux is through netstat. You can use a command such as the following:
     • sudo netstat -tnap | grep "8035\|8036"
   • If you determine that other processes are using port 8035 or port 8036, you may be able to configure them to use other ports. You will need to consult the documentation for those processes for information on changing their configurations.
2. Configure the ICDx identity service to use a different set of ports that are not in use.
   • See the steps below.

To configure the ICDx identity service to use other ports:

1. Determine which two ports are not used by other processes and can be used by ICDx (For this example we will use ports 11500 and 11501).
2. Use a text editor, such as nano or vi, to modify the epmp "application.properties" and "id_epmp_i_support-override.properties" files (for this example we will use nano):
   
   
   • sudo nano $SYMC_HOME/id_epmp_dx-<version>/application.properties
     • (<version> is the currently installed module version in the form of #.#.###-###)
     • Find the following line:
       server.port=8035
     • Change the port number 8035 to your new chosen primary port number
       • For example:
         server.port=11500
     • Find the following line:
       management.server.port=8036
     • Change the port number 8036 to your new chosen secondary port number
       • For example:
         management.server.port=11501
     • Save the file changes.
       
       
   • sudo nano $SYMC_HOME/id_epmp_dx-<version>/id_epmp_i_support-override.properties
     • (<version> is the currently installed module version in the form of #.#.###-###)
     • Find the following line:
       identity.keys-url=http://localhost:8035/oauth2/keys
     • Change the port number in the url from 8035 to your chosen primary port number
       • For example:
         identity.keys-url=http://localhost:11500/oauth2/keys
     • Save the file changes.
       
       
   • sudo nano $SYMC_HOME/r3_epmp_dx-<version>/id_epmp_i_support-override.properties
     • (<version> is the currently installed module version in the form of #.#.###-###)
     • Find the following line:
       identity.keys-url=http://localhost:8035/oauth2/keys
     • Change the port number in the url from 8035 to your chosen primary port number
       • For example:
         identity.keys-url=http://localhost:11500/oauth2/keys
     • Save the file changes.
       
       
3. Restart the services:
   • sudo service launcher_dx restart

Once the services have restarted using the available ports, this login issue will be resolved.