Integration details

A&AI webservices resources and traversal are integrated with AAF through the Cadi filter. The request workflow looks as follows:

1. The request is authenticated in AAF
2. TODO: the request should be authorized in the future
3. 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.

The AAF model

Permissions in AAF are triplets - type, instance, action.

• Type: core name of the permission
• Instance: the object that is being interacted
• Action: What is happening with this object

Users have roles assigned and each role has permissions.

A&AI permissions for Casablanca

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.

Resources webservice AAF role and permission setup

role create org.onap.aai.resources_all
perm create org.onap.aai.resources * get org.onap.aai.resources_all
perm create org.onap.aai.resources * put org.onap.aai.resources_all
perm create org.onap.aai.resources * post org.onap.aai.resources_all
perm create org.onap.aai.resources * patch org.onap.aai.resources_all
perm create org.onap.aai.resources * delete org.onap.aai.resources_all
user role add demo@people.osaaf.org org.onap.aai.resources_all #just an example, add role to the correct user
role create org.onap.aai.resources_readonly
perm create org.onap.aai.resources * get org.onap.aai.resources_readonly

Open questions

1. How are permissions and roles for traversal modeled? What are the requirements?
2. How do we enable AAF since it has to have a connection to the windriver lab? Or we enable it only in special deployments?
3. What are the variable configuration parameters of AAF? - the certificate, AAF server IP, permission names? Whaat to externalise to OOM?
4. Who creates the roles and permissions during the new release, who and how maintains these scripts?