[GitHub] [couchdb] tudordumitriu opened a new issue #1995: Is it possible to disable a user in a one db per-user schema?

[GitBox <gi...@apache.org>]

tudordumitriu opened a new issue #1995: Is it possible to disable a user in a one db per-user schema?
URL: https://github.com/apache/couchdb/issues/1995
 
 
   Hi 
   Is it possible to disable / enable back an user (restricting login) if we are using Cookie authentication for a per-user db configuration.
   
   ## Summary
   
   [NOTE]: # ( Provide a brief overview of what the new feature is all about. )
   
   ## Desired Behavior
   
   Ideally there could be a 'disabled' field in the user document in _users db, and that to be considered in authentication handler, hence the login would be rejected, ideally with an specific error code. Of course this could be controlled via other processes or as the admin.
   
   ## Possible Solution
   
   There are few options, but we wouldn't like to get to it unless it's strictly necessary:
   1. Writing a custom httpd_auth that will take the disabled field into account and configuring it instead of cookie default handler - but is in erlang and we would have to constantly keep it up to date
   2. Using Proxy Authentication - but that is not ideal as well, since we would have to manage the authentication separately, and the user base (accounts and passwords), and this also means that the ENTIRE traffic wold have to be routed through the reverse proxy, and we are afraid this would be a scalability issue, especially if we're to migrate to a cloud solution.
   
   ## Additional context
   We're using CouchDB with PouchDB, continuous replication 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services