ATLAS HTCondor-CE ping with SCITOKEN

host: 
port: 
aud: 

HTCondor basic info

Name: cloud-htcondor-ce-3-kit.gridka.de
CE Version: 24.0.2
Version: $CondorVersion: 24.0.3 2025-01-03 BuildID: 777902 PackageID: 24.0.3-1 GitSHA: ef02b46e $
Platform: $CondorPlatform: x86_64_AlmaLinux8 $
Identity: condor@family

Test condor_ping with SCITOKEN credentials (new issuer)

04/03/25 20:46:04 recognized WRITE as authorization level, using command 60021.
Destination:                 schedd cloud-htcondor-ce-3-kit.gridka.de
Remote Version:              $CondorVersion: 24.0.3 2025-01-03 BuildID: 777902 PackageID: 24.0.3-1 GitSHA: ef02b46e $
Local  Version:              $CondorVersion: 24.0.6 2025-03-27 BuildID: 796350 PackageID: 24.0.6-1 $
Session ID:                  cloud-htcondor-ce-3-kit:1543678:1743705965:171375
Instruction:                 WRITE
Command:                     60021
Encryption:                  AES
Integrity:                   AES
Authenticated using:         SCITOKENS
All authentication methods:  SCITOKENS
Remote Mapping:              atlasprd@users.htcondor.org
Authorized:                  TRUE

Test condor_ping with SCITOKEN credentials (old issuer)

04/03/25 20:46:05 recognized WRITE as authorization level, using command 60021.
04/03/25 20:46:05 SECMAN: required authentication with schedd cloud-htcondor-ce-3-kit.gridka.de failed, so aborting command DC_SEC_QUERY.
WRITE failed!
AUTHENTICATE:1003:Failed to authenticate with any method
AUTHENTICATE:1004:Failed to authenticate using SCITOKENS

Test condor_ping with GSI credentials

This can't work with recent HTCondor-CEs that no longer support GSI

condor_ping result: 
04/03/25 20:46:05 recognized WRITE as authorization level, using command 60021.
WARNING: GSI authentication is enabled by your security configuration! GSI is no longer supported.
For details, see https://htcondor.org/news/plan-to-replace-gst-in-htcss/
04/03/25 20:46:05 SECMAN: no classad from server, failing
WRITE failed!
SECMAN:2011:Connection closed during command authorization. Probably due to an unknown command.

Test condor_ping with SSL credentials

This could work only with recent HTCondor-CEs, but only with special individual SSL mapping for certificate subject: 

SSL "" unix_account
condor_ping result: 
04/03/25 20:46:06 recognized WRITE as authorization level, using command 60021.
04/03/25 20:46:06 SECMAN: FAILED: Received "DENIED" from server for user unauthenticated@unmapped using method SSL.
WRITE failed!
SECMAN:2010:Received "DENIED" from server for user unauthenticated@unmapped using method SSL.

Client credentials

Token (new issuer): 
{
  "wlcg.ver": "1.0",
  "sub": "7dee38a3-6ab8-4fe2-9e4c-58039c21d817",
  "aud": [
    "cloud-htcondor-ce-3-kit.gridka.de:9619",
    "condor://cloud-htcondor-ce-3-kit.gridka.de:9619",
    "https://wlcg.cern.ch/jwt/v1/any"
  ],
  "nbf": 1743705964,
  "scope": "compute.read compute.cancel compute.modify compute.create",
  "iss": "https://atlas-auth.cern.ch/",
  "exp": 1744051564,
  "iat": 1743705964,
  "jti": "06d1115f-aebd-463e-87bf-4f5b64081306",
  "client_id": "7dee38a3-6ab8-4fe2-9e4c-58039c21d817"
}
Token (old issuer): 



Proxy:

Proxy not found: /tmp/x509up_u48.prd.htcondor.130 (No such file or directory)