-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSRF enabled -> Missing or bad crumb data if use Redirect to other Port #193
Comments
Where you can enter api token ? |
In password field. In some of next release we will document this in UI. Something like Password/Token |
Thanks for such quick answer |
No problem |
Update: It appears the stack trace is generated when submitting the correct, but not working crumb, and clicking OK to close the Jenkins Control Plugin configuration section, then clicking the "Refresh latest builds" button, not the Test Connection button. No stack trace is generated when clicking Test Connection, only the error message. I'm getting the same "[Fail] CSRF enabled -> Missing or bad crumb data" but without Apache and a different stack trace. I am running Jenkins 2.222.1 on Ubuntu 18.04. I installed IntelliJ and the Jenkins Control Plugin (0.12.0-2019.3). When I enter the crumb data from http://jenkins-url:8080/crumbIssuer/api/xml?tree=crumb and click Test Connection, I get the error. IntelliJ IDEA Details Stack Trace
Is this the appropriate location to post this, or would you prefer a new issue? |
Hi @jep,
Jenkins say that;
So it is recommend to use a API Token instead a password. then you can work without a crumb. see #173 Hope it helps. I will update the UI in one of next release to change password with API Token to clarify this |
I apologize for overlooking this. Your suggestion resolved the issue. Thank you for your quick response! |
improved redirect handling with 0.13.17 If there are still issues please reopen or file new issue |
If you use an Apache with Redirect Port 80 --> 8080 and use APi Token without Crumb Token you will receive followong error:
The text was updated successfully, but these errors were encountered: