Page Comparison

...

The "RL?" column notes which files can be reloadable, but not necessarily which ones are since that may depends on various properties in shibboleth2.xml

File	RL?	Purpose	Tasks
Core Configuration
attribute-map.xml	Y(*)	Maps incoming SAML Attributes and/or NameID Formats into local variable/header names within the SP. The asterisk refers to the fact that this file should generally only be marked reloadable if you take care not to rely on HTTP request headers to consume the data.	Determining the data the SP consumes from IdPs and what to call it
attribute-policy.xml	Y	Controls rules for accepting incoming data from IdPs. Comes with a useful set of default rules for certain kinds of attributes and usually isn't needed very often beyond that.	Adding additional "scoped" attributes Rejecting certain attributes from certain IdPs (e.g. self-asserted names or email addresses) Adding custom attributes only valid for a specific IdP
protocols.xml	Y(*)	Defines underlying default paths and low level details that allow the system to auto-configure itself via the `<SSO>`, `<Logout>`, etc. elements. It isn't usually modified by deployers. It could be reloadable but has no effect until the core configuration is reloaded.	Generally none, but could be used to alter the default paths where SAML messages are processed
security-policy.xml	Y	Defines low-level rules for securing SAML message processing, and also supports explicitly turning off compromised cryptographic algorithms or overriding system defaults in that area. Rarely modified by deployers.	Adjusting algorithm rules if the system defaults aren't suitable Creating advanced rules for processing messages specific to particular IdPs (very unusual)
shibboleth2.xml	Y	Root configuration file of the SP, this is the main starting point for all changes and tasks excluding altering content rules on Apache	Just about everything that's not somewhere else, but particularly initial setup, adding metadata, adjusting session timeout, and content rules for IIS deployments
Logging Configuration
console.logger		Configures logging of the command line tools and the shibd command line when the configuration is "tested"
native.logger		Configures logging from the web server modules	Altering the default level Routing messages to a remote syslog collector
shibd.logger		Configures logging of the shibd process and the transaction/audit log (the actual transaction log format string is set in shibboleth2.xml)	Altering various logging levels Routing messages to someplace other than a local file
Credentials
sp-signing-key.pem	Y	Private key generated by installer used for signing of messages or client TLS authentication directly to IdPs	Overwriting your own signing key from a different install of the software
sp-signing-cert.pem	Y	Public key certificate generated by installer used for signing of messages or client TLS authentication directly to IdPs	Overwriting your own signing key from a different install of the software
sp-encrypt-key.pem	Y	Private key generated by installer used for decryption of incoming encrypted data from IdPs	Overwriting your own decryption key from a different install of the software
sp-encrypt-cert.pem	Y	Public key certificate generated by installer used for decryption of incoming encrypted data from IdPs	Overwriting your own decryption key from a different install of the software

Versions Compared

Old Version 1

New Version 2

Key