forked from ecadlabs/signatory
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsignatory.yaml
50 lines (48 loc) · 1.5 KB
/
signatory.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
41
42
43
44
45
46
47
48
49
50
server:
# Address for the main HTTP server to listen on
address: :6732
# Address for the utility HTTP server to listen on
utility_address: :9583
vaults:
# Name is used to identify backend during import process
kms:
driver: cloudkms
config:
# See backend specific documentation
project: signatory
location: europe-north1
key_ring: hsm-ring
azure:
driver: azure
config:
# See backend specific documentation
vault: https://signatory.vault.azure.net/
tenant_id: cf5dd0ba-d3a3-4f3f-a688-06d12672f8ed
client_id: 5d29a974-edd0-4659-b933-7d9c56726649
client_pkcs12_certificate: principal.pfx
yubi:
driver: yubihsm
config:
# See backend specific documentation
address: localhost:12345
password: password
auth_key_id: 1
# List enabled public keys hashes here
tezos:
# Default policy allows "block" and "endorsement" operations
tz1Wz4ZabKRsz842Xuzy4a7CcWADfPVsPKus:
# Explicit policy
tz3MhmeqpudUqEX8PYTbNDF3CVcnnjNQoo8N:
# Setting `log_payloads` to `true` will cause Signatory to log operation
# payloads to `stdout`. This may be desirable for audit and investigative
# purposes.
log_payloads: true
allowed_operations:
# List of [generic, block, endorsement]
- generic
- block
- endorsement
allowed_kinds:
# List of [endorsement, ballot, reveal, transaction, origination, delegation, seed_nonce_revelation, activate_account]
- transaction
- endorsement