blob: 4b8fe2055bc75db483c4f37c4468604da0aa9691 [file] [log] [blame]
Sai Gandhamd67a9de2018-05-25 15:48:11 +00001.. This work is licensed under a Creative Commons Attribution 4.0 International License.
2.. http://creativecommons.org/licenses/by/4.0
3
Instrumentalbbe71542018-05-25 12:29:38 -05004Client Configuration
5====================
Sai Gandhamd67a9de2018-05-25 15:48:11 +00006
Sai Gandhambd61eba2018-06-13 18:24:21 +00007TEST version of "cadi.properties"
8---------------------------------
9These properties point you to the ONAP TEST environment.
10
11Properties are separated into
12
13 * etc
14 * main Property file which provides Client specific info. As a client, this could be put in container, or placed on Host Box
15 * The important thing is to LINK the property with Location and Certificate Properties, see "local"
16 * local
17 * where there is Machine specific information (i.e. GEO Location (Latitude/Longitude)
18 * where this is Machine specific Certificates (for running services)
19 * This is because the certificates used must match the Endpoint that the Container is running on
20 * Note Certificate Manager can Place all these components together in one place.
21 * For April, 2018, please write Jonathan.gathman@att.com for credentials until TEST Env with Certificate Manager is fully tested. Include
22 1. AAF Namespace (you MUST be the owner for the request to be accepted)
23 2. Fully Qualified App ID (ID + Namespace)
24 3. Machine to be deployed on.
25
26Client Credentials
27------------------
28For Beijing, full TLS is expected among all components. AAF provides the "Certificate Manager" which can "Place" Certificate information
29
30Example Source Code
31-------------------
Sai Gandham5e236c72018-06-15 00:44:18 -050032Note the FULL class is available in the authz repo, cadi_aaf/org/onap/aaf/client/sample/Sample.java