Details
-
Task
-
Resolution: Fixed
-
Critical
-
None
-
Security Level: Public
-
None
-
CBG Sprint 32
-
3
Description
Pulled out of CBG-502
We should also try to get some sort of test coverage that would've caught the X.509 runtime error, even if we can't easily get a full end-to-end (read: successful) X.509 integration test.
Perhaps an untrusted client cert would be sufficient enough to test that we can attempt to authenticate with the cluster, similar to what I provided in the GOCBC-592 issue.
Attachments
Issue Links
- relates to
-
CBG-502 x.509 broken due to deprecated CertificateAuthenticator
- Closed