diff options
| author |   Ubuntu <lji@research.att.com> | 2017-02-24 21:19:41 +0000 |
|---|---|---|
| committer | Ubuntu <lji@research.att.com> | 2017-02-24 21:19:41 +0000 |
| commit | 2a392869cb8013245ad4a764363f8fb8e9654de9 (patch) | |
| tree | 4d7fbe5a3e74526af9fd84fbf9f5e116ccfa7a9e /docker_files/cadi.properties | |
| parent | dd7aeafdb1d7596c1e825c7c12b2ab672bba25b9 (diff) | |
push another branch
Change-Id: Ibe8c9a38801d10f6c95fd7da4750ee64392a8b1b
Signed-off-by: Ubuntu <lji@research.att.com>
Diffstat (limited to 'docker_files/cadi.properties')
| -rw-r--r-- | docker_files/cadi.properties | 18 |
1 files changed, 17 insertions, 1 deletions
diff --git a/docker_files/cadi.properties b/docker_files/cadi.properties index 17aaabe..9c95e9c 100644 --- a/docker_files/cadi.properties +++ b/docker_files/cadi.properties @@ -4,11 +4,21 @@ #For more information on utilizing the AAF framework, please goto wiki link: #AAF wiki link: http://wiki.web.att.com/display/aaf/AAF+Documentation +#In order to test functionality of cadi-ajsc-plugin locally (pertaining to GLO (AT&T Global Login)), you will need an AT&T cross +#domain cookie. Cadi "should" find your hostname for you. However, we have seen some situations where this fails. A Local testing +#modification can include modifying your hosts file so that you can use "mywebserver.att.com" for your localhost in order +#to test/verify GLO functionality locally. If you are on a Windows machine, you will already have a machine name associated with +#it that will utilize an AT&T domain such as "sbc.com". You may need to add your AT&T domain to this as a comma separated list depending +#upon your particular machine domain. This property is commented out as cadi SHOULD find your machine name. With version 1.2.1 of cadi, +#it appears to resolve Mac machine names as well, now. But, this can be somewhat inconsistent depending on your specific working envrironment. +#hostname=mywebserver.att.com + #Setting csp_domain to PROD will allow for testing using your attuid and password through GLO. #csp_domain=PROD #csp_devl_localhost=true -basic_realm=opencomp.org +basic_realm=csp.att.com +#basic_realm=aaf.att.com basic_warn=TRUE cadi_loglevel=DEBUG @@ -17,6 +27,11 @@ cadi_keyfile=/appl/dmaapMR1/etc/keyfile # Configure AAF aaf_url=https://DME2RESOLVE/service=com.att.authz.AuthorizationService/version=2.0/envContext=DEV/routeOffer=BAU_SE +# lji: according to this web page: https://wiki.web.att.com/display/soacloud/DME2+-+URI+Patterns, DME2 supports a direct URL mode: +# Format 3: DIRECT: http://host:port/service=?/version=?/envContext=?/routeOffer=? +# Point to a specific host:port and call the service there.No lookup/resolution by DME2 client. +#aaf_url=http://10.0.17.1:8101/service=com.att.authz.AuthorizationService/version=2.0/envContext=TEST/routeOffer=BAU_SE + #AJSC - MECHID aaf_id=dgl@openecomp.org aaf_password=enc:f2u5br1mh29M02- @@ -29,6 +44,7 @@ aaf_user_expires=60000 aaf_high_count=1000000 +# Some Libs need System Property Sets (i.e. AT&T Discovery) # The following properties are being set by the AJSC Container and should NOT need to be set here. AFT_LATITUDE=33.823589 AFT_LONGITUDE=-84.366982 |