Skip to content

Commit b8c9dc5

Browse files
authored
Merge pull request SkylineCommunications#42 from jens-gellynck/TLSEnabled
Corrected help for TLSEnabled setting of Cassandra
2 parents fff65eb + 6be78da commit b8c9dc5

File tree

1 file changed

+3
-2
lines changed
  • user-guide/Reference/Skyline_DataMiner_Folder/More_information_on_certain_files_and_folders

1 file changed

+3
-2
lines changed

user-guide/Reference/Skyline_DataMiner_Folder/More_information_on_certain_files_and_folders/DB_xml.md

+3-2
Original file line numberDiff line numberDiff line change
@@ -169,13 +169,14 @@ To do so
169169
<UID>myUserId</UID>
170170
<PWD>myPassword</PWD>
171171
<DB>SLDMADB</DB>
172-
<TLSEnabled>true</TLSEnabled>
172+
<TLSEnabled>true</TLSEnabled>
173173
</DataBase>
174174
```
175175

176176
> [!NOTE]
177-
> - IF TLS is enabled, port 7001 must be opened in the firewall. See [Overview of IP ports used in a DMS](xref:Configuring_the_IP_network_ports#overview-of-ip-ports-used-in-a-dms).
178177
> - This procedure only enables TLS on the database connection. It does not enable client authentication.
178+
> - From DataMiner 10.1.3 onwards TLS 1.0 is supported. From DataMiner 10.2.4/10.2.0-CU1 onwards, TLS 1.0, 1.1 and 1.2 are supported.
179+
> - When Cassandra is hosted on the local DataMiner server, and DataMiner Failover is active, Cassandra will use TCP port 7001 for TLS encrypted inter-node communication (instead of port 7000). Make sure this port is allowed through the firewall of both Failover agents.
179180

180181
### Example of a general database configuration
181182

0 commit comments

Comments
 (0)