Authentication Mechanism

From wiki.hpc.mk
Revision as of 09:18, 31 August 2021 by Boris (talk | contribs) (Created page with "'''<h1 id="Autentication_Setting">Setting up a user authentication mechanism</h1>''' For greater security in the communication of the master server with the clients, it is ne...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Setting up a user authentication mechanism

For greater security in the communication of the master server with the clients, it is necessary to set up two-way authentication with the help of a shared key. According to standard practice, Slurm uses the munge protocol to validate the mutual communication of system components. In short, it is designed for large HPC environments, in which the UID and GID identifiers of users and groups are validated with a shared cryptographic key. It typically uses a 128 AES encryption scheme as well as a SHA-256 hash validation message. The generated key is then copied to all nodes to be used in the cluster along with the corresponding permissions. It should also be noted that users who will use Slurm should have the same UID and GUID everywhere, for better security and further authentication when sending tasks.