Scenario - Configuring keystone federation

Scenario - Configuring keystone federation

Federation for keystone can be utilised in two ways:

  • Supporting keystone as a Service Provider (SP): consuming identity assertions issued by an external Identity Provider, such as SAML assertions or OpenID Connect claims.

  • Supporting keystone as an Identity Provider (IdP): fulfilling authentication requests on behalf of Service Providers.

    Important

    It is also possible to have one keystone act as an SP that consumes Identity from another keystone acting as an IdP. This will be discussed further in this document.

In keystone federation, the IdP and SP exchange information securely to enable a user on the IdP cloud to access resources of the SP cloud.

The following procedure describes how to set up federation:

  1. Configure keystone SPs.

  2. Configure the IdP:

    • Configure keystone as an IdP.

    • Configure Active Directory Federation Services (ADFS) 3.0 as an IdP.

  3. Configure the service provider:

    • Configure keystone as a federated service provider.

    • Configure keystone mappings.

  4. Run the authentication wrapper to use keystone-as-a-Service-Provider federation.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.