How-to guides

This how-to describes how to connect security.manager for OGC to the Identity Service so that you can bind policies to roles of authenticated users.

This how-to describes how you can change the path of the data directory of security.manager for OGC.

This how-to describes how you can change the path of the configuration directory from which security.manager for OGC reads its configuration.

This how-to describes how to disable URL rewriting in security.manager for OGC and let the secured service generate correct URLs itself.

This how-to describes how you can run security.manager for OGC without Tomcat using a simple command from the command line.

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/.

This how-to describes how you can reference roles from an Identity Provider in policies when you have connected security.manager for OGC with an Identity Service.

This how-to describes how you can use a service of type FORWARD to allow access to arbitrary paths on the target server via security.manager for OGC.

This how-to describes how you can protect services for which security.manager for OGC does not offer fine-grained access control. These can be service types such as OGC API Features services, Web Map Tile Services (WMTS), or other arbitrary HTTP service endpoints.

This how-to describes how to protect multiple services with different service types, e.g. WMS and WFS, on the same path.

This how-to describes how to protect a service that requires HTTP Basic Authentication for access.

This how-to describes how to use a service secured with security.manager for OGC in QGIS.

This how-to describes how to use a service secured with security.manager for OGC in ArcGIS Pro.