Clarify token caching

trinodb · Nov 15, 2021 · 4b4fb69 · 4b4fb69
1 parent a0d3dc2
commit 4b4fb69
Showing 1 changed file with 3 additions and 1 deletion.
diff --git a/docs/src/main/sphinx/installation/jdbc.rst b/docs/src/main/sphinx/installation/jdbc.rst
@@ -190,7 +190,9 @@ Name                                                         Description
                                                              connections for the same authenticated user until the cache is
                                                              invalidated, such as when a client is restarted or when the classloader
                                                              reloads the JDBC driver. This is disabled by default, with a value of
-                                                             ``NONE``. To enable, set the value to ``MEMORY``.
+                                                             ``NONE``. To enable, set the value to ``MEMORY``. If the JDBC driver is used
+                                                             in a shared mode by different users, the first registered token is stored
+                                                             and authenticates all users.
 ``disableCompression``                                       Whether compression should be enabled.
 ``assumeLiteralNamesInMetadataCallsForNonConformingClients`` When enabled, the name patterns passed to ``DatabaseMetaData`` methods
                                                              are treated as literals. You can use this as a workaround for