continuous integration - How to properly configure Jenkins GitLab plugin credential provider with API Token

Question

I have created a Webhook in GitLab to use secret token generated on my Jenkins job configuration. I get a 403 error when I test this Webhook, with a message "No valid crumb provided". A Jenkins GitLab plugin needs to be installed on Jenkins server, and I verified this is already installed on our enterprise Jenkins server. The documentation quotes that I have to configure Jenkins server by adding GitLab API Token at Jenkins Credential Provider. I don't have overall administer access on our enterprise Jenkins server, so I couldn't reach this part of the UI. I am wondering, if this API token is already configured on our enterprise server, as I see the plugin is installed. Is the API token on Jenkins Credential Provider singular for all the users, or this part needs to be configured individually to make a GitLab webhook work? I have this question, as there is a field in this place "GitLab host URL (not the url for repository)"

question from:https://stackoverflow.com/questions/65948505/how-to-properly-configure-jenkins-gitlab-plugin-credential-provider-with-api-tok

Answer 1

Waitting for answers