With its host name e.g. "clarity-server"
With the host name and the domain e.g. "clarity-server.ca.com"
With its IP address e.g. "123.123.123.123"

In Clarity v13.x you can use all three methods to connect to Clarity, when SSL is not enabled. As soon as you enable SSL, only the URL given in the "HTTPS Entry URL" field in CSA works. The two others will show the login screen, but the login will
hang. In app-system.log you will find an error message that loops and generates thousands of identical lines.
This can be reproduced with Clarity 13.0.1 fix pack 6 and Clarity 13.1.0 fix pack 4. In Clarity 12.1.3 the issue could not be reproduced and the system
behaves as expected.

Steps to Reproduce:

Configure an out-of-the-box Clarity v13.x in CSA

a. disable HTTP connections

b. enable HTTPS connections

c. enter the "HTTPS Entry URL" like https://hostname:8043

Restart the application service (app)

Login from any supported browser with the URL https://hostname:8043

If the login is successful, logout

Identify the IP address of the host running Clarity

Login from any supported browser with the URL https://ip address>:8043

Expected Result:
Successful Login in a reasonable amount of timeActual Result:
Login hangs, app-system.log will be filled with a loop in the stack trace

WORKAROUND: Instead of encrypting SSL in Clarity (either in Tomcat, WebSphere or WebLogic), offload the SSL handling to a front end device (i.e. hardware load balancer
or Apache HTTP Server), then run Clarity without SSL ports enabled. Set the SSL Settings in Clarity to "SSL is used but processed externally".
This problem is not reproducible if Clarity itself is not encrypting the SSL traffic.