Changed aaiEndpoint to point to new server name 49/20449/1
authorJim Hahn <jrh3@att.com>
Tue, 24 Oct 2017 21:42:44 +0000 (17:42 -0400)
committerJim Hahn <jrh3@att.com>
Tue, 24 Oct 2017 21:45:10 +0000 (17:45 -0400)
aaiEndpoint was pointing to the vm1 server which is aliased to the new
server.  However, as the new server's certificate does not include the
alias as one of its alternate names, things were unable to connect. The
endpoint has now been changed to match the new server name, thus the SSL
ceritifcate should match now. Note: for this to work, the new server
name must be found in DNS (or /etc/hosts).

Change-Id: I75362c92876607e795e9a98969c8a0693cae1af3
Issue-Id: SO-249
Signed-off-by: Jim Hahn <jrh3@att.com>
environments/mso-docker.json

index 1c5d5ac..9011843 100644 (file)
       "mso.sniro.endpoint": "/optimizationInstance/V1/create",
       "mso.sniro.callback": "/adapters/rest/SDNCNotify/SNIROResponse",
       "mso.infra.customer.id": "21014aa2-526b-11e6-beb8-9e71128cae77",
-      "aaiEndpoint": "https://c1.vm1.aai.simpledemo.openecomp.org:8443",
+      "aaiEndpoint": "https://aai.api.simpledemo.openecomp.org:8443",
       "aaiAuth": "2630606608347B7124C244AB0FE34F6F",
       "adaptersNamespace": "http:://org.openecomp.mso",
       "adaptersCompletemsoprocessEndpoint": "http://mso:8080/CompleteMsoProcess",