Deploy security.manager for OGC web app under '/'

This how-to describes how you can make security.manager for OGC available on the root context path, i.e. under https://secman.example.com/ instead of https://secman.example.com/secman-ogc/.

By default, you deploy security.manager for OGC under the path /secman-ogc, so clients access protected services via a URL like https://secman.example.com/secman-ogc/. You can also make security.manager for OGC available via other paths, for example via the root context path /.

In this guide you will find all the steps necessary to make an existing standard installation of security.manager for OGC available via the root context path.

Prerequisites

  • All prerequisites that apply to the installation of security.manager for OGC also apply.

  • You are not running any other web app on the root context path in Tomcat.

Remove existing web app

If you have already installed the security.manager web app as described in the installation guide, you must first remove the web app from the Tomcat webapps/ folder. To do this, proceed as follows:

  1. Stop the Tomcat server.

  2. Check whether the file [TOMCAT]/webapps/secman-ogc/WEB-INF/classes/custom-application.properties contains entries that you want to keep. If so, save this file in another location.

  3. Delete the file secman-ogc.war and the folder secman-ogc/ from [TOMCAT]/webapps/.

Do not remove any other files, especially not the configuration files. You can continue to use the configuration without any changes.

Deploy web app on root context path

  1. Copy [SECMAN_DIST]/secman-ogc.war to the folder [TOMCAT]/webapps. This ensures that you are using the secman-ogc.war file of the desired release version.

  2. Rename the file [TOMCAT]/webapps/secman-ogc.war to [TOMCAT]/webapps/ROOT.war.

  3. (Optional) Transfer the entries from the saved custom-application.properties file. To do this, you must first unpack the file [TOMCAT]/webapps/ROOT.war in place, so that the directory [TOMCAT]/webapps/ROOT/ is created. Transfer the desired entries from the saved custom-application.properties file to the file [TOMCAT]/webapps/ROOT/WEB-INF/classes/custom-application.properties.

  4. Restart the Tomcat server.

Once Tomcat has deployed the security.manager for OGC web app, you can access the application via the following URL: https://secman.example.com/.

Deploy web app on another path

If you want to make security.manager for OGC available via another path, the procedure is analogous to deploying on the root context path. When renaming the web app from the distribution directory, do not use ROOT.war as the file name but <context-path>.war. Replace <context-path> with the path component under which security.manager for OGC should be accessible.