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

Credentials Scope dropdown is empty for new entry

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Component/s: credentials-plugin
    • Labels:
    • Environment:
      Ubuntu 12.04 LTS, Jenkins 1.609, credentials-plugin 1.22 and 1.21
    • Similar Issues:

      Description

      When I create a new entry in global credentials the dropdown of scope is empty! When I save the entry, a error page is shown with the attached stack trace.

        Attachments

          Issue Links

            Activity

            Hide
            buderu Florian Storz added a comment -

            I reinstalled jenkins, and with initial configuration it works again. But as I configured our LDAP authentication the same problem occures as mentioned above!

            Show
            buderu Florian Storz added a comment - I reinstalled jenkins, and with initial configuration it works again. But as I configured our LDAP authentication the same problem occures as mentioned above!
            Hide
            buderu Florian Storz added a comment - - edited

            When I want to create a certificate credentials entry i get a NullPointerException (see stack_trace_Create_certificate_credentials.txt)

            Show
            buderu Florian Storz added a comment - - edited When I want to create a certificate credentials entry i get a NullPointerException (see stack_trace_Create_certificate_credentials.txt )
            Hide
            buderu Florian Storz added a comment -

            After further investigation I figured out that the problem is the "Cross-Site-Request-Forgery" security option. When this option is enabled, the credentials plugin stops to work. When it is disabled everything works as expected.

            Show
            buderu Florian Storz added a comment - After further investigation I figured out that the problem is the "Cross-Site-Request-Forgery" security option. When this option is enabled, the credentials plugin stops to work. When it is disabled everything works as expected.
            Hide
            danielbeck Daniel Beck added a comment -

            Are you using nginx?

            Show
            danielbeck Daniel Beck added a comment - Are you using nginx?
            Hide
            buderu Florian Storz added a comment -

            Yes, with following configuration:
            root /var/cache/jenkins/war/;
            proxy_pass http://127.0.0.1:8080/jenkins;
            proxy_pass_request_headers on;

            #Proxy Settings
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header Host $http_host;
            proxy_set_header X-Real-IP $remote_addr;

            Show
            buderu Florian Storz added a comment - Yes, with following configuration: root /var/cache/jenkins/war/; proxy_pass http://127.0.0.1:8080/jenkins ; proxy_pass_request_headers on; #Proxy Settings proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr;
            Hide
            buderu Florian Storz added a comment -

            Same problem with crumbs and nginx as reverse proxy

            Show
            buderu Florian Storz added a comment - Same problem with crumbs and nginx as reverse proxy
            Hide
            buderu Florian Storz added a comment -

            With the solution from JENKINS-12875 I resolved my problem.

            Show
            buderu Florian Storz added a comment - With the solution from JENKINS-12875 I resolved my problem.

              People

              • Assignee:
                Unassigned
                Reporter:
                buderu Florian Storz
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: