forked from Venafi/vcert
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsample.multi.yaml
40 lines (40 loc) · 1.42 KB
/
sample.multi.yaml
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
# This is an unlikely scenario. Mostly to showcase the tool capabilities.
config:
connection:
type: tpp
url: https://my.tpp.instance.company.com
trustBundle: /path/to/my/trustbundle.pem
credentials:
accessToken: '{{ Env "TPP_ACCESS_TOKEN" }}'
refreshToken: '{{ Env "TPP_REFRESH_TOKEN" }}'
clientId: vcert-sdk
certificateTasks:
- name: myCertificate # Task Identifier, no relevance in tool run
renewBefore: 31d
request:
csr: local
subject:
# Templating needs to go between single quotes to avoid issues when refreshing tokens and saving back
commonName: '{{ Hostname | ToLower -}}.{{- Env "USERDNSDOMAIN" | ToLower }}'
country: US
locality: Salt Lake City
state: Utah
organization: Venafi Inc
orgUnits:
- engineering
- marketing
zone: "Open Source\\vcert"
installations:
- format: PEM
file: "/path/to/my/certificate/cert.cer"
chainFile: "/path/to/my/certificate/chain.cer"
keyFile: "/path/to/my/certificate/key.pem"
afterInstallAction: "echo Success!!!"
- format: JKS
file: "/path/to/my/certificate/cert.jks"
jksAlias: venafi
jksPassword: foobar123 # Minimum six characters length
afterInstallAction: "echo Success!!!"
- format: PKCS12
file: "/path/to/my/certificate/cert.p12"
afterInstallAction: "echo Success!!!"