You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"description": "Signing Key is the key used to sign a user's attestation JWT which can be consumed by upstream applications to pass along identifying user information like username, id, and groups.",
1481
1481
"services": [],
1482
1482
"type": "string",
@@ -1485,7 +1485,7 @@
1485
1485
"signing-key-file": {
1486
1486
"id": "signing-key-file",
1487
1487
"title": "Signing Key File",
1488
-
"path": "/signing-key-settings#signing-key-file",
1488
+
"path": "/signing-key",
1489
1489
"description": "File path to a secret containing the signing key, used to sign a user's attestation JWT which can be consumed by upstream applications to pass along identifying user information like username, id, and groups.",
Copy file name to clipboardexpand all lines: content/docs/reference/shared-secret.mdx
+1-3
Original file line number
Diff line number
Diff line change
@@ -13,9 +13,7 @@ toc_max_heading_level: 2
13
13
importTabsfrom'@theme/Tabs';
14
14
importTabItemfrom'@theme/TabItem';
15
15
16
-
# Shared Secret Settings
17
-
18
-
## Shared Secret
16
+
# Shared Secret
19
17
20
18
**Shared Secret** is the base64-encoded, 256-bit key used to mutually authenticate requests between Pomerium services. It's critical that secret keys are random, and stored safely.
This page discusses the signing key settings Pomerium uses to sign the Pomerium JWT that's sent to upstream services to verify a user's identity.
@@ -17,20 +17,19 @@ toc_max_heading_level: 2
17
17
importTabsfrom'@theme/Tabs';
18
18
importTabItemfrom'@theme/TabItem';
19
19
20
-
# Signing Key Settings
21
-
22
-
## Signing Key
20
+
# Signing Key
23
21
24
22
**Signing Key** is one or more PEM-encoded private keys used to sign a user's attestation JWT, which can be consumed by upstream applications to pass along identifying user information like username, id, and groups.
If set, the signing key's public key(s) can be retrieved by hitting Pomerium's well-known JWKS endpoint:
@@ -105,51 +114,3 @@ To implement key rotation, follow a 3-step process:
105
114
3. Remove the old key from the list.
106
115
107
116
With sufficient time between the steps, this process should be resilient to caching of the JWKS endpoint by applications.
108
-
109
-
## Signing Key File
110
-
111
-
**Signing Key File** is the path to a file containing a [Signing Key](#signing-key).
112
-
113
-
The signing key is the private key used to sign a user's attestation JWT, which can be consumed by upstream applications to pass along identifying user session information such as username, id, and groups.
114
-
115
-
See [Signing Key](#signing-key) for more information.
Signing Key File is useful when deploying in environments that provide secret management like [Docker Swarm](https://docs.docker.com/engine/swarm/secrets/).
0 commit comments