TunnelUtil creates exception with "No subject alternative names present" on self-assigned certificate

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 6.0.6 GA, 6.0.11 EE, 6.1.0 CE RC1
• Fix Version/s: 6.0.12 EE, 6.1.0 CE RC1, 5.2.X EE
• Component/s: Security, WCM, WCM > Staging
• Labels: None
• Similar Issues: Show 5 results ; ;

  LPS-22005	Improve exception handling if message has null subject
  LPS-28415	Wildcards present if searching for letters present in tags and usernames
  LPS-12648	Page Localization Name displayed in alternate language
  LPS-12064	Creating a community with a duplicate name throws exception
  LPS-13192	Selenium: Creating a community with a duplicate name throws an exception

In cases such as remote staging, if a server is using a self-assigned certificate for SSL, TunnelUtil will generate an exception with "No subject alternative names present". To circumvent this on a development environment only, add a portal.properties entry to disable hostname verification.

[Alexander Chow]

For added details, see RFC 2818 §3.1.

[Brian Chan]

Renamed the property to:

com.liferay.portal.service.http.TunnelUtil.verify.ssl.hostname

Set it to false to disable hostname verification. Default is true.