6.2 Chrome HTTPS issue

[William Gosse, modificado 8 Anos atrás.]

I'm front ending liferay with apache httpd which is handling ssl. Using AJP that not ssl to access liferay from httpd.

Content being returned looks fine is IE and FF but styling is lost in Chrome.

If ssl not used everything looks fine in Chrome as well.

[David H Nebinger, modificado 8 Anos atrás.]

Make sure you've configured Liferay to use SSL for all requests using the following properties:

company.security.auth.requires.https=true
session.enable.phishing.protection=false
web.server.protocol=https

You'll know if you have a problem if the URLs for the javascript and css are http:// instead of https://.

[William Gosse, modificado 8 Anos atrás.]

Thanks! This solved the issue.

[William Gosse, modificado 8 Anos atrás.]

I tried adding a new LDAP server to Liferay’s Portal Settings -> Authentication -> LDAP -> Add but the request is getting rejected for some reason. I see the following error in the liferay log file:
19:20:59,897 WARN [ajp-hal-pptla-d01/10.5.75.167:8009-2][SecurityPortletContainerWrapper:630] Reject process action for https://ch4ht-dev.intranet.xxxxx.com/group/control_panel/manage on 130

I’m thinking it may be related to ssl but I’m not sure at this point. I have these settings in my portal-ext.properties file:
company.security.auth.requires.https=true
session.enable.phishing.protection=false
web.server.protocol=https

I have no issues doing this an a localhost installation that I have that does not have these settings.

[David H Nebinger, modificado 8 Anos atrás.]

That will be logged when there is a principal exception encountered when trying to access the given URL.

[William Gosse, modificado 8 Anos atrás.]

Any thoughts on how this issue can be resolved? Again this is out of the box functionality here.

[David H Nebinger, modificado 8 Anos atrás.]

If you enable debug logging on com.liferay.portlet.SecurityPortletContainerWrapper, it will log the exception that is causing the message to be displayed. That will provide the insight into why and where it is failing.

[William Gosse, modificado 8 Anos atrás.]

Actually I'm now seeing this:
19:53:51,668 DEBUG [ajp-hal-pptla-d01/10.5.75.167:8009-1][PortletRequestProcessor:496] Getting request parameter path /admin_server/edit_server
19:53:51,670 DEBUG [ajp-hal-pptla-d01/10.5.75.167:8009-1][PortletRequestProcessor:518] Processing path /admin_server/edit_server
19:53:51,671 ERROR [ajp-hal-pptla-d01/10.5.75.167:8009-1][PortletRequestProcessor:466] Forward does not exist
19:53:51,694 DEBUG [ajp-hal-pptla-d01/10.5.75.167:8009-1][PortletRequestProcessor:496] Getting request parameter path null
19:53:51,695 DEBUG [ajp-hal-pptla-d01/10.5.75.167:8009-1][PortletRequestProcessor:501] Getting request attribute path null
19:53:51,696 DEBUG [ajp-hal-pptla-d01/10.5.75.167:8009-1][PortletRequestProcessor:518] Processing path /dockbar/view