The Shibboleth software is a web-based single sign-on system made up of three components:
The following diagram shows the interaction between the user, located at their web browser, the IdP, located at the home organization, and the SP, located at the resource organization.
Given this very basic familiarity with the Shibboleth components and their interactions, the following documentation provides further detail. The section Understanding the Basics provides further information about the concepts and components within Shibboleth. The Identity Provider and Service Provider sections give further details relating specifically to their respective components.
Describes the goals of the Shibboleth software and the environments in which it operates.
Describes the general flow through the system.
Describes what metadata is and how it is used by Shibboleth.
Discusses what a user session is and a Shibboleth session differs from normal web application sessions.
Describes what Name Identifiers are and how they are used.
A glossary of terms used throughout this wiki.
|Entity Naming||Naming guidelines for systems|
|Attribute Naming||Naming guidelines for attributes|
Describes how one Shibboleth component identifiers itself to, and trusts, another.
Describes how a service provider determines a user's identity provider.
|Advanced Uses||Discussion of more advanced use cases.|
Describes the different request/response types that Shibboleth supports.
Describes how the IdP identifies and interacts with relying parties.
Describes how the IdP establishes and maintains sessions.
Describes how the IdP uses metadata.
|Attribute Storage||Discussion of attribute storage and access.|
Describes the skill set an IdP deployer should have.
Describes how the SP establishes and maintains sessions.
Describes how the SP uses metadata.
Discusses how information form the IdP can be used to control access to a resource.
Describes the skill set an SP deployer should have.