Grant the node's client read+update permissions

@jkeiser looking for your input on this.
I found an issue where the node's client is unable to update the node's attributes with the chef server upon client and node creation. The chef server gives full rights to my personal client, but not the node's client. My current workaround is to use the chef server's (AFAICT undocumented) ACL endpoint to grant read and update rights to the node's client.
This approach looks and feels hacky, but it does work for me right now (gotta make deadlines :stuck_out_tongue_closed_eyes: ). What would be the cleaner approach to do this? I'd rather do things the pretty upstream way than carrying this patch forward :wink: