Page Comparison

...

In our case, the reverse proxy server hosts an Apache HTTP server with modules to implement a proxy (mod_proxy) which would also host the authentication logic. Following successful authentication, the user is passed in the RequestHeader and the request is forwarded to the Tomcat server hosting OLE. Unsuccessful authentication is handled appropriately.

 To get this working successfully a few configurations are needed. The significant ones are listed below for reference.

Configurations on the Apache Tomcat side

...

<filter>
	<filter-name>DummyLoginFilter</filter-name>
    <filter-class>org.kuali.ole.sys.web.filter.DevelopmentLoginFilter</filter-class>
    <init-param>
    	<param-name>loginUser</param-name>
        <param-value>ole-quickstart</param-value>
    </init-param>
</filter>
<filter-mapping>
	<filter-name>DummyLoginFilter</filter-name>
    <servlet-name>action</servlet-name>
</filter-mapping>
<filter-mapping>
	<filter-name>DummyLoginFilter</filter-name>
	<servlet-name>dwr-invoker</servlet-name>
</filter-mapping>
<filter-mapping>
	<filter-name>DummyLoginFilter</filter-name>
	<servlet-name>batchFileUpload</servlet-name>
</filter-mapping>

Changes in server.xml

The server.xml file is found at <CATALINA_HOME>/conf/

If SSL is used, there could be problems while accessing certain search pages. This is because the URL is formed by using request.getRequestURL(), which ultimately comes from "scheme" part of the connector configuration in server.xml. So the scheme attribute should be set to 'https' and the port attribute to '443' for OLE to generate the proper URLs.

<Connector port="8443" protocol="HTTP/1.1"
               connectionTimeout="20000"
               URIEncoding="UTF-8"
               scheme="https"
               proxyPort="443"/>