Pairwise testing is the process of validating the interconnections between OOF components and external dependencies in a lab environment. OOF supports functional testing in the form of simulations of some external dependencies, and PWT further validates the system with 'live' testing.
OOF-HAS → AAF
PWT of the Homing and Allocation Service (HAS) and the Application Authorization Service is has been performed by executing HAS in a local environment (a Mac laptop) accessing test instance of AAF in the WindRiver lab.
AAF test instance
A test instance of AAF is running in the WindRiver lab. Access to the lab can be granted by contacting Stephen Gooch at stephen.gooch@windriver.com. Jonathan Gathman is a resource on the AAF team that may be of help with questions (jg1555@att.com).
See here Integration / Developer Lab Access for more detail
The AAF instance is populated with a number of objects. Those relevant for HAS PWT are:
namespace:
org.onap.oof
roles:
org.onap.admin
org.onap.oof.owner
org.onap.oof.service
permissions:
org.onap.oof.access|*|*
org.onap.oof.access|*|read
org.onap.oof.certman|local|request, ignoreIPs, showpass
Once VPN access is established, the following curl command will provide the associated response:
$ curl -u aaf_admin@people.osaaf.org:demo123456! --cacert AAF_RootCA.cer --header "Accept: application/Perms+json;q=1.0;charset=utf-8;version=2.1,application/json;q=1.0;version=2.1,*/*;q=1.0" https://aaf-onap-test.osaaf.org:8100/authz/perms/org.onap.oof.access
{"perm":[{"type":"org.onap.oof.access","instance":"*","action":"*","roles":["org.onap.oof|admin"],"description":"AAF Namespace Write Access"},{"type":"org.onap.oof.access","instance":"*","action":"read","roles":["org.onap.oof|owner"],"description":"AAF Namespace Read Access"}]}
TBD:
- modify/configure has/conductor/conductor/api/adapters/aaf/aaf_authentication.py to use test AAF URL, ca cert, and username/password
- execute has in integration lab
- construct additional test scenarios to validate all code paths