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
1. For each client certificate, select **+ Add certificate**, paste or upload the client certificate, then select **Done**.
42
42
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.
44
44
45
45
1. You can configure **Additional certificate validations** to further limit connections to clients with valid certificates.
46
46
@@ -73,59 +73,27 @@ To enable mutual TLS for client connections:
73
73
74
74
1. Select **Save**.
75
75
76
-
{{< note >}}
77
76
By default, Redis Enterprise Software validates client certificate expiration dates. You can use `rladmin` to turn off this behavior.
78
77
79
78
```sh
80
79
rladmin tune db < db:id | name > mtls_allow_outdated_certs enabled
81
80
```
82
-
83
-
{{< /note >}}
84
81
85
82
## Enable TLS for Active-Active cluster connections
86
83
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
-
{{<imagefilename="images/rs/screenshots/switch-to-legacy-ui.png"width="300px"alt="Select switch to legacy admin console from the dropdown.">}}
To enable TLS for Active-Active cluster connections:
108
87
109
-
### Configure TLS certificates for Active-Active
88
+
1. During [database creation]({{<relref "/operate/rs/databases/active-active/create">}}), expand the **TLS** configuration section.
110
89
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.
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.
123
91
124
-
### Configure TLS on all participating clusters
92
+
{{<imagefilename="images/rs/screenshots/databases/active-active-databases/enable-tls-for-active-active-db.png"alt="TLS is enabled on the Cluster Manager UI screen.">}}
125
93
126
-
Repeat this process on all participating clusters.
94
+
1. Click **Create**.
127
95
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.
0 commit comments