SVN post commit hook is giving 403 forbidden while triggering Jenkins job-CodePudding

The

My post commit hook file post-commit like the following ( I was removed post-commit.tmpl and created new post-commit file and added content here),

And My Jenkins freestyle jobs like the following,

NB-: Code change are successfully committing to SVN repository. Problem is when triggering the Jenkins job.

Can anyone guide me for following any official documentation or any mistake that I did here please?

CodePudding user response：

Maybe you hit the CSRF (Cross Site Request Forgery) Jenkins protection.

CSRF protection uses a token (called crumb in Jenkins) that is created by Jenkins and sent to the user. Any form submissions or similar action resulting in modifications, like triggering builds or changing configuration, requires that the crumb be provided.

Requests sent using the POST method are subject to CSRF protection in Jenkins >and generally need to provide a crumb.

If you have administrator permissions, you can configure CSRF Protection through Manage Jenkins » Configure Global Security » CSRF Protection.

If you authenticate your API calls with a username and a user API token then a crumb is not required from Jenkins 2.96. So you can:

Generate API token from Jenkins (admin permissions needed).

Then use the API token instead of password for your calls.

Reference:
https://www.jenkins.io/doc/book/security/csrf-protection/
Jenkins : Error 403 No valid crumb was included in the request : From TFS
https://support.cloudbees.com/hc/en-us/articles/219257077-CSRF-Protection-Explained
Jenkins: 403 No valid crumb was included in the request

CodePudding user response：

I think that Jenkins does not allow you to contact the notifyCommit URL from your hook script and therefore you receive the 403 Forbidden error. Contact an admin of your Jenkins server for assistance.

According to one of your screenshots, you did not select the option Trigger builds remotely (e.g, from scripts). You have to select this option.