RNCTX edited a comment on issue #2872:
URL: https://github.com/apache/couchdb/issues/2872#issuecomment-626232129


   Yes, I just deleted my log of my own sanity check, lol. This is the weirdest 
chrome bug with passwords I've managed to create in many years.  
   
   The installation parameters I am passing to the remote server are quite 
simple:
   
   ```
       - name: Install couchdb...
         apt:
           name: couchdb
           update_cache: true
   
       - name: Set couchdb ini file options...
         vars:
           default_password: "{{ lookup('password', 
'~/pwds/password-for_admin.txt length=32 chars=ascii_letters,digits') }}"
         ini_file:
           ini_file:
           dest: /opt/couchdb/etc/local.ini
           section: "{{ item.section }}"
           option: "{{ item.option }}"
           value: "{{ item.value }}"
           create: false
           backup: "{{ true if index == 0 else false }}"
         loop:
           - { section: 'chttpd', option: 'port', value: '5984' }
           - { section: 'chttpd', option: 'bind_address', value: '127.0.0.1' }
           - { section: 'chttpd', option: 'require_valid_user', value: 'true' }
           - { section: 'admins', option: 'admin', value: '{{ default_password 
}}' }
         loop_control:
           index_var: index
   
   ```
   Identical to the debconf prompts (because ansible doesn't do debconf 
properly, it seems, it can set non-password options but doesn't reconfigure 
after setting them, so it's fairly worthless).
   
   I switched to Firefox as I was typing up another head scratcher and every 
problem went away? Then I went and opened the server in chrome on my desktop 
instead of my laptop and it works fine as well.
   
   /shrug
   
   So for real this time, couchdb works fine, chrome's password saving on (one 
of my) OS X does not!


----------------------------------------------------------------
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