Ensure an entity ID allows routing of API call to correct backend
During IceHouse, we had several proposals (and indeed code ready to merge) that solved the issue of correctly determining the domain and driver for an API call that only contains a user or group ID. This is needed for both multi-backend as well as Federation support. However, the approaches (e.g. either encode the domain into the ID or alternatively have an SQL mapping table) have their pros and cons. We need to settle on our approach and implement.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- High
- Drafter:
- Henry Nash
- Direction:
- Approved
- Assignee:
- Henry Nash
- Definition:
- Pending Approval
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2014.2
- Started by
- Henry Nash
- Completed by
- Dolph Mathews
Related branches
Related bugs
Sprints
Whiteboard
A patch with the mapping table approach can be found at: https:/
Gerrit topic: https:/
Addressed by: https:/
multi-backend support for identity
Gerrit topic: https:/
Addressed by: https:/
Cross Backend Unique Idenifiers for User and Group Entities
Addressed by: https:/
Minor doc fix
Addressed by: https:/
Debug messages don't need translations
Addressed by: https:/
Adds a newline for pep8 compliance
Addressed by: https:/
Stops overriding a builtin for pep8 compliance
Addressed by: https:/
Always use sha1 for cross backend unique identifiers
Addressed by: https:/
Migrate ID generation for users and groups from controller to manager
Addressed by: https:/
Add identity mapping capability
