Skip to content
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

Unable to replicate using Facebook authenticator #489

Closed
pham0167 opened this issue Aug 13, 2015 · 5 comments
Closed

Unable to replicate using Facebook authenticator #489

pham0167 opened this issue Aug 13, 2015 · 5 comments
Labels
Milestone

Comments

@pham0167
Copy link

When I try to replicate using the Facebook authenticator, the user and session gets created correctly in Sync Gateway, but I am unable to login. Subsequent attempts to replicate after the user and session have been created also fails with a 401 Login Required.

Note that replicating with basic authenticator works correctly.

Client is Xamarin iOS app running Couchbase Lite version 1.1.0.1
Couchbase Server Community Edition 3.0.1 running on a Windows machine with firewalls turned off.
Sync Gateway version 1.1.0

Here's the sync console output:
HTTP: #2: GET /sync_gateway/_session
HTTP: #3: POST /sync_gateway/_facebook
go-couchbase: call to ViewCustom("sync_gateway", "access") in github.com/couchbase/sync_gateway/db.(*DatabaseContext).ComputeChann
elsForPrincipal took 473ms
HTTP: #4: GET /sync_gateway/_local/82b5437a4586262d94a5866682aec15ad0f63d23
HTTP: #4: --> 401 Login required (1.0 ms)

@borrrden
Copy link
Member

Alright, sorry this took so long to respond to! I got sucked into another issue for an extraordinarily long time. I will set up a test to try to reproduce this, though I doubt it will take much. I'll let you know more soon.

borrrden added a commit that referenced this issue Aug 24, 2015
@borrrden
Copy link
Member

borrrden commented Sep 2, 2015

Update: Looks like the cookie saving mechanism needs some attention. I should have a fix out tomorrow.

borrrden added a commit that referenced this issue Sep 3, 2015
@borrrden
Copy link
Member

borrrden commented Sep 3, 2015

@pham0167 Check out the issue/498 branch. I replicated the issue and corrected it so let me know if this solves your problem.

@pham0167
Copy link
Author

pham0167 commented Sep 3, 2015

@borrrden Will this fix be available in a release on NuGet soon? I'm currently consuming this in a Xamarin mobile project as a nuget package.

@borrrden
Copy link
Member

borrrden commented Sep 3, 2015

@pham0167 It is not likely that we will make another Nuget release for a while (we usually try to make releases on multiple platforms at once). It's possible that we may start using another distribution system to release nightly, or at least periodical builds but that is still under discussion. Does this mean that the branch in question has solved your problem?

borrrden added a commit that referenced this issue Sep 10, 2015
borrrden added a commit that referenced this issue Sep 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants