Qualifies the existing RedisTlsProvider client-certificate path without changing production code. A real Redis server requires client TLS authentication and a password. The test uses separately generated server/client identities, rejects missing and unrelated client keys, then verifies PONG and framework health UP with the trusted client.
Existing untrusted-server and hostname-mismatch tests remain intact. Test keys are generated in disposable directories and never come from external credentials.
Validation: focused TLS2testsPASS; full Java21 wrapper verify24tests, zero failures/errors/skips, packaging/coverage/dependency guardrailsPASS. Certificate rotation, broader trust-chain/revocation policies, admin actions and multi-node dashboard aggregation remain outside this test.
Related QRun-IO/qqq#1317; this is partial acceptance, not issue closure. Basefeature/redis was verified atfe823b3. No snapshot, merge or deployment.
Qualifies the existing RedisTlsProvider client-certificate path without changing production code. A real Redis server requires client TLS authentication and a password. The test uses separately generated server/client identities, rejects missing and unrelated client keys, then verifies PONG and framework health UP with the trusted client.
Existing untrusted-server and hostname-mismatch tests remain intact. Test keys are generated in disposable directories and never come from external credentials.
Validation: focused TLS2testsPASS; full Java21 wrapper verify24tests, zero failures/errors/skips, packaging/coverage/dependency guardrailsPASS. Certificate rotation, broader trust-chain/revocation policies, admin actions and multi-node dashboard aggregation remain outside this test.
Related QRun-IO/qqq#1317; this is partial acceptance, not issue closure. Basefeature/redis was verified atfe823b3. No snapshot, merge or deployment.
You are not authorized to merge this pull request.
This pull request can be merged automatically.
This pull request is marked as a work in progress.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Qualifies the existing RedisTlsProvider client-certificate path without changing production code. A real Redis server requires client TLS authentication and a password. The test uses separately generated server/client identities, rejects missing and unrelated client keys, then verifies PONG and framework health UP with the trusted client.
Existing untrusted-server and hostname-mismatch tests remain intact. Test keys are generated in disposable directories and never come from external credentials.
Validation: focused TLS2testsPASS; full Java21 wrapper verify24tests, zero failures/errors/skips, packaging/coverage/dependency guardrailsPASS. Certificate rotation, broader trust-chain/revocation policies, admin actions and multi-node dashboard aggregation remain outside this test.
Related QRun-IO/qqq#1317; this is partial acceptance, not issue closure. Basefeature/redis was verified atfe823b3. No snapshot, merge or deployment.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.