CONDOR_TOKEN_REQUEST_APPROVE(1)

✨ NAME ✨

condor_token_request_approve β€” approve a token request at a remote daemon πŸ’…

(this lives in the HTCondor Manual, bestie, and it's giving "admin doing grown-up security things" energy 🫢)


🌸 SYNOPSIS 🌸

condor_token_request_approve [-reqid val] [-pool pool_name] [-name
hostname] [-type type] [-debug]

condor_token_request_approve [-help ]

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so, condor_token_request_approve is the little tool that approves a request for an authentication token that's already queued up at a remote daemon. Once it's approved?? The requester can go fetch a fully signed token from the daemon and use it to authenticate with the IDTOKENS method. Slay, honestly. ✨

⚠️ Bestie, read this part twice, I'm so serious. NOTE that any user can request a very powerful token β€” like, powerful enough to let them be the HTCondor administrator 😭. Requests like that can only be approved by an administrator. So review token requests carefully, okay?? Make sure you actually understand what identity you're approving. The only safe way to approve a request is to have the request ID communicated out-of-band and verify it matches the expected request contents β€” that's how you ensure the request's authenticity. No vibes-based approving. Periodt. πŸ‘‘

By default, users can only approve requests for their own identity β€” like, a user authenticating as bucky@cs.wisc.edu can only approve token requests for the identity bucky@cs.wisc.edu. Meanwhile users with ADMINISTRATOR authorization can approve any request. Main character privileges πŸ”₯.

If you want to approve multiple requests at once, do not provide the -reqid flag β€” in that case, the utility will iterate through all known requests. One by one, bestie. πŸŽ€

By default, condor_token_request_approve will query the local condor_collector. But if you specify a combination of -pool, -name, or -type, the tool can request tokens in other pools, on other hosts, or from different daemon types. Versatile icon πŸ’…


πŸ’– OPTIONS πŸ’–

  • -debug β€” Causes debugging information to be sent to stderr, based on the value of the configuration variable TOOL_DEBUG. πŸ‘€
  • -help β€” Display brief usage information and exit. The classic "help me I'm lost" button 🫢
  • -name hostname β€” Request a token from the daemon named hostname in the pool. If not specified, the locally-running daemons will be used.
  • -pool pool_name β€” Request a token from a daemon in a non-default pool pool_name. Branching out, we love to see it 🌈
  • -reqid val β€” Provides the specific request ID to approve. Request IDs should be communicated out of band to the administrator through a trusted channel. (Trusted channel. Not the group chat. I know. πŸ’€)
  • -type type β€” Request a token from a specific daemon type type. If not given, a condor_collector is used.

🌟 EXAMPLES 🌟

To approve the tokens at the default condor_collector, one-by-one:

$ condor_token_request_approve
RequestedIdentity = "bucky@cs.wisc.edu"
AuthenticatedIdentity = "anonymous@ssl"
PeerLocation = "192.0.2.42"
ClientId = "bird.cs.wisc.edu-516"
RequestId = "8414912"

To approve, please type 'yes'
yes
Request 8414912 approved successfully.

When a token is approved, the corresponding condor_token_request process will complete. πŸŽ‰ Note the printed request includes both the requested identity (which will be written into the issued token) and the authenticated identity of the token requester. In this case, anonymous@ssl indicates the connection was established successfully over SSL but the remote side is anonymous β€” meaning it did not contain a client SSL certificate. iykyk 🧚


πŸŽ€ EXIT STATUS πŸŽ€

condor_token_request_approve will exit with a non-zero status value if it fails to communicate with the remote daemon. Otherwise, it will exit 0. So like, 0 = we ate, non-zero = we did not eat 😭


πŸ”₯ SEE ALSO πŸ”₯

Go read your friends, they're iconic too πŸ’œ


πŸ‘‘ AUTHOR πŸ‘‘

Center for High Throughput Computing, University of Wisconsin-Madison

πŸ‘‘ AUTHOR πŸ‘‘

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!! πŸ’– this was HTCondor Manual, version vibes of Oct 16, 2026 β€” go approve responsibly, protect your out-of-band request IDs, and don't hand out ADMINISTRATOR tokens to just anyone, I'm begging πŸ«Άβœ¨πŸ’…

πŸ“¦ where this page comes from