blob: 98dcfb9b6dd3a002618cd8042f4edf9f62cf2311 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
|
# Cert service client *(deprecated)*
> Deprecated since Istanbul release in favor of Cert Manager certificates
> (for more details see certServiceK8sExternalProvider submodule).
### Project building
```
mvn clean package
```
### Install the package into the local repository
```
mvn clean install
```
### Building Docker image and install the package into the local repository
```
mvn clean install -P docker
```
### Nexus container image
```
nexus3.onap.org:10001/onap/org.onap.oom.platform.cert-service.oom-certservice-client:latest
```
### Running local client application as standalone docker container
CertService API and client must be running in same network.
You need certificate and trust anchors (in JKS format) to connect to CertService API via HTTPS. Information how to generate truststore and keystore files you can find in CertService main README.
Information how to run you can find in CertService main README and official documentation, see [Read The Docs](https://docs.onap.org/projects/onap-oom-platform-cert-service/en/latest/sections/usage.html)
### Logs locally
path:
```
var/log/onap/oom/certservice-client/certservice-client.log
```
### Logs in Docker container
```
docker logs oom-certservice-client
```
###Exit codes
```
0 Success
1 Invalid client configuration
2 Invalid CSR configuration
3 Fail in key pair generation
4 Fail in CSR generation
5 CertService HTTP unsuccessful response
6 Internal HTTP Client connection problem
7 Fail in PEM conversion
8 Fail in Private Key to PEM Encoding
9 Wrong TLS configuration
10 File could not be created
|
