Configuration
On startup, security.manager for OGC loads the current configuration from the configuration directory.
The configuration directory has the following structure:
📒 .secman-ogc (1)
📄 application.properties (2)
📄 secrets.properties (3)
📄 server-config.json (4)
📂 policies (5)
📄 my-policies-1.json
📄 my-policies-2.json
📄 polygon-europe.geojson
| 1 | Configuration directory |
| 2 | General configuration file for security.manager for OGC (optional) |
| 3 | Secrets configuration file for storing sensitive configuration like passwords (optional) |
| 4 | Server configuration |
| 5 | Access policies directory with access policy files. |
General configuration file
The application.properties contains the general configuration options for CORS, logging, general security, etc.
Secrets configuration file
The secrets.properties contains the secret configuration options with sensitive information like passwords, secrets, or API keys.
Server configuration
The server-config.json contains the server configuration for the services to be protected, WMS or WFS, for example.
Policies folder
The policies folder contains the access policy files, each of which defines the access policies for a protected service.
In addition, files such as GeoJSON files, which may be required for authorization, are stored in this folder.
Policy files
An access policy file defines the access policies for a service in JSON format.
The name of this file can be freely chosen, but may only consist of alphanumeric characters and _, -, ., #, and @.
The file name must end with .json.