I went down this route a while but I will recommend against it if you are going to have any other methods of accessing the data in couch base.
Instead I have written an api that pulls the user record with stored encrypted password from couchbase, verifies identity and then using the admin port of the sync gateway creates a session and returns that to the app. The app then uses that session to sync. I found that trusting the user record in sync gateway to be the authority on user identification was onerous for users to access data from other places (web, etc) -j Sent from my iPhone > On Nov 1, 2014, at 8:08 AM, Steve <[email protected]> wrote: > > Doh! I see the code from Pro Couchbase Server is remarkably similar to the > code here. > > Also, I see from the Couchbase Mobile documentation that the remote Couchbase > server can employ https and this seems to be mandatory if wanting to use > Basic Authentication in a secure manner. > -- > You received this message because you are subscribed to the Google Groups > "Couchbase Mobile" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/mobile-couchbase/ce904de9-3636-41ec-853b-c9fc331220c8%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/78A86239-FBCA-4476-9E7A-A39024288F27%40gmail.com. For more options, visit https://groups.google.com/d/optout.
