RNCTX opened a new issue #2872:
URL: https://github.com/apache/couchdb/issues/2872


   ## Expected Behavior
   Per 
[docs](https://docs.couchdb.org/en/stable/config/auth.html#server-administrators),
 adding an admin user to the `[admins]` section of the ini should create a new 
admin on server reload.
   
   ## Current Behavior
   Admins created via local.ini `[admins]` cannot log in to the web ui.  The 
exact same user/password created via the web ui can log in to the web ui.
   
   ## Possible Solution
   Not sure...
   
   ```
   [notice] 2020-05-06T01:07:43.192755Z couchdb@127.0.0.1 <0.255.0> -------- 
rexi_server : cluster stable
   [notice] 2020-05-06T01:07:43.192902Z couchdb@127.0.0.1 <0.259.0> -------- 
rexi_buffer : cluster stable
   [warning] 2020-05-06T01:08:42.009138Z couchdb@127.0.0.1 <0.1030.0> 
39b7eceb33 couch_httpd_auth: Authentication failed for user Administrator from 
192.168.1.1
   ```
   
   ## Steps to Reproduce (for bugs)
   
   1. Add apache couchdb repo to sources.list
   2. fresh install of couchdb
   3. edit /opt/couchdb/etc/local.ini, add another admin to bottom of the file
   4. sudo service couchdb stop && sudo service couchdb start
   5. the user will be created in local.d/10-admins.ini, but cannot log in to 
the web ui
   6. log in with admin created by dpkg configuration, delete the new ini admin 
you added
   7. re-add the same user/pass combo in the web ui that could not log in from 
the ini, now it can log in.
   
   I'm creating the user "Administrator" (with the capital A) and an `openssl 
rand -base64 32` randomly generated 32 char password to reproduce this.
   
   ## Your Environment
   
   * Version used: 3.1.0
   * Browser Name and version: Chrome v81
   * Operating System and version (desktop or mobile): Ubuntu 18.04
   * Link to your project: N/A
   


----------------------------------------------------------------
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:
us...@infra.apache.org


Reply via email to