Configuration Mapping
The following Jedis configuration parameters are:
-
Successfully Mapped: user, password, clientName, ssl, redisProtocol, connectionTimeoutMillis, socketTimeoutMillis, database.
-
Partially Mapped: sslSocketFactory, sslParameters, hostnameVerifier.
-
Not Mapped: blockingSocketTimeoutMillis.
Parameters Mappings
Section titled “Parameters Mappings”user→ServerCredentials.usernamepassword→ServerCredentials.passwordclientName→BaseClientConfiguration.clientNamessl→BaseClientConfiguration.useTLSredisProtocol→BaseClientConfiguration.protocolconnectionTimeoutMillis→AdvancedBaseClientConfiguration.connectionTimeoutsocketTimeoutMillis→BaseClientConfiguration.requestTimeoutdatabase→BaseClientConfiguration.databaseIdfor standalone clients. Cluster configurations reject a non-zero database because Valkey Cluster supports only database 0.
Partially Mapped Parameters
Section titled “Partially Mapped Parameters”sslSocketFactory→ Requires SSL/TLS migration to system certificate storesslParameters→ Limited mapping; custom protocols/ciphers not supportedhostnameVerifier→ Standard verification works; custom verifiers requireuseInsecureTLS
Unsupported Parameters
Section titled “Unsupported Parameters”blockingSocketTimeoutMillis→ No equivalent (GLIDE uses async I/O model)
Key Migration Insights
Section titled “Key Migration Insights”- GLIDE Architecture Shift: From application-managed SSL to system-managed SSL with secure defaults
- Certificate Management: Custom keystores/truststores require migration to system certificate store
- Protocol Selection: GLIDE auto-selects TLS 1.2+ and secure cipher suites
- Client Authentication: Client certificates require GLIDE’s advanced TLS configuration rather than Jedis socket factories