...
Most of the configuration is no longer reloadable in the style of older versions, with the exception of the two XML-based configurations.
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Existing/Compatible
The XML AccessControl and RequestMapper syntaxes are structurally expected to remain mostly compatible/similar to V3, with the exception that the RequestMapper would be in a separate file (due to the surrounding configuration being non-XML-based, so embedding it no longer “fits”). The separate file is assumed to be rooted in a <RequestMap>
element. AccessControl can be embedded in it as before, or placed in external files (more typically via the Apache module’s support for this).
...
No other values currently defined, extension point allowing for alternative implementations of the bulk of the agent library’s configuration and handling of various components. The old SP has a similar extension point but it’s never been used and the setting won’t normally appear.
allowedSchemes = https http
Space-delimited list of URL schemes permitted to appear in URLs when redirects are issued.
extraAuthTypes = custom1 custom2
Space-delimited list of Apache AuthTypes (unused otherwise) to process as though they were “shibboleth”, which is always included and is the default AuthType the module processes.
[extensions]
<pathname> = true | false
...
Basic means of overriding logging level for specific categories, but notably this isn’t hierarchical as with more full-featured logging libraries.
[remoting]
type = HTTP
Controls the agent/hub remoting service to use, this is the only type expected to be implemented.
[session-cache]
type = filesystem | storage | cookie
Controls the session cache implementation to use. These are “expected” types, but the only certainties are the first type, using the file system or calling on the hub to access a Java-based StorageService implementation such as a database.
[request-mapper]
type = XML | Native
Controls the RequestMapper implementation to use. The XML type essentially points to a reloadable external XML file to hold the configuration, while the Native type is for Apache to turn off the extra mapping layer (same as in V3).
path = <pathname>
For the XML type, specifies the local file containing the XML.
reloadChanges = true | false
Whether to monitor the file for reloads, which occur in the foregrund after taking a read lock, based on file modification time. C++-14 support is required for this code to be active and doing so introduces shared locking to the use of the component.