...
- AccessRequirement itself can have similar terms. AccessRequirements do not have name. Without the context of which subject it applies too, it is hard for user to identify which AccessRequirement they wants.
- ACT members have to adapt to a new way to use AccessRequirement.
Questions:
...
Update:
After discussion on July 7th, 2017, we decided that the cons in option 2 can be addressed by the client presenting the same workflow to users, and handle more API calls in the background. This made option 2 a better choice since it addresses both problem #1 and #2. It also allows us to address #3 later.
New Services
These are APIs for option 2.
| Action | Intended Users | Method | URI | RequestBody | ResponseBody |
|---|---|---|---|---|---|
| Apply an AccessRequirement to a list of subjects | ACT | PUT | /accessRequirement/{id}/association | AccessRequirementAssociationRequest | |
| Removing a list of subjects from an AccessRequirement | ACT | DELETE | /accessRequirement/{id}/association | AccessRequirementAssociationRequest |
| AccessRequirementAssociationRequest |
|---|
| List<RestrictableObjectDescriptor> subjects |