IdP Configuration Configuration
This page provides information about various ways in which you can influence how the IdP loads/reads its configuration.
Loading Configuration Files
The service.xml configuration file provides information about all the other the configurations loaded into the IdP. Each service that reads a configuration may read any number of them. The result of reading more than one configuration is equivalent to merging all the configurations into one large file.
The IdP supports multiple mechanisms for fetching its configurations. The definition of what and how to fetch is known as a configuration resource and the IdP supports the following configuration resource types:
- Classpath Resource - Read a configuration resource from the IdP's classpath.
- Filesystem Resource - Reads a configuration file from the filesystem.
- HTTP Resource - Reads a configuration document fetched from an HTTP URL.
- File-backed HTTP Resource - Reads a configuration document fetched from an HTTP URL and caches it on the filesystem for use in the event that the remote server is unavailable.
Enabling Configuration Reloading
Most of the IdP configuration files can be watched and reloaded if a change is detected.
| Note | ||
|---|---|---|
| ||
Do NOT enable configuration reloading in a production environment unless you have a rigorous configuration testing process in place and used. |
Reloadable Services
The IdP contains four services which can be reloaded
...