Ticket 16897

Summary: scontrol token lifespan max fails softly
Product: Slurm Reporter: sysadmin
Component: slurmrestdAssignee: Nate Rini <nate>
Status: RESOLVED DUPLICATE QA Contact:
Severity: 4 - Minor Issue    
Priority: --- CC: marshall, nate
Version: 21.08.8   
Hardware: Linux   
OS: Linux   
See Also: https://bugs.schedmd.com/show_bug.cgi?id=13695
Site: Allen Institute Alineos Sites: ---
Atos/Eviden Sites: --- Confidential Site: ---
Coreweave sites: --- Cray Sites: ---
DS9 clusters: --- HPCnow Sites: ---
HPE Sites: --- IBM Sites: ---
NOAA SIte: --- OCF Sites: ---
Recursion Pharma Sites: --- SFW Sites: ---
SNIC sites: --- Linux Distro: ---
Machine Name: CLE Version:
Version Fixed: Target Release: ---
DevPrio: --- Emory-Cloud Sites: ---

Description sysadmin 2023-06-06 11:05:56 MDT 
Happy Tuesday,
Heard reports that someone was getting invalid JWT tokens with a long lifespan (slurm passes a token... but it is not honored on further commands).

I believe that max_token_lifespan could help avoid this error state but wondering if there should be more of a visible note to the user that the lifespan is too long. Unfortunately max_token_lifespan is not available in our slurm version...

Testing scenario:
export $(scontrol token lifespan=999999999999999999)
Result: Token generated, error: "slurm_load_partitions: Zero Bytes were transmitted or received" on sinfo

export $(scontrol token lifespan=99999999999999999)
Result: Token generated, valid response from sinfo

I claim that slurm should not be handing out invalid tokens if they are invalid- any chance an error message can prompt users to be less optimistic about the duration of the earth's lifespan? (yes- I acknowledge that this lifespan is ridiculous... but users like hitting the '9' key... a lot...)

I do want to hear back on how things are going at the expiration of the max token... Has Pangaea re-formed?

Many thanks,
-Nathaniel
Comment 3 Nate Rini 2023-06-06 11:46:39 MDT 
The ability to set max token lifespan was added by bug#13107 in Slurm-22.05.0:
> https://github.com/SchedMD/slurm/commit/85516610c0e74887b77a03a97146363921856995

Please upgrade to either of the currently supported releases to use this functionality:
> Slurm-22.05
> Slurm-23.02

Closing out this ticket as duplicate. Please respond if there are any more related questions or issues.

*** This ticket has been marked as a duplicate of ticket 13107 ***