Integration details
A&AI webservices resources and traversal are integrated with AAF through the Cadi filter. The request workflow looks as follows:
- The request is authenticated in AAF
- TODO: the request should be authorized in the future
- If the request passes all the checks (authentication and in the future authorization), it is forwarded to the A&AI servlet which handles the web services.
...
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_advanced and org.onap.aai.resources_readonly and org.onap.aai.traversal_basic. These roles will be assigned to all users/applications which access A&AI web services.
| Role name | Meaning |
|---|---|
| org.onap.aai.resources_all | read + write access to the resources web service |
| org.onap.aai.resources_readonly | read-only access to the resources web service |
| org.onap.aai.traversal_advanced | applications may issue basic and advanced queries in the traversal web service |
| org.onap.aai.traversal_basic | applications may issue only basic queries in the traversal web service |
...