AD Plugin No Longer Allows Fallback to Jenkins Internal User Database

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

XMLWordPrintable

      After upgrading to the Jenkins 2.516.1 and AD 2.40, I can no longer get Jenkins Internal Users to authenticate via the command line.  They can't login to the portal either.  Before this upgrade I was able to authenticate using the CLI from an external server with a command such as:

      ssh -p myPort myJenkinsInternalUser@myJenkinsMachine whoami

       

      This no longer works, and thus, my application which I designed to start all of my Jenkins builds and deploys no longer functions unless I shut down Jenkins security.

            Assignee:
            Félix Belzunce Arcos
            Reporter:
            Eric
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: