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
- duplicates
-
-
- Resolved
-
Activity
When I want to create a certificate credentials entry i get a NullPointerException (see stack_trace_Create_certificate_credentials.txt
)
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 ) 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.
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. Are you using nginx?
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;
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; Same problem with crumbs and nginx as reverse proxy
Florian Storz
added a comment - Same problem with crumbs and nginx as reverse proxy With the solution from JENKINS-12875 I resolved my problem.
Florian Storz
added a comment - With the solution from JENKINS-12875 I resolved my problem. 
I reinstalled jenkins, and with initial configuration it works again. But as I configured our LDAP authentication the same problem occures as mentioned above!