Скачать или смотреть Resolving HTTP ERROR 403 No valid crumb was included in the request in Jenkins

Learn how to fix the frustrating `HTTP ERROR 403` in Jenkins when trying to abort a job build. Follow our detailed steps to manage crumb values effectively.
---
This video is based on the question https://stackoverflow.com/q/73247907/ asked by the user 'eresque-' ( https://stackoverflow.com/u/19547474/ ) and on the answer https://stackoverflow.com/a/73275368/ provided by the user 'eresque-' ( https://stackoverflow.com/u/19547474/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How to deal with "HTTP ERROR 403 No valid crumb was included in the request" Jenkins?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding the HTTP ERROR 403 in Jenkins

When you're working with Jenkins and trying to abort a job build using Python's requests library, you might encounter an error message that reads: "HTTP ERROR 403 No valid crumb was included in the request." This can be frustrating, especially when you believe you’ve followed the right procedures. In this guide, we will explore what this error means and how to effectively resolve it.

What Causes the HTTP ERROR 403?

The HTTP ERROR 403 generally indicates that the request you are making is forbidden. With Jenkins, this often relates to the Crumb Issuer, which is a security feature designed to prevent CSRF (Cross-Site Request Forgery) attacks. Here are some reasons why you might see this error:

Missing or Incorrect Crumb Value: You've either not provided a crumb value or included an incorrect one in your request.

Authentication Issues: Your requests may not be authenticated properly.

Session Problems: Sending requests in different sessions may lead to issues with accessing resources.

Fixing the Problem

Recommended Approach: Use a Single Session

To resolve this issue, you need to ensure that both your Get and Post requests utilize the same session. This way, the Jenkins server can authenticate your requests correctly, thus avoiding the crumb validation error. Here’s a step-by-step guide to achieve this:

Step 1: Create a Session

First, you'll want to create a requests session. This session will handle all your requests, maintaining authentication and session details.

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Get the Crumb Value

Next, make a Get request to fetch the crumb value. This crumb needs to be sent along with your abort request.

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Post the Abort Request

Once you have retrieved the crumb, you can now send the Post request to abort the Jenkins job. Be sure to include the Jenkins-Crumb header in your request:

[[See Video to Reveal this Text or Code Snippet]]

Complete Code Example

Here’s the complete code that incorporates all the steps mentioned above:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

By following the steps outlined above, you should be able to effectively address the HTTP ERROR 403 No valid crumb was included in the request error in Jenkins. Always remember to perform both the Get and Post requests with the same session to maintain proper authentication.

Using a consistent session simplifies the handling of requests and avoids common pitfalls related to crumb management. Happy coding!