Integration details
...
There will be a separate permission for traversal and resources web services. Let's call these permissions org.onap.aai.resources and org.onap.aai.traversal. For now we will not distinguish between different objects we could affect, so the instance will always be "*" meaning everything. Actions will be mapped to HTTP verbs - GET, PUT, POST, DELETE, PATCH.
For a seemless transition to AAF, the first roles we use for our clients will be called org.onap.aai.resources_all and org.onap.aai.traversal_all with read and write permission and org.onap.aai.resources_readonly and org.onap.aai.traversal_readonly with read only permission. These roles will be assigned to all users/applications which access A&AI web services.
| Role org.onap.aai.traversal_all |
|---|
| Permission type | instances | action |
|---|
| org.onap.aai.traversal | * | get | | org.onap.aai.traversal | * | put | | org.onap.aai.traversal | * | post | | org.onap.aai.traversal | * | delete | | org.onap.aai.traversal | * | patch |
|
| Role org.onap.aai.resources_all |
|---|
| Permission type | instances | action |
|---|
| org.onap.aai.resources | * | get | | org.onap.aai.resources | * | put | | org.onap.aai.resources | * | post | | org.onap.aai.resources | * | delete | | org.onap.aai.resources | * | patch |
|
| Role org.onap.aai.resources_readonly |
|---|
| Permission type | instances | action |
|---|
| org.onap.aai.resources | * | get |
|
| Role org.onap.aai.traversal_readonly |
|---|
| Permission type | instances | action |
|---|
| org.onap.aai.traversal |
|
* | put | org.onap.aai.traversal | * | postOpen questions
- How do we enable AAF since it has to have a connection to the windriver lab? Or we enable it only in special deployments?
...