OpenID connect as A Federated IdP protocol
In order to provide the perspective an additional mechanism brings to the design approach, we are going to look into implementing OpenID connect, which has been used as a federation protocol comparable to, and different from SAML. This document will capture the differences from the SAML implementation for extending the Federated approach.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Steve Martinelli
- Definition:
- Approved
- Series goal:
- Accepted for kilo
- Implementation:
-
Implemented
- Milestone target:
-
2015.1.0
- Started by
- Steve Martinelli
- Completed by
- Morgan Fainberg
Related branches
Related bugs
Sprints
Whiteboard
I believe this is OpenID, which is a Federated IdP Protocol. Not to be confused with OpenID Connect.
OpenID http://
OpenIDConnect http://
David> Adam, we have already implemented SAML, OpenID and OpenID connect in Keystone and we know what the differences are: there are none, providing the federation API is specified correctly and generically.
Addressed by: https:/
Add openID Connect auth plugin for federation
Gerrit topic: https:/
Addressed by: https:/
Add openid connect support
Gerrit topic: https:/
Addressed by: https:/
Rename openid to oidc in test_auth_
Gerrit topic: https:/
Addressed by: https:/
Merge remote-tracking branch 'origin/master' into feature/
Work Items
Dependency tree

* Blueprints in grey have been implemented.