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
Copy file name to clipboardExpand all lines: content/operate/rs/7.4/security/encryption/tls/enable-tls.md
+28-45Lines changed: 28 additions & 45 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,65 +85,48 @@ rladmin tune db < db:id | name > mtls_allow_outdated_certs enabled
85
85
86
86
## Enable TLS for Active-Active cluster connections
87
87
88
-
You can enable TLS for Active-Active cluster connections when you create a database using the Cluster Manager UI, [`crdb-cli`]({{<relref "/operate/rs/7.4/references/cli-utilities/crdb-cli">}}), or the [REST API]({{<relref "/operate/rs/7.4/references/rest-api">}}).
88
+
To enable TLS for Active-Active cluster connections:
89
89
90
-
If you need to enable or turn off TLS after the Active-Active database is created, you must use [`crdb-cli`]({{<relref "/operate/rs/7.4/references/cli-utilities/crdb-cli">}}) or the [REST API]({{<relref "/operate/rs/7.4/references/rest-api">}}).
90
+
1.If you are using the new Cluster Manager UI, switch to the legacy admin console.
91
91
92
-
### Enable TLS during database creation
92
+
{{<imagefilename="images/rs/screenshots/switch-to-legacy-ui.png"width="300px"alt="Select switch to legacy admin console from the dropdown.">}}
93
93
94
-
To enable TLS for Active-Active cluster connections using the Cluster Manager UI:
1.During [database creation]({{<relref "/operate/rs/7.4/databases/active-active/create">}}), expand the **TLS** configuration section.
96
+
1.[Configure TLS certificates for Active-Active.](#configure-tls-certificates-for-active-active)
97
97
98
-
1.Select **On** to enable TLS.
98
+
1.[Configure TLS on all participating clusters.](#configure-tls-on-all-participating-clusters)
99
99
100
-
{{<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.">}}
100
+
{{< note >}}
101
+
You cannot enable or turn off TLS after the Active-Active database is created, but you can change the TLS configuration.
102
+
{{< /note >}}
101
103
102
-
1. Click **Create**.
104
+
### Retrieve syncer certificates
103
105
104
-
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.
106
+
For each participating cluster, copy the syncer certificate from the **general** settings tab.
You can enable TLS for an existing Active-Active database using either `crdb-cli` or the REST API.
110
+
### Configure TLS certificates for Active-Active
109
111
110
-
{{< multitabs id="enable-tls-post-creation"
111
-
tab1="CLI"
112
-
tab2="REST API" >}}
112
+
1. During database creation (see [Create an Active-Active Geo-Replicated Database]({{< relref "/operate/rs/7.4/databases/active-active/create.md" >}}), select **Edit** from the **configuration** tab.
113
+
1. Enable **TLS**.
114
+
-**Enforce client authentication** is selected by default. If you clear this option, you will still enforce encryption, but TLS client authentication will be deactivated.
115
+
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" >}}
121
+
1. Repeat this process, adding the syncer certificate for each participating cluster.
122
+
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.
123
+
1. Select **Update** at the bottom of the screen to save your configuration.
113
124
114
-
Run the following [`crdb-cli crdb update`]({{<relref "/operate/rs/7.4/references/cli-utilities/crdb-cli/crdb/update">}}) command:
Replace `<guid>` with your Active-Active database's globally unique identifier.
121
-
122
-
-tab-sep-
123
-
124
-
You can use an [update database configuration]({{<relref "/operate/rs/7.4/references/rest-api/requests/bdbs#put-bdbs">}}) request to enable TLS.
125
-
126
-
To enable TLS for Active-Active database communications only:
127
-
128
-
```sh
129
-
PUT https://<host>:9443/v1/bdbs/<database-id>
130
-
{
131
-
"enforce_client_authentication": "disabled",
132
-
"tls_mode": "replica_ssl"
133
-
}
134
-
```
135
-
136
-
To enable TLS for all communications:
137
-
138
-
```sh
139
-
PUT https://<host>:9443/v1/bdbs/<database-id>
140
-
{
141
-
"enforce_client_authentication": "disabled",
142
-
"tls_mode": "enabled"
143
-
}
144
-
```
127
+
Repeat this process on all participating clusters.
145
128
146
-
{{< /multitabs >}}
129
+
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.
0 commit comments