Use Keystone Trusts to avoid storing user credentials
Now keystone trusts have been merged, we need to figure out how to use trust tokens in order to avoid storing user credentials in our DB
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- High
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Steven Hardy
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
-
Implemented
- Milestone target:
-
2013.2
- Started by
- Steven Hardy
- Completed by
- Steven Hardy
Whiteboard
https:/
keystone trusts implementation:
https:/
Trusts extension API spec:
https:/
Blocked on the following keystoneclient and keystone reviews:
https:/
https:/
Gerrit topic: https:/
Addressed by: https:/
Migrate stored credentials to keystone trusts
Addressed by: https:/
Add trust_id and trustor_user_id Context and DB
Gerrit topic: https:/
Work Items
Dependency tree
* Blueprints in grey have been implemented.
