New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support authenticating against CBS using x.509 certificate #3329

Closed
adamcfraser opened this Issue Feb 21, 2018 · 5 comments

Comments

Projects
None yet
3 participants
@adamcfraser
Copy link
Contributor

adamcfraser commented Feb 21, 2018

Support specifying the location of a client cert in the Sync Gateway config, and then use that cert for X.509 Certificate Authentication when connecting to the bucket via the SDK.

@adamcfraser adamcfraser added this to the 2.1.0 milestone Feb 21, 2018

@djpongh djpongh added the backlog label Feb 26, 2018

@adamcfraser adamcfraser changed the title Support authenticating against CBS using client certificate Support authenticating against CBS using x.509 certificate Apr 2, 2018

@adamcfraser adamcfraser assigned adamcfraser and unassigned bbrks Apr 16, 2018

@adamcfraser adamcfraser added ready and removed backlog labels Apr 16, 2018

@adamcfraser

This comment has been minimized.

Copy link
Contributor

adamcfraser commented Apr 21, 2018

In progress, but will be blocked until https://issues.couchbase.com/browse/GOCBC-287 is fixed.

@adamcfraser

This comment has been minimized.

Copy link
Contributor

adamcfraser commented Apr 27, 2018

gocb is now working, DCP is currently blocked:
https://issues.couchbase.com/browse/MB-29435

Also need to review all cases where we're attempting to use basic auth for direct HTTP requests (MaxTTL, expiry, etc), and work out the correct way to invoke these requests when authenticating via X.509 cert.

@adamcfraser

This comment has been minimized.

Copy link
Contributor

adamcfraser commented Apr 27, 2018

Some good news - because we're reusing the gocb client when making direct HTTP requests, those are succeeding. Will remove the current handling that's setting [bucketname, ""] as basic auth credential, but it's working as-is (they are being ignored).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment