Table of Contents
The credentials of a user are defined in the XML file
/opt/rudder/etc/rudder-users.xml
. This file expects the following format:
<authentication hash="sha512"> <user name="alice" password="xxxxxxx" role="administrator"/> <user name="bob" password="xxxxxxx" role="administration_only, node_read"/> <user name="custom" password="xxxxxxx" role="node_read,node_write,configuration_read,rule_read,rule_edit,directive_read,technique_read"/> </authentication>
The name and password attributes are mandatory (non empty) for the user tags. The role attribute can be omitted but the user will have no permission, and only valid attributes are recognized.
Every modification of this file should be followed by a restart of the Rudder web application to be taken into account:
service rudder-jetty restart
The authentication tag should have a "hash" attribute, making "password" attributes on every user expect hashed passwords. Not specifying a hash attribute will fallback to plain text passwords, but it is strongly advised not to do so for security reasons.
The algorithm to be used to create the hash (and verify it during authentication) depend on the value of the hash attribute. The possible values, the corresponding algorithm and the Linux shell command need to obtain the hash of the "secret" password for this algorithm are listed here:
Table 2. Hashed passwords algorithms list
Value | Algorithm | Linux command to hash the password |
---|---|---|
"md5" | MD5 |
|
"sha" or "sha1" | SHA1 |
|
"sha256" or "sha-256" | SHA256 |
|
"sha512" or "sha-512" | SHA512 |
|
When using the suggested commands to hash a password, you must enter the command, then type your password, and hit return. The hash will then be displayed in your terminal. This avoids storing the password in your shell history.
Here is an example of authentication file with hashed password:
<authentication hash="sha256"> <!-- In this example, the hashed password is: "secret", hashed as a sha256 value --> <user name="carol" password="2bb80d537b1da3e38bd30361aa855686bde0eacd7162fef6a25fe97bf527a25b" role="administrator"/> </authentication>