Configure Site Admin to Use a Single Pre-Authenticated User

You can configure Site Admin to always log in with a single pre-authenticated user. This option bypasses authentication so that any user that accesses Site Admin is logged in automatically with that user name and any associated permissions.

To use this option, you must set the server.reverseProxy system property to true, even if you do not want to use a reverse proxy. The reverse proxy is not required, because the normal Site Admin HTTP(S) ports still work.

You then set the siteadmin.reverse-proxy.pre-authenticated-roles and siteadmin.reverse-proxy.pre-authenticated-username system properties to the role and user name that you want to use for all users.

To configure Site Admin to use a single pre-authenticated user

  1. At the command line, send the java run command with the server.reverseProxy argument set to true, the siteadmin.reverse-proxy.pre-authenticated-roles argument set to the roles to use, and the siteadmin.reverse-proxy.pre-authenticated-username argument set to the user name to use. For example:

    java -Dserver.reverseProxy=true -Dsiteadmin.reverse-proxy.pre-authenticated-roles=admin,useradmin -Dsiteadmin.reverse-proxy.pre-authenticated-username=anon -Didol.siteadmin.home=[home directory] -Dserver.port=[port] -jar siteadmin.jar
  2. Restart Site Admin to apply your configuration changes.

If you run Site Admin as a service on Windows, you can also add the server.reverseProxy and siteadmin.reverse-proxy.pre-authenticated-username properties to the siteadmin.xml file.

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

When you modify the Site Admin configuration by modifying the XML file or start scripts, you must restart Site Admin 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 siteadmin restart to restart the service.