Issue 216 in couchdb-python: Cookie Authentication

[couchdb...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 216 by bigblue...@gmail.com: Cookie Authentication
http://code.google.com/p/couchdb-python/issues/detail?id=216

CouchDB supports HTTP Basic, Cookie, and OAuth authentication options. It
would be great if couchdb-python made Cookie authentication available. It
would take some extension to http.py, but should be a fairly minimal change.

Thanks!

[couchdb...@googlecode.com]

Comment #1 on issue 216 by kxepal: Cookie Authentication
http://code.google.com/p/couchdb-python/issues/detail?id=216

Since there is OAuth support patch (issue 158), probably we need to extend
Session object to support custom auth providers: Basic(default), Cookie and
OAuth(if oauth lib available).

[couchdb...@googlecode.com]

Comment #2 on issue 216 by matt.goo...@gmail.com: Cookie Authentication
http://code.google.com/p/couchdb-python/issues/detail?id=216

What's the use case for supporting cookie auth in a library like
couchdb-python? My understanding is that it's only there to support pretty
login forms, something a library (presumably) has no need for.

[couchdb...@googlecode.com]

Comment #3 on issue 216 by kxepal: Cookie Authentication
http://code.google.com/p/couchdb-python/issues/detail?id=216

Case is when user had been already auth'ed at CouchDB, you has cookie
about, but no credentials. The basic example is CouchDB external process,
which might been called by such user and which required to callback CouchDB
for some additional data: it'll has userctx, cookies, but no user
credentials to request CouchDB behind of scene unless you made by another
user name which may create potentially issues.

[couchdb...@googlecode.com]

Comment #4 on issue 216 by djc.ochtman: Cookie Authentication
http://code.google.com/p/couchdb-python/issues/detail?id=216

This issue has been migrated to GitHub. Please continue discussion here:

https://github.com/djc/couchdb-python/issues/216

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings