APIM [3.x.x] Causing "SSL peer failed hostname validation for name: localhost" when login to APIM portals

When the localhost is not included in the certificate file as a common name (CN) or a subject alternative name (SAN).

Following SSL issue causing when tried to log in to the APIM 3.0.0 admin/publisher/dev portals.

org.jaggeryjs.scriptengine.exceptions.ScriptException: javax.net.ssl.SSLPeerUnverifiedException: SSL peer failed hostname validation for name: localhost

Since the hostname used for internal calls triggered when login (admin/publisher/devportal) are set to 'localhost' the above issue is causing

For APIM publisher and dev portal. we can modify the following files, by altering the localhost and provide the relevant hostname to solve the issue.

• /repository/deployment/server/jaggeryapps/<PUBLISHER/DEVPORTAL>/site/public/theme/settings.js file, /repository/deployment/server/jaggeryapps/<PUBLISHER/DEVPORTAL>/site/public/theme/settings.js file

But when it comes to the admin portal we need to modify AuthManager, server URL hostname by providing the cert's CN. But In 3.x, the AuthManager, server URL is not configurable.

Due to this in order to avoid those issues, We need to update the documentation with recommending to add the localhost as a common name (CN) or a subject alternative name (SAN) when configuring the certificate.