There is a bug in 2.0 _cluster_setup that doesn’t use the same salt on all nodes for the admin password. So if you used that to setup, yours “sessions” will be “per node”, but that’s not by design. You can copy the local.ini config line for the admin from one node to all other nodes to address this issue.
Best Jan -- > On 14. May 2017, at 18:50, Robert Samuel Newson <[email protected]> wrote: > > A session cookie acquired on one node is recognised by any other node if you > follow the instructions below (these are in the docs and _cluster_setup does > this too). > > You need to ensure each node has the same secret in couch_httpd_auth. It's > randomized at startup if not set, so set it to something (large, random) > before starting couchdb. > > For _admin_ users, you also need to ensure you set the same hashed version in > the .init file as the salt value is part of the cookie state (so that cookies > are invalidated when passwords change). > > Basically, anything in the .ini file needs synchronising between the nodes > externally. By hand, but more likely using chef / puppet, etc. > > Cloudant, for example, generates default.ini from a template which sets a > cluster-wide couch_httpd_auth secret and the [admins] section. > > B. > >> On 14 May 2017, at 02:43, Geoffrey Cox <[email protected]> wrote: >> >> Hi! >> >> Anyone have any ideas on this?http://stackoverflow.com/q/43958527/2831606 >> >> Thanks! >> >> Geoff > -- Professional Support for Apache CouchDB: https://neighbourhood.ie/couchdb-support/
