The Shibboleth 2 IdP uses the following configuration files to control various aspects of its operation:
It also relies on configuration of the web environment for some features.
The following tasks are basic configuration operations performed by most deployers.
Describes how to communicate with a new Service Provider.
Describes how to read a new source of metadata information and how to apply filters to a source.
Describes how to configuration the IdP's authentication mechanism.
Describes how to read in and prepare a new attribute that may be released to a service provider.
Describes how to define a new attribute filter policy in order to control the release of a configured attribute.
Describes how to use the IdP's status page.
Describes how to customize the IdP's logging files and describes the format of the Audit and Access logs.
Describes how to determine the IdP version number.
Describes how to generate a new key/certificate pair for the IdP.
The following tasks are usually not necessary for many IdP deployments and are more complicated than the basic configuration tasks and as such should not be done without a good understanding of how the IdP operates.
Describes how to customize configurations on a per relying party basis.
Describes how to add support for a new name identifier type either for the entire IdP or for a given service provider.
Describes how to read in new cryptographic credentials (e.g. private keys, certificates) and make them available for cryptographic operations.
Describes how to enable configure XML signing and encryption support.
Describes how to configure multiple running instances of an IdP to share state.
Describes how to enable the ECP profile handler included with the V2.3+ IdP.
|Error Handling with Velocity||Describes how to use Velocity instead of JSP for error handling.|
The following tasks are rarely needed for an IdP deployment. They can be quite complicated and should not be attempted without an excellent understanding on how the operation operates. Mistakes in these configurations can leave the IdP inoperable or insecure.
Describes how to configure a new trust engine that may be used to validate signatures and client certificates.
Describes how to customize the manner in which the IdP loads its configuration information. This includes loading configuration from URLs, enabling configuration reloading, etc.
The following tasks are descriptions contributed by IdP deployers. The are generally tasks that span multiple configuration locations (i.e. authentication and attribute management). The content of these documents are not watched as closely by the Shibboleth development team and may fall out of date as new releases are made. If this occurs please contact the development on the user's mailing list
Use multiple separate LDAP directories and user bases with a single IdP.
Issues that arise when configuring the Identity Provider to communicate with an Active Directory server.