Skip to content

Commit e251dbc

Browse files
authored
docs: add Google Trust Services instructions (#1144)
* Create Google-Trust-Services.md Add basic details on using the GTS ACME endpoint. * Update README.md add a link to the Google Trust Services doc.
1 parent a7ee264 commit e251dbc

File tree

2 files changed

+19
-0
lines changed

2 files changed

+19
-0
lines changed

docs/Google-Trust-Services.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
## Google Trust Services
2+
3+
[Google Trust Service](https://pki.goog/) is an ACME CA with generous default quota and high ubiquity.
4+
5+
Using Google Trust Services through an ACME client, like in this container, allows for unlimited 90 days and multi-domains (SAN) certificates.
6+
7+
### Activation
8+
9+
Google Trust Services support is activated when the `ACME_CA_URI` environment variable is set to the Google Trust Services ACME endpoint (`https://dv.acme-v02.api.pki.goog/directory`).
10+
11+
### Account
12+
13+
Google Trust Services requires the use of an externally bound account. First create a [Google Trust Services account](https://cloud.google.com/certificate-manager/docs/public-ca-tutorial#request-key-hmac):
14+
15+
- provide the pre-generated [EAB credentials](https://tools.ietf.org/html/rfc8555#section-7.3.4) using the `ACME_EAB_KID` and `ACME_EAB_HMAC_KEY` environment variables.
16+
17+
These variables can be set on the proxied containers or directly on the **acme-companion** container.

docs/README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@
1616

1717
[Container configuration](./Container-configuration.md)
1818

19+
[Google Trust Services](./Google-Trust-Services.md)
20+
1921
[Persistent data](./Persistent-data.md)
2022

2123
[Standalone certificates](./Standalone-certificates.md)

0 commit comments

Comments
 (0)