Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-58858

Configuration as Code value for securityRealm reset after reboot

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Not A Defect
    • Labels:
      None
    • Environment:
      Ubuntu: 18.04
      Docker: 18.09.7, build 2d0083d
      Jenkins: 2.176.2
      Config as Code Plugin: 1.27
    • Similar Issues:

      Description

      We are trying to use the https://wiki.jenkins.io/display/JENKINS/Reverse+Proxy+Auth+Plugin to handle our authentication. We can get the plugin configured correctly and after that export the config as code .yaml and save it on the filesystem. The problem is when we reboot jenkins it revertes to Internal Jenkins DB users, instead of using the reverse proxy.

      Here is the snippet of JCasC yaml we get from exporting the config from Jenkins:

        securityRealm:     reverseProxy:       disableLdapEmailResolver: false
            forwardedUser: "X-Forwarded-User"
            headerGroups: "X-Forwarded-Groups"
            headerGroupsDelimiter: "|"
            inhibitInferRootDN: false
            updateInterval: 15
            userSearch: "uid={0}"
      

      Marking as minor as there is a workaround (reset the value after each reset), but it would be really nice not to have to work around it .

      Not 100% is this is a bug with this or the reverse auth proxy, but raising here first seemed to make sense.

        Attachments

          Activity

            People

            Assignee:
            ewel Ewelina Wilkosz
            Reporter:
            canuck1987 Tim Brown
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: