Issue Summary

This is reproducible on Data Center: Yes

Steps to Reproduce

1.  Integrate Crowd with an Application. Confluence is used in this example.
2. When specifying an Application's Address or Hostname, add an invalid hostname to the list, along with the valid hostnames and addresses.
   • In this example, the invalid hostname added is: false
3. Try to log into the application with a user configured in the Crowd directory created for the application.

Expected Results

• The invalid hostname will be ignored and login will be successful.

Actual Results

• The users will not be able to log in with the following message shown in the UI:
  

• The below exception is thrown in the atlassian-crowd.log file:

  http-nio-8095-exec-1 ERROR [[Catalina].[localhost].[/crowd].[default]] Servlet.service() for servlet [default] in context with path [/crowd] threw exception
  java.lang.IllegalArgumentException: Failed to parse addressfalse
  <Trimmed>
  Caused by: java.net.UnknownHostException: false
  

• The exception will show the invalid hostname added in the remote addresses of the application. In this example: false

This issue is observed in Crowd versions 5.3.0 and 5.3.1
Previous versions of Crowd will allow login even if an invalid hostname is present in the remote addresses of the application.

Workaround

Remove the invalid hostname(s) from the list of the remote addresses in Crowd.