[jira] [Commented] (COUCHDB-2362) Have dev/run put the same cookie secret and hashed admin password in all three nodes of dev cluster

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/COUCHDB-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184692#comment-14184692 ] 

ASF GitHub Bot commented on COUCHDB-2362:
-----------------------------------------

Github user candeira commented on the pull request:

    https://github.com/apache/couchdb/pull/269#issuecomment-60536183
  
    Cookie auth was not working for me on the cluster started by dev/run, so I tweaked the name of the issue and the script so all three secrets were identical.


> Have dev/run put the same cookie secret and hashed admin password in all three nodes of dev cluster
> ---------------------------------------------------------------------------------------------------
>
>                 Key: COUCHDB-2362
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2362
>             Project: CouchDB
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: BigCouch
>            Reporter: Javier Candeira
>
> When starting a dev cluster with the --admin option:
> `dev/run -a candeira:candeira`
> the local.ini scripts get rebuilt with an extra [admin] section and the plaintext user = password line. This means that couchdb adds the hashed password instead of replacing it.
> in addition, the admin party fix only sets the user = password line in one of the cluster's nodes, which may create problem.
> The forthcoming patch will initialise all three nodes with the same hashed password, as per rnewson:
> 00:27 <+rnewson> so you need to ensure that the admin is the same on all nodes after  hashing  
> 00:28 <+rnewson> otherwise cookies won't work if you hop between nodes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)