Hi Maarten,maybe I am overthinking it, but AFAIS the problem is the remote submit needing to forward the proxy
The user servers are as remote submitters not running a local schedd but only forward the jobs to the actual schedulers. I am not sure, if the X509s are forwarded, or?
Cheers, Thomas On 11/02/2021 18.09, Maarten Litmaath wrote:
Hi Thomas, could it be as simple as using a JDL like this: cmd = ... output = ... error = ... log = ... +TransferOutput = "" periodic_hold = ... periodic_remove = ... universe = grid grid_resource = condor htc-ce.some.domain htc-ce.some.domain:9619 use_x509userproxy = true environment = ... queue 1 That is how ALICE let a local HTCondor service deal with all the intricacies of handling jobs for remote HTCondor CEs. Maybe I am missing something? ________________________________________ From: HTCondor-users [htcondor-users-bounces@xxxxxxxxxxx] on behalf of Thomas Hartmann [thomas.hartmann@xxxxxxx] Sent: 11 February 2021 17:46 To: HTCondor-Users Mail List Subject: [HTCondor-users] Remote Submit Scheds with grid submission to CondorCE Hi all, does somebody has maybe already experiences with combining remote submission with gridward submission to CondorCEs? Thing is, that we have a number of nodes for our users, that act as remote submitters to the actual schedulers. Now it would come handy, not only to submit to the local Condor but also allow our users to do submissions into the Grid targeting CondorCEs. Since the Schedd would have to do the authentication through the users' proxy X509, it would need to be passed forward like kerberos etc. tickets/tokens. And are there other caveats, that might need to be considered in such a setup? Maybe somebody has already a working similar setup? Cheers, Thomas
Description: S/MIME Cryptographic Signature