CONDOR_TOKEN_LIST(1)

✨ condor_token_list β€” the HTCondor Manual glow-up ✨

okay bestie, come sit with me, we're doing a lil tour of condor_token_list(1) from the HTCondor Manual πŸ’– this is the little tool that lists every token you've got, specifically the ones for IDTOKENS auth. yes queen, the whole list. no crumbs left.


🌸 SYNOPSIS 🌸

condor_token_list [-dir directory]

condor_token_list -help

that's it. that's the whole vibe. two shapes, pick your fighter 🫢


πŸ’… DESCRIPTION πŸ’…

so condor_token_list parses the tokens that are available to the current user and prints them to stdout. it's giving "show me what I'm working with" energy ✨

the tokens live in files inside the directory referenced by SEC_TOKEN_DIRECTORY. important detail bestie: multiple tokens can be saved inside each file β€” one per line. so don't go assuming one file = one token, that's not the vibe here πŸ’€

the output format is a list of the deserialized contents of each token, plus the file name the token was found in, one per line. and ngl, this is the part you need to hear loud and clear:

Do NOT treat this output as machine readable. fr fr, it literally says it should not be considered machine readable, and the format is subject to change in future releases of HTCondor. humans only, no parsing scripts πŸ™ˆ

πŸŽ€ OPTIONS πŸŽ€

  • -help β€” shows you a lil brief usage info and then dips (exit). short and sweet, queen πŸ‘‘
  • -dir β€” read the tokens from an alternate directory instead. yes you can point it somewhere else, slay πŸ¦‹

⭐ EXAMPLES ⭐

here's what it looks like when you list all tokens as the current user:

$ condor_token_list
Header: {"alg":"HS256","kid":"POOL"} Payload: {"exp":1565576872,"iat":1565543872,"iss":"htcondor.cs.wisc.edu","scope":"condor:\/DAEMON","sub":"k8sworker@wisc.edu"} File: /home/bucky/.condor/tokens.d/token1
Header: {"alg":"HS256","kid":"POOL"} Payload: {"iat":1572414350,"iss":"htcondor.cs.wisc.edu","scope":"condor:\/WRITE","sub":"bucky@wisc.edu"} File: /home/bucky/.condor/tokens.d/token2

two tokens, two files, whole lotta JSON. header, payload, file. iconic πŸ”₯


πŸ’€ EXIT STATUS πŸ’€

condor_token_list exits with a non-zero status value if:

  • it fails to read the token directory 🫠
  • the tokens are improperly formatted 😭
  • it runs into some other error, whatever that may be πŸ’€

otherwise? it exits 0. we love a clean exit. periodt ✨


🌈 SEE ALSO 🌈

your girl doesn't work alone, she's got a whole squad:

go read them, iykyk 🫢


πŸ‘‘ AUTHOR πŸ‘‘

Center for High Throughput Computing, University of Wisconsin-Madison

πŸ‘‘ AUTHOR (yes, again) πŸ‘‘

HTCondor Team


1990-2026, Center for High Throughput Computing, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI, US. Licensed under the Apache License, Version 2.0.


and that's the whole page bestie, no notes πŸ’… this was the HTCondor Manual version dated Oct 16, 2026, and condor_token_list(1) is out here being the main character. go forth and list your tokens responsibly, you ate πŸŒΈπŸ¦‹β­

πŸ“¦ where this page comes from