-
-
Notifications
You must be signed in to change notification settings - Fork 74
No valid crumb in POST request #56
Comments
This is in a Jenkins log file right? What version of Jenkins do you use? This plugin should probably be extended with functionality for getting getting that crumb. |
Sorry about my unclearness :) Jenkins version: 1.624 |
I saw you fork, are you planning on submitting a pull requst for this? It is important that the solution is not Jenkins-specific. This could be solved by adding a feature that can:
|
Currently I'm just looking into the code to see if I could solve it. It doesn't look promising right now :) |
* Evaluated in content of a URL. Raw content or value of a xPath or JsonPath * Bugfix: Closing inputstream after invokation. This will have caused "IOException: Too many open files"
* Evaluated in content of a URL. Raw content or value of a xPath or JsonPath * Bugfix: Closing inputstream after invokation. This may have caused "IOException: Too many open files"
* Evaluated in content of a URL. Raw content or value of a xPath or JsonPath * Bugfix: Closing inputstream after invokation. This may have caused "IOException: Too many open files"
* Evaluated in content of a URL. Raw content or value of a xPath or JsonPath * Bugfix: Closing inputstream after invokation. This may have caused "IOException: Too many open files"
* Evaluated in content of a URL. Raw content or value of a xPath or JsonPath * Bugfix: Closing inputstream after invokation. This may have caused "IOException: Too many open files"
* Evaluated in content of a URL. Raw content or value of a xPath or JsonPath * Bugfix: Closing inputstream after invokation. This may have caused "IOException: Too many open files"
* Evaluated in content of a URL. Raw content or value of a xPath or JsonPath * Bugfix: Closing inputstream after invokation. This may have caused "IOException: Too many open files"
Released in 1.22, open issue again if problem still exists! |
The feature seems to work fine, however I don't understand how to use it. Currently I'm always sending .crumb:, not just the crumb. Can you add a turtorial to the readme on how to use this feature properly? :) |
If you browse to: |
I get: The raw document (Without the concat) looks like this: <defaultCrumbIssuer>
<crumb>a9fc665a713a53587bcec672d66ba935</crumb><crumbRequestField>.crumb</crumbRequestField>
</defaultCrumbIssuer> And the json object looks like this: {"crumb":"a9fc665a713a53587bcec672d66ba935","crumbRequestField":".crumb"} So ideally there would be some way of easily getting the value of crumbRequestField=crumb However if you call it with: Now this was a long answer for a short question |
Ok I see, I'll have a look later today. I think maby you should enter: |
That returns: <crumb>a9fc665a713a53587bcec672d66ba935</crumb> So if I use that I get: |
Perhaps adding /text() helps? |
I tried that, it returns a security error: Problem accessing /crumbIssuer/api/xml. Reason:
|
I may implement option to extract value from regexp into the ${INJECTION_URL_VALUE} variable. You may be able to solve this with the current implementation, if you install this in Jenkins: |
* To be able to extract crumb from Jenkins even if primitive XPath result sets forbidden
* To be able to extract crumb from Jenkins even if primitive XPath result sets forbidden
* To be able to extract crumb from Jenkins even if primitive XPath result sets forbidden
Released regular expression feature in 1.27 and updated readme about it. |
Whenever I trigger a build from Stash I get the error:
WARNING: No valid crumb was included in request for XXX. Returning 403.
in Jenkins.
I have entered my username and password in the configuration so that shouldn't be the problem.
The text was updated successfully, but these errors were encountered: