E&O Documentation Inputs
Context and Scope
Ahead of R3 release the broader E&O team needs to provide documentation explaining the options for enforcing entitlement. We will also need to provide test cases to enable certification. At the completion of the incubator we will need a handover of this information so we can proceed to create the documentation.
Decision
We will need the decision to be made about how the 'combined' approach to AuthZ is going to work. In simple terms what use cases can be satisfied by use of the legal tags and creation/population of the ACL's (the static approach), versus those that use the policy engine (the dynamic approach).
We also need to agree the resolve the current naming of the different services and ensure that they reflect the use/purpose and 'make sense' to the end-user
Rationale
Needed ahead of testing and release.
Consequences
We need this issue to be resolved so that we can complete the release documentation. It is also needed so that we can map the different entitlement use cases to the different possible approaches and judge the impact on performance of different decisions/mechanisms.
Decision Criteria and Trade Offs
- Performance
- Usability