Updating the summary tables

Author: gerardma77

content/vault/v1.19.x/content/docs/updates/important-changes.mdx

@@ -418,3 +418,15 @@ to the billing start date for the cluster.
 To avoid issues and unexpected behavior with Vault Community, always provide a
 valid `start_time` value when calling `/sys/internal/counters/activity` or
 upgrade to v1.20.x.
+
+### Failing credential refresh for Snowflake DB secrets engine key pair authentication ((#snowflake-keypair-refresh))
+
+| Change      | Affected version                       | Fixed version
+| ----------- | -------------------------------------- | --------------------
+| Known issue | 1.20.x, 1.19.x, 1.18.x+ent, 1.17.x+ent, 1.16.x+ent | None
+
+Users using keypair or username and password authentication with Snowflake databases may receive errors
+due to improper credential refreshes and stale connections in the connection pool.
+When two or more concurrent operations occur, Vault tries to reuse an idle
+connection from the pool and the request fails due to session timeout in the
+Snowflake database.

content/vault/v1.20.x/content/docs/updates/important-changes.mdx

@@ -284,7 +284,7 @@ You can also use the API explorer to make any HTTP request:
 | ----------- | -------------------------------------- | --------------------
 | Known issue | 1.20.x, 1.19.x, 1.18.x+ent, 1.17.x+ent, 1.16.x+ent | None
 
-Users using keypair authentication with Snowflake databases may receive errors
+Users using keypair or username and password authentication with Snowflake databases may receive errors
 due to improper credential refreshes and stale connections in the connection pool.
 When two or more concurrent operations occur, Vault tries to reuse an idle
 connection from the pool and the request fails due to session timeout in the