Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
1
Description
When gocb is initialized with cacertpath, certpath and keypath its "obvious" that client certificate authentication is going to be used.
If no authenticator is set (or specifically: gocb.CertificateAuthenticator is not used) then the SDK tries to bootstrap but fails in a non-obvious way (from verbose log):
GOCB 10:16:26.586310 agentrouting.go:138: Authenticating...
|
GOCB 10:16:26.586329 memdclient.go:112: Writing request. 10.142.175.1:58818 OP=0x21. Opaque=3
|
GOCB 10:16:26.586572 memdclient.go:247: Resolving response OP=0x21. Opaque=3
|
GOCB 10:16:26.586588 memdclient.go:177: Dispatching response callback. OP=0x21. Opaque=3
|
GOCB 10:16:26.586607 agentrouting.go:141: Failed to authenticate. server does not support this command
|
The situation might be improved if gocb checks the state on open bucket if the combination can actually work.