# Configure Find to Use the Reverse Proxy

You configure Find to use a reverse proxy by setting the `server.reverseProxy` system property.

When you set `server.reverseProxy` to true, the Find application listens for AJP connections on a port that you can define by using the `server.ajp.port` system property.

The reverse proxy must translate incoming HTTP(S) connections from your clients into AJP connections to Find. In AJP mode, the application reads the user name from incoming requests, so you must set up remote authentication. You cannot encrypt the connection from the reverse proxy to the application.

By default, `server.reverseProxy` is false. In this case, the Find application is available only over HTTP or HTTPS. Remote authentication is not possible in this mode. However, you can encrypt the connection with SSL. In this mode, users authenticate by using the proxied login page.

In both these methods, the reverse proxy must rewrite the request path, response Location headers, and cookie paths.

## Set the Reverse Proxy System Property

You can use the following procedure to set the `server.reverseProxy` system property.

To configure Find to use a reverse proxy

1. At the command line, send the java run command with the `server.reverseProxy` argument set to `true`. For example:

       java -Dserver.reverseProxy=true -Didol.find.home=[home directory] -Dserver.port=[port] -jar find.war

   By default, this option opens an AJP port on port 8009. To use a different port, set the `server.ajp.port` argument to the correct port number.

   You can also specify the roles to assign to your users by setting the `find.reverse-proxy.pre-authenticated-roles` system property:

   - Set `find.reverse-proxy.pre-authenticated-roles` to a comma-separated list of Find Community role names (see User Roles) to use hard-coded role names.

   - Set `find.reverse-proxy.pre-authenticated-roles` and leave the value blank to use roles from the Community component. For example:

         java -Dserver.reverseProxy=true -Didol.find.home=[home directory] -Dserver.port=[port] -jar find.war -Dfind.reverse-proxy.pre-authenticated-roles=

     To use this option, you must ensure that your Community component configuration file has `CheckEntitlement` set to `False` (the default value).

   The default value for this property is `FindUser`.

   NOTE: This setting does not assign any roles in the Community component. It gives all users that use the reverse proxy the same permissions to access Find.

   Another option is to set `find.reverse-proxy.pre-authenticated-username` to a specific user name. This option bypasses authentication so that any user that accesses Find is logged in automatically as that user name. See Configure Find to Use a Single Pre-Authenticated User.

2. Restart Find to apply your configuration changes.

If you run Find as a service on Windows, you can also add the `server.reverseProxy` property to the `find.xml` file.

If you run Find as a service on Linux, you can add the arguments to the existing arguments variable in the start scripts (`find.sh` for SystemV, `find.conf` for Upstart, or `find.service` for systemd).

When you modify the Find configuration by modifying the XML file or start scripts, you must restart Find to apply your configuration changes.

On Upstart, you must also run `initctl reload-configuration` before you restart, to apply the init file changes. You can then run `service find restart` to restart the service.

_FT_HTML5_bannerTitle.htm