An authentication token consists of a username in Base64-encoded format and a password that’s hashed using the MD5 hash algorithm, separated by a colon, like this:
base64-encoded-username:md5-hashed-password
For example, here’s the token for the Base64-encoded username myuser and the MD5-hashed password p2Ss#0rd:
bXl1c2Vy:6ecaf581f6879c9a14ca6b76ff2a6b15
The GNU Core Utilities include the base64 and md5sum commands necessary to encode your account information. These commands convert text to Base64-encoded and MD5-hashed values, respectively. For more information on the GNU Core Utilities, see http://www.gnu.org/software/coreutils/.
Other tools that generate Base64-encoded and MD5-hashed values are available for download on the web. For security reasons, do not use interactive public web-based tools to generate these values.
The GNU Core Utilities include the base64 and md5sum commands, which convert text to Base64-encoded and MD5-hashed values, respectively. With these commands, a line such as this creates the required token:
echo `echo -n username | base64`:`echo -n password | md5sum` |
awk '{print $1}'
The character before echo, before and after the colon, and following md5sum is a backtick (or grave accent). The -n option in the echo command prevents the command from appending a newline character to the output. This is required to ensure correct Base64 and MD5 values.
© 2016 Hitachi Data Systems Corporation. All rights reserved.