|
Lines 48-53
scontrol token
Link Here
|
| 48 |
command.</li> |
48 |
command.</li> |
| 49 |
</ol> |
49 |
</ol> |
| 50 |
|
50 |
|
| 51 |
<p style="text-align:center;">Last modified 30 September 2020</p> |
51 |
<h2>Compatibility</h2> |
|
|
52 |
Slurm uses libjwt to view and verify RFC7519 JWT tokens. Compliant tokens |
| 53 |
generated by another solution can be used as long as the following requirments |
| 54 |
are met: |
| 55 |
<ol> |
| 56 |
<li>Required tokens for Slurm are present: |
| 57 |
<ol> |
| 58 |
<li>iat: Unix timestamp of creation date.</li> |
| 59 |
<li>exp: Unix timestamp of expiration date.</li> |
| 60 |
<li>sun: Slurm UserName |
| 61 |
<a href="https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_437"> |
| 62 |
(POSIX.1-2017 User Name) |
| 63 |
</a>. |
| 64 |
</li> |
| 65 |
</ol> |
| 66 |
</li> |
| 67 |
<li>Tokens are signed with HS256 algorithm compliant to RFC7518. No other |
| 68 |
algorithms are currently supported by Slurm.</li> |
| 69 |
<li>Signing key is provided to slurmctld and slurmdbd to allow decryption of |
| 70 |
the tokens. Slurm currently only supports a single signing key.</li> |
| 71 |
</ol> |
| 72 |
|
| 73 |
<p style="text-align:center;">Last modified 01 December 2020</p> |
| 52 |
|
74 |
|
| 53 |
<!--#include virtual="footer.txt"--> |
75 |
<!--#include virtual="footer.txt"--> |
| 54 |
- |
|
|
