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: docs/api/getting-started.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,8 +38,8 @@ To connect your application to KurrentDB, you need to configure and create a cli
38
38
::: tip Insecure clusters
39
39
The recommended way to connect to KurrentDB is using secure mode (which is
40
40
the default). However, if your KurrentDB instance is running in insecure
41
-
mode, you must explicitly set `tls=false` in your [connection
42
-
string](#connection-string) or client configuration.
41
+
mode, you must explicitly set `tls=false` in your connection
42
+
string or client configuration.
43
43
:::
44
44
45
45
KurrentDB uses connection strings to configure the client connection. The connection string supports two protocols:
@@ -93,7 +93,6 @@ There are a number of query parameters that can be used in the connection string
93
93
|`keepAliveTimeout`| Number |`10`| Keep-alive ping call timeout, in seconds. |
94
94
|`userCertFile`| String, file path | None | User certificate file for X.509 authentication. |
95
95
|`userKeyFile`| String, file path | None | Key file for the user certificate used for X.509 authentication. |
96
-
|`dnsDiscover`|`true`, `false`|`false`| Enable DNS-based cluster discovery. When `true`, resolves hostnames to discover cluster nodes. Use with `feature=dns-lookup` for full DNS resolution. |
97
96
|`feature`|`dns-lookup`| None | Enable specific client features. Use `dns-lookup` with `dnsDiscover=true` to resolve hostnames to multiple IP addresses for cluster discovery. |
98
97
99
98
When connecting to an insecure instance, specify `tls=false` parameter. For example, for a node running locally use `kurrentdb://localhost:2113?tls=false`. Note that usernames and passwords aren't provided there because insecure deployments don't support authentication and authorisation.
@@ -218,4 +217,4 @@ latch.await();
218
217
When you read events from the stream, you get a collection of `ResolvedEvent`
219
218
structures (synchronous) or `ReadMessage` objects (reactive). The event payload
220
219
is returned as a byte array and needs to be deserialized. See more advanced
221
-
scenarios in [reading events documentation](./reading-events.md).
220
+
scenarios in [reading events documentation](./reading-events.md).
0 commit comments