Table of Contents |
---|
Obtain the Jars
NOTE: We'll be reducing these very quickly to only those trigger Dependencies. You do NOT need the whole list.
Maven - TODO give examples of latest version Dependencies
This Dependency will pick up all the required dependencies
Code Block |
---|
<dependency>
|
Code Block |
<dependencyManagement> <dependencies> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-misc-env</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-misc-log4j</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-misc-rosetta</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-misc-xgen</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-cadi-core</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-cadi-client</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-cadi-aaf</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-cadi-aaf</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-cadi-oauth-enduser</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-cadi-shiro</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-auth-client</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-auth-core</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-auth-cass</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-auth-cmd</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-auth-oauth</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-auth-deforg</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-auth-service</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-auth-hello</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-auth-locate</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-auth-fs</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-auth-gui</artifactId> <version>2.1.0</version> </dependency> <dependency> <groupId>org.onap.aaf.authz</groupId> <artifactId>aaf-authcadi-certman<aaf</artifactId> <version>2.1.0</version> </dependency> </dependencies> </dependencyManagement> |
TEST version of "cadi.properties"
...
- etc
- main Property file which provides Client specific info. As a client, this could be put in container, or placed on Host Box
- The important thing is to LINK the property with Location and Certificate Properties, see "local"
- local
- where there is Machine specific information (i.e. GEO Location (Latitude/Longitude)
- where this is Machine specific Certificates (for running services)
- This is because the certificates used must match the Endpoint that the Container is running on
- Note Certificate Manager can Place all these components together in one place.
- For April, 2018, please write Jonathan.gathman@att.com for credentials until TEST Env with Certificate Manager is fully tested. Include
- AAF Namespace (you MUST be the owner for the request to be accepted)
- Fully Qualified App ID (ID + Namespace)
- Machine to be deployed on.
Client Credentials
For Beijing, full TLS is expected among all components. AAF provides the "Certificate Manager" which can "Place" Certificate information
...