...
| Note | ||
|---|---|---|
| ||
Do NOT enable configuration reloading in a production environment unless you have a rigorous configuration testing process in place and used. |
Reloadable Services
| Info |
|---|
To configure automatic reloading of Service Provider metadata please refer to the arguments for MetadataProvider within relying-party.xml. Reloading relying party configuration manager service is not intended to be used for reloading changes to metadata. |
The IdP contains four services which can be reloaded
- attribute resolver - responsible for fetching and creating attributes, controlled by $IDP_HOME/conf/attribute-resolver.xml
- attribute filtering engine - responsible for filtering attributes based on policy, controlled by $IDP_HOME/conf/attribute-filter.xml
- profile handler manager - responsible for defining IdP endpoints (profile handlers), controlled by $IDP_HOME/conf/handler.xml
- relying party configuration mangermanager - responsible for managing per relying party configurations, controlled by _ $IDP_HOME/conf/relying-party.xml
To enabled enable service, and hence configuration, reloading you edit the service definition in the service configuration file, $IDP_HOME/conf/service.xml. Each Service element has two optional attributes that control service reloading:
- configurationResourcePollingFrequency - the frequency with which the service's configuration(s) are polled for changes, expressed as an interval either in milliseconds or in ISO format XML duration notation (e.g., "PT15M" for "every 15 minutes")
- configurationResourcePollingRetryAttempts - number of times the IdP will attempt to reload a failed configuration before giving up, default value of 3.
...