jenkins/inbound-agent unable to connect when authorizationStrategy set to unsecured

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Minor
    • Component/s: remoting
    • Environment:

      I created a Jenkins server using jenkins/jenkins:lts-alpine as Docker image and left the configuration more or less untouched (admin user created, server URL set).

      Created a new node on the UI, left everything default (filled in the work-directory).

      Then created an agent using jenkins/inbound-agent:latest as Docker Image and tried to configure it by passing -url and -workDir as well as the agent's name. Instructions taken from the agent's status page.

      Now, the agent wouldn't connect, stating that I had to pass not only the agent's name, but also the secret. I tried to pass an empty string for the secret, but that would then fail the authorization header stage when connecting.

      Following the instructions on my machine (Ubuntu 23.04) from the agent's status page - lacking a security key - did work just fine though.

      In the end, it turns out that I just had to change Global Security > Authentication > Authorization from "Anyone can do anything" to "Logged-in users can do anything".

      IMHO, it should be possible to skip passing a security key to the inbound-agent Docker container.

            Assignee:
            Unassigned
            Reporter:
            Nils
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: