Ability to authorize interaction with entity properties
We need to be able to authorize specific groups of users to create, update, and read different properties of arbitrary entities.
Blueprint information
- Status:
- Complete
- Approver:
- Brian Waldon
- Priority:
- High
- Drafter:
- Brian Waldon
- Direction:
- Approved
- Assignee:
- Iccha Sethi
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
-
Implemented
- Milestone target:
-
2013.2
- Started by
- Iccha Sethi
- Completed by
- Mark Washenberger
Related branches
Sprints
Whiteboard
This shouldn't require API contract changes, so it can wait until Grizzly to happen.
misc links:-
futher discussion to be documented on:
https:/
Latest proposal (27 June): https:/
The latest proposal looks great to me. I'm afraid we won't have this in by havana-2, so I'm bumping it just to reflect that fact during the project updates.
Gerrit topic: https:/
Addressed by: https:/
Add Extra Properties class in domain layer
Addressed by: https:/
Rule parser for property protections
Addressed by: https:/
Property Protection Layer
Addressed by: https:/
Property Protection Layer
Addressed by: https:/
Adds property protection layer to gateway
Addressed by: https:/
Implement protected properties for API v1
Addressed by: https:/
Add policy style '@'/'!' rules to prop protections
Addressed by: https:/
Ensure prop protections are read/enforced in order
Addressed by: https:/
Add documentation for property protections
Addressed by: https:/
Using policies for protected properties
Addressed by: https:/
Use packaged version of ordereddict
Addressed by: https:/
Add documentation for property protections
Addressed by: https:/
Documentation for using policies for protected properties
Work Items
Dependency tree
* Blueprints in grey have been implemented.
