Skip to content

Commit 2c2b943

Browse files
committed
DOC-4418 RS: Enable TLS updates for new CM UI
1 parent c6904e1 commit 2c2b943

File tree

3 files changed

+8
-40
lines changed

3 files changed

+8
-40
lines changed

content/operate/rs/security/encryption/tls/enable-tls.md

Lines changed: 8 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -36,11 +36,11 @@ To enable mutual TLS for client connections:
3636

3737
1. Select **Mutual TLS (Client authentication)**.
3838

39-
{{<image filename="images/rs/screenshots/databases/security-mtls-clients.png" alt="Mutual TLS authentication configuration.">}}
39+
{{<image filename="images/rs/screenshots/databases/security-mtls-clients-7-8-2.png" alt="Mutual TLS authentication configuration.">}}
4040

4141
1. For each client certificate, select **+ Add certificate**, paste or upload the client certificate, then select **Done**.
4242

43-
If your database uses Replica Of or Active-Active replication, you also need to add the syncer certificates for the participating clusters. See [Enable TLS for Replica Of cluster connections](#enable-tls-for-replica-of-cluster-connections) or [Enable TLS for Active-Active cluster connections](#enable-tls-for-active-active-cluster-connections) for instructions.
43+
If your database uses Replica Of, you also need to add the syncer certificates for the participating clusters. See [Enable TLS for Replica Of cluster connections](#enable-tls-for-replica-of-cluster-connections) for instructions.
4444

4545
1. You can configure **Additional certificate validations** to further limit connections to clients with valid certificates.
4646

@@ -73,59 +73,27 @@ To enable mutual TLS for client connections:
7373

7474
1. Select **Save**.
7575

76-
{{< note >}}
7776
By default, Redis Enterprise Software validates client certificate expiration dates. You can use `rladmin` to turn off this behavior.
7877

7978
```sh
8079
rladmin tune db < db:id | name > mtls_allow_outdated_certs enabled
8180
```
82-
83-
{{< /note >}}
8481

8582
## Enable TLS for Active-Active cluster connections
8683

87-
To enable TLS for Active-Active cluster connections:
88-
89-
1. If you are using the new Cluster Manager UI, switch to the legacy admin console.
90-
91-
{{<image filename="images/rs/screenshots/switch-to-legacy-ui.png" width="300px" alt="Select switch to legacy admin console from the dropdown.">}}
92-
93-
1. [Retrieve syncer certificates.](#retrieve-syncer-certificates)
94-
95-
1. [Configure TLS certificates for Active-Active.](#configure-tls-certificates-for-active-active)
96-
97-
1. [Configure TLS on all participating clusters.](#configure-tls-on-all-participating-clusters)
98-
99-
{{< note >}}
10084
You cannot enable or turn off TLS after the Active-Active database is created, but you can change the TLS configuration.
101-
{{< /note >}}
102-
103-
### Retrieve syncer certificates
10485

105-
For each participating cluster, copy the syncer certificate from the **general** settings tab.
106-
107-
{{< image filename="/images/rs/general-settings-syncer-cert.png" alt="general-settings-syncer-cert" >}}
86+
To enable TLS for Active-Active cluster connections:
10887

109-
### Configure TLS certificates for Active-Active
88+
1. During [database creation]({{<relref "/operate/rs/databases/active-active/create">}}), expand the **TLS** configuration section.
11089

111-
1. During database creation (see [Create an Active-Active Geo-Replicated Database]({{< relref "/operate/rs/databases/active-active/create.md" >}}), select **Edit** from the **configuration** tab.
112-
1. Enable **TLS**.
113-
- **Enforce client authentication** is selected by default. If you clear this option, you will still enforce encryption, but TLS client authentication will be deactivated.
114-
1. Select **Require TLS for CRDB communication only** from the dropdown menu.
115-
{{< image filename="/images/rs/crdb-tls-all.png" alt="crdb-tls-all" >}}
116-
1. Select **Add** {{< image filename="/images/rs/icon_add.png#no-click" alt="Add" >}}
117-
1. Paste a syncer certificate into the text box.
118-
{{< image filename="/images/rs/database-tls-replica-certs.png" alt="Database TLS Configuration" >}}
119-
1. Save the syncer certificate. {{< image filename="/images/rs/icon_save.png#no-click" alt="Save" >}}
120-
1. Repeat this process, adding the syncer certificate for each participating cluster.
121-
1. Optional: If also you want to require TLS for client connections, select **Require TLS for All Communications** from the dropdown and add client certificates as well.
122-
1. Select **Update** at the bottom of the screen to save your configuration.
90+
1. Select **On** to enable TLS.
12391

124-
### Configure TLS on all participating clusters
92+
{{<image filename="images/rs/screenshots/databases/active-active-databases/enable-tls-for-active-active-db.png" alt="TLS is enabled on the Cluster Manager UI screen.">}}
12593

126-
Repeat this process on all participating clusters.
94+
1. Click **Create**.
12795

128-
To enforce TLS authentication, Active-Active databases require syncer certificates for each cluster connection. If every participating cluster doesn't have a syncer certificate for every other participating cluster, synchronization will fail.
96+
If you also want to require TLS for client connections, you must edit the Active-Active database configuration after creation. See [Enable TLS for client connections](#client) for instructions.
12997

13098
## Enable TLS for Replica Of cluster connections
13199

29 KB
Loading
93.4 KB
Loading

0 commit comments

Comments
 (0)