Bug 1053722
| Summary: | [RFE][keystone]: External Identity Providers | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | RHOS Integration <rhos-integ> |
| Component: | openstack-keystone | Assignee: | RHOS Maint <rhos-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Ami Jeain <ajeain> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | aberezin, ayoung, breeler, markmc, nkinder, ukalifon, yeylon |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | 6.0 (Juno) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://blueprints.launchpad.net/keystone/+spec/identity-providers | ||
| Whiteboard: | upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_pending-approval | ||
| Fixed In Version: | openstack-keystone-2014.1-4.el7ost | Doc Type: | Enhancement |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-07-08 15:25:02 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1041881, 1082414 | ||
|
Description
RHOS Integration
2014-01-15 17:01:19 UTC
*** Bug 1041870 has been marked as a duplicate of this bug. *** What external providers are there, for example? Is this feature the same as federation, or the integration with LDAP? (In reply to Udi from comment #3) > What external providers are there, for example? Is this feature the same as > federation, or the integration with LDAP? This is covered by federation, so you should fovcus on the federation API doc instead of the referenced blueprint: https://github.com/openstack/identity-api/blob/master/openstack-identity-api/v3/src/markdown/identity-api-v3-os-federation-ext.md Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-0854.html |