With SO, bpmn gets called by openstack adapter, sdnc adapter, appc-orchestrator sub applications.Each of these sub applications use a set of credentials to call bpmn.

During integration testing, we noticed that in the logs,
https://logs.onap.org/onap-integration/gating//119309-19/infrastructure-healthcheck/k8s-teardown/kubernetes-status/pod-onap-so-bpmn-infra-6696f87d77-j29kq-so-bpmn-infra.log
 "User 'so@so.onap.org' not found" repeatedly.
Since we don't see any issues with openstack & sdnc adapter any issues calling bpmn, we need to identify the sub application using wrong credentials to call bpmn (most probably appc-orchestrator?).
With OOM we have configured to use either basic or aaf credentials. We normally use basic credentials only. For some reason, the sub application seems to be using aaf credentials causing this issue