Currently VES supports 4 authentication methods:

noAuth  --> Works by default. No changes are required.

basicAuth      --> Works with/without https healthcheck endpoint (readiness) defined; DCAE healthcheck pass on either case. VES blueprint needs to be overwritten.
certOnly        --> Works only when https healthcheck endpoint (readiness) is removed from blueprint; DCAE healthcheck also pass (when readiness is not explicitly defined). VES blueprint needs to be overwritten.
certBasicAuth-->Works with/without https healthcheck endpoint (readiness) defined; DCAE healthcheck pass on either case. VES blueprint needs to be overwritten.

For Dublin, there is created separate jira (DCAEGEN2-1593) for documentation updates to include steps for deploying VESCollector with above authentication enabled.

Readiness support on certOnly mode can be dealt vwith healtchecks disabled. Support for healtchecks is planned as future enhancement (DCAEGEN2-1594).

For enabling TLS, as new application port is involved the service should be redeployed (by modifying the parameters in blueprint), esp when changing from noAuth to basicAuth/certOnly/certBasicAuth. The latter 3 types use 8443 while the noAuth uses 8080. Any changes within basicAuth/certOnly/certBasicAuth can be done through consul update as k8s deployment descriptor (which contains the service definition and healthcheck spec) are still valid.

High level test cases for auth.method = "basicAuth"  :

When application is setup for TLS and auth.method = "basicAuth", healthcheck endpoint must be using 8443 (change submitted to override and support 8080 for healthcheck is not required nor valid).

To change VES Collector flag to basic.auth and adopt healthhecks to use HTTPS, there is need to change VES blueprints. Steps:

1. Copy attached k8s-ves-0529-secure.yaml file to ONAP Bootstrap node
2. From Rancher node find bootstrap pod: kubectl -n onap get pod | grep -i bootstrap
3. Login to found in point 1 pod: kubectl exec -it <bootstrap_pod_name> -n onap bash
4. Uninstal VES: cfy uninstall ves
5. Delete VES blueprint: cfy blueprints delete ves
6. Overwrite VES default blueprint with copied k8s-ves-0529-secure.yaml: copy new bp - k8s-ves-0529-secure.yaml as /blueprints/k8s-ves.yaml
7. Apply new blueprint: cfy install -b ves -d ves -i /inputs/k8s-ves-inputs.yaml  /blueprints/k8s-ves.yaml

T01

curl -vk --cert rootCA.crt --key rootCA.key --pass collector -u sample1:sample1-X POST https://192.168.0.22:30417/eventListener/v7 -d @event.json  "Content-Type: application/json"

T02

T03

curl -vk -u sample1:sample1-X POST https://192.168.0.22:30417/eventListener/v7 -d @event.json --header "Content-Type: application/json"