[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] What happens to x509* job attributes when Condor drops GCT?

Hello Max,
I performed a few tests in order to understand that, for what concerns submission to the HTCondor-CE (5.1.x on top of HTCondor 9.0.x)
An example working configuration for the condorce scitokens mapfile and jobrouter can be found here:

One use case that i would like to address is, for example, configuration for hierarchical fairshare. I came up with a potentially working
solution which depends however on one assumption about how the equivalent of the FQANÂ (i.e. something like to say, "/voname/groupname")
is reported in the jwt. That solution is also reported in the above wiki page.


Il 17/02/22 17:57, Fischer, Max (SCC) ha scritto:
Hi all,

in the struggle for switching to WLCG Tokens from GSI we realised that a lot of our infrastructure uses the x509* Job ClassAds such as X509UserProxyVOName. For now these are still there since pilots have a GSI proxy for other tasks anyway, so everything runs smoothly for now.
But itâs not really clear to us how much we can rely on that in the future.

Will HTCondor still be able to provide these job attributes when it drops GSI/GCT in the 10.0 series?


HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at: