updates shared secret

Author: ZPain8464

content/docs/reference/reference.json

@@ -541,7 +541,7 @@
   "shared-secret-file": {
     "id": "shared-secret-file",
     "title": "Shared Secret File",
-    "path": "/shared-secret#shared-secret-file",
+    "path": "/shared-secret",
     "description": "File path containing base64-encoded shared secret.",
     "services": [],
     "type": "string",

content/docs/reference/shared-secret.mdx

@@ -15,82 +15,25 @@ import TabItem from '@theme/TabItem';
 
 # Shared Secret
 
-**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.
-
-### How to configure
-
-<Tabs>
-<TabItem value="Core" label="Core">
-
-| **Config file keys** | **Environment variables** | **Type** | **Usage**      |
-| :------------------- | :------------------------ | :------- | :------------- |
-| `shared_secret`      | `SHARED_SECRET`           | `string` | \***optional** |
-
-\* Standalone Pomerium Core configurations do not require a `shared_secret` or `shared_secret_file`. If you don't set a shared secret, Pomerium will generate one for you.
-
-:::enterprise Shared Secret in Enterprise Configurations
-
-If you're connecting to the [Enterprise Console](/docs/enterprise), your Pomerium Core and Enterprise configurations each require the same shared secret.
-
-See the [Enterprise Quickstart](/docs/enterprise/quickstart) for an example implementation.
-
-:::
+## Summary
 
-### Examples
+**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.
 
 :::note
 
 If you adjust your shared secret and/or how it's accessed by Pomerium, you may create a [**secret mismatch**](/docs/troubleshooting#shared-secret-mismatch).
 
 :::
 
-To generate a key, run the following command:
-
-```shell
-head -c32 /dev/urandom | base64
-```
-
-Add the value to your configuration file:
-
-```yaml
-shared_secret: wC4RFsEdM1gHFzvRt3XW+iWw6Ddt/1kKkdh66OKxiqs=
-```
-
-```bash
-SHARED_SECRET=wC4RFsEdM1gHFzvRt3XW+iWw6Ddt/1kKkdh66OKxiqs=
-```
-
-</TabItem>
-<TabItem value="Enterprise" label="Enterprise">
-
-`shared_secret` is a bootstrap configuration setting and is not configurable in the Console.
-
-</TabItem>
-<TabItem value="Kubernetes" label="Kubernetes">
-
-| **Name**                | **Type** | **Usage**    |
-| :---------------------- | :------- | :----------- |
-| `secrets.shared_secret` | `string` | **required** |
-
-See Kubernetes [bootstrap secrets](/docs/k8s/reference#spec) for more information.
-
-</TabItem>
-</Tabs>
-
-## Shared Secret File
-
-**Shared Secret File** is the location of a file containing 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.
-
-### How to configure
+## How to configure
 
 <Tabs>
 <TabItem value="Core" label="Core">
 
 | **Config file keys** | **Environment variables** | **Type** | **Usage**      |
 | :------------------- | :------------------------ | :------- | :------------- |
-| `shared_secret_file` | `SHARED_SECRET_FILE`      | `string` | \***optional** |
-
-\* Standalone Pomerium Core configurations do not require a `shared_secret` or `shared_secret_file`. If you don't set a shared secret, Pomerium will generate one for you.
+| `shared_secret`      | `SHARED_SECRET`           | `string` | **required** |
+| `shared_secret_file` | `SHARED_SECRET_FILE`      | `string` | **required** |
 
 :::enterprise Shared Secret in Enterprise Configurations
 
@@ -102,30 +45,26 @@ See the [Enterprise Quickstart](/docs/enterprise/quickstart) for an example impl
 
 ### Examples
 
-:::note
-
-If you adjust your shared secret and/or how it's accessed by Pomerium, you may create a [**secret mismatch**](/docs/troubleshooting#shared-secret-mismatch).
-
-:::
-
-`shared_secret_file` points to a file containing the secret. This is useful when deploying in environments that provide secret management like [Docker Swarm](https://docs.docker.com/engine/swarm/secrets/).
-
 To generate a key, run the following command:
 
 ```shell
 head -c32 /dev/urandom | base64
 ```
 
-Place the value in your `shared_secret_file`:
+Add the value to your configuration file:
 
 ```yaml
-shared_secret_file: '/run/secrets/POMERIUM_SHARED_SECRET'
+shared_secret: wC4RFsEdM1gHFzvRt3XW+iWw6Ddt/1kKkdh66OKxiqs=
+```
+
+```bash
+SHARED_SECRET_FILE='/run/secrets/POMERIUM_SHARED_SECRET'
 ```
 
 </TabItem>
 <TabItem value="Enterprise" label="Enterprise">
 
-`shared_secret_file` is a bootstrap configuration setting and is not configurable in the Console.
+`shared_secret` is a bootstrap configuration setting and is not configurable in the Console.
 
 </TabItem>
 <TabItem value="Kubernetes" label="Kubernetes">

static/_redirects

@@ -467,8 +467,8 @@ https://0-20-0.docs.pomerium.com/category/guides https://0-20-0.docs.pomerium.co
 /docs/reference/signing-key-file /docs/reference/signing-key
 
 # Shared Secret settings
-/docs/reference/shared-secret /docs/reference/shared-secret-settings#shared-secret
-/docs/reference/shared-secret-file /docs/reference/shared-secret-settings#shared-secret-file
+/docs/reference/shared-secret /docs/reference/shared-secret-settings
+/docs/reference/shared-secret-file /docs/reference/shared-secret-settings
 
 # Topics links - now concepts
 /docs/topics/auth-logs /docs/capabilities/audit-logs