{"action":"opened","issue":{"url":"https://api.github.com/repos/influxdata/influxdb/issues/5532","repository_url":"https://api.github.com/repos/influxdata/influxdb","labels_url":"https://api.github.com/repos/influxdata/influxdb/issues/5532/labels{/name}","comments_url":"https://api.github.com/repos/influxdata/influxdb/issues/5532/comments","events_url":"https://api.github.com/repos/influxdata/influxdb/issues/5532/events","html_url":"https://github.com/influxdata/influxdb/issues/5532","id":131073787,"number":5532,"title":"[0.10.0-rc2] user passwords not changeable in cluster","user":{"login":"dgnorton","id":209347,"avatar_url":"https://avatars.githubusercontent.com/u/209347?v=3","gravatar_id":"","url":"https://api.github.com/users/dgnorton","html_url":"https://github.com/dgnorton","followers_url":"https://api.github.com/users/dgnorton/followers","following_url":"https://api.github.com/users/dgnorton/following{/other_user}","gists_url":"https://api.github.com/users/dgnorton/gists{/gist_id}","starred_url":"https://api.github.com/users/dgnorton/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dgnorton/subscriptions","organizations_url":"https://api.github.com/users/dgnorton/orgs","repos_url":"https://api.github.com/users/dgnorton/repos","events_url":"https://api.github.com/users/dgnorton/events{/privacy}","received_events_url":"https://api.github.com/users/dgnorton/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/influxdata/influxdb/labels/category/clustering","name":"category/clustering","color":"d111e2"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-02-03T16:18:42Z","updated_at":"2016-02-03T16:18:42Z","closed_at":null,"body":"Issue #5505 was fixed for single node in RC2 by PR #5520 but it is still broken for clusters.  The fix for single node was to:\r\n- update user's password\r\n- on successful update, `meta.Client` deletes that user from `meta.Client.authCache`.\r\n\r\nThe problem in a cluster is that only the `meta.Client` on the node that executed the update knows to update its `authCache`.  The other nodes still have an out of date `authCache` containing the hash for the old password.\r\n\r\nA quick hack would be to deleted the entire `authCache` every time the loop in `meta.Client.retryUntilSnapshot` gets a new snapshot.  A better  way would be to individually update each user in the `authCache` from the user data in the new snapshot."}}