I installed new jenkins setup with latest version(2.46.1) and later upgraded to 2.46.2 since it prompted me to upgrade.

      When I try to create job and add SVN Credentials, I get only Domain and Kind populated with "Global credentials (unrestricted)" and "Username and password" respectively but I get no field to enter my credentials(screenshot.1.jpg).

      Alternatively, I tried to add credentials by clicking on Jenkins --> Credentials --> Click (global) under Stores scoped to Jenkins --> Add credentials. I'm getting only "Kind" populated with "Username with password" and "Scope" being blank(screenshot.2.jpg). When I Ignore and try to enter credentials, it throws HTTP 403 error with a message "No valid crumb was included in the request"(screenshot.3.jpg).

        1. screenshot.1.jpg
          screenshot.1.jpg
          92 kB
        2. screenshot.2.jpg
          screenshot.2.jpg
          94 kB
        3. screenshot.3.jpg
          screenshot.3.jpg
          41 kB

          [JENKINS-44006] Not able to add credentials.

          I don't know how, I am able to Add Credentials now. I did not make any changes to the server machine or Jenkins. But I keep getting "No valid crumb was included in the request" issue randomly. Updating the Priority to Minor from Major.

          Adithya Ranganath added a comment - I don't know how, I am able to Add Credentials now. I did not make any changes to the server machine or Jenkins. But I keep getting "No valid crumb was included in the request" issue randomly. Updating the Priority to Minor from Major .

          By any chance do you have Jenkins behind a reverse proxy / apache httpd / nginx / haproxy / etc

          If you do then this is not an issue with the credentials plugin, rather a configuration issue in your reverse proxy... there is probably an admin monitor warning from Jenkins core on the Manage Jenkins screen... 

          Stephen Connolly added a comment - By any chance do you have Jenkins behind a reverse proxy / apache httpd / nginx / haproxy / etc If you do then this is not an issue with the credentials plugin, rather a configuration issue in your reverse proxy... there is probably an admin monitor warning from Jenkins core on the Manage Jenkins screen... 

            stephenconnolly Stephen Connolly
            kradikar Adithya Ranganath
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: