{"push_id":737148941,"size":1,"distinct_size":1,"ref":"refs/heads/keystone-sp","head":"8745679f851f3e5a7496d7a30fa5832304e35b32","before":"caa7564b48d3d39d8d3ecb3f2a79691373872d78","commits":[{"sha":"8745679f851f3e5a7496d7a30fa5832304e35b32","author":{"email":"867e6f7716cd7d89b2aa6d04c9799a31b0e6903e@gmail.com","name":"Miguel Grinberg"},"message":"Keystone Federation Service Provider Configuration\n\nThis patch adds the ability to configure Keystone as a Service\nProvider (SP) for a Federated Identity Provider (IdP).\n\n* New variables to configure Keystone as a service provider are now\n  supported under a root `keystone_sp` variable. Example configurations\n  can be seen in Keystone's defaults file. This configuration includes\n  the list of identity providers and trusted dashboards. (At this time\n  only one identity provider is supported).\n\n* Identity provider configuration includes the remote-to-local user\n  mapping and the list of remote attributes the SP can obtain from the\n  IdP.\n\n* Shibboleth is installed and configured in the Keystone containers when\n  SP configuration is present.\n\n* Horizon is configured for SSO login\n\nDocImpact\nUpgradeImpact\nImplements: blueprint keystone-federation\nChange-Id: I78b3d740434ea4b3ca0bd9f144e4a07026be23c6\nCo-Authored-By: Jesse Pretorius <jesse.pretorius@rackspace.co.uk>","distinct":true,"url":"https://api.github.com/repos/miguelgrinberg/os-ansible-deployment/commits/8745679f851f3e5a7496d7a30fa5832304e35b32"}]}