Closed fduranti closed 7 years ago
The only way that the /project endpoint authentication will work is if your webhook passes a valid jenkins username and password using HTTP basic auth. This in turn will depend on how you configure Jenkins user authorization. The simplest way is what you were attempting using a Jenkins user's username and API key and including them with your webhook, as in http://username:APIKEY@jenkinsserver.foo.com/...
See https://github.com/jenkinsci/gitlab-plugin/issues/418 for some more insight. Let me know if this helps.
Issue
Problem with authentication for /project end-point
Context
Logs & Traces
Problem description
I've integrated Jenkins pipeline with the Gitlab-EE Service Jenkins-CI (tried also with WebHook with the same result). I want jenkins to run a build when i do a push or merge. It works (with some issue) if the Authentication for /project end-point is disabled. If I enable the authentication it don't work and has different behaviour. I'm using a local defined user on jenkins with it's jenkins api token for authentication. Putting user and apitoken (tried also with password) on the fields on the Service Jenkins-CI page is not working (jenkins see the user as anonymous). For this I've asked to gitlab support as it seems a problem on how credential are passed. If i use the http://user:api@jenkinsserver syntax It's authenticating correctly and report an error if the user don't have Job/Build permission as expected. Using Matrix-based authorization or "logged-in users can do anything" I get a long error on the test of the service:
I get the same error doing the configuration from project webhooks.
I've also tried with gitlab oauth plugin for authorization and authentication
Anyone know what I'm doing wrong?