DataGrip and Database Server: Credential Expiration and Session Persistence
0 reputation · 11 Feb 2021, 22:41 UTC
DataGrip manages database connectivity through JDBC drivers, utilizing internal password-safe mechanisms or system keychains to store authentication data. While the IDE maintains persistent connections to improve performance, the lifecycle of these sessions is governed by the target database server's timeout and credential expiration policies.
A challenge arises when credentials expire on the server side while a DataGrip session remains active. Because the IDE relies on the driver's handling of the authentication handshake, there is uncertainty regarding how the client behaves when a persistent connection is severed due to credential rotation or expiration without a manual trigger of the 'Test Connection' feature.
- Does DataGrip automatically trigger a credential refresh prompt when the JDBC driver reports an authentication failure on an existing session?
- What is the expected behavior for session recovery when utilizing system keychain integration versus the internal master password storage?
datagrip