When connecting to the Seqera Platform using the Tower CLI, users must provide an SSL certificate. This works well when running the CLI from local machines or the HPC cluster's head node. However, when running jobs (e.g., the pipeline) from local machines, the issue occurs when the HPC SLURM cluster attempts to connect back to the Seqera Platform to retrieve essential run details (e.g., run IDs, organization/workspace names).

While the Tower CLI can authenticate using the SSL certificate and an SSH private key for submitting jobs, the compute nodes running the jobs often lack access to critical connection details, such as the SSL certificate and the user’s token. This lack of access prevents the compute node from successfully connecting back to the Platform.

The request is to find a way to automatically propagate these necessary connection details to the compute environment, allowing seamless communication between the Seqera Platform and the HPC cluster during job execution.