Important: I am not using LDAP for Jenkins, but instead "Jenkins' own user database" as I want to manage myself the users.
I'm trying to trigger a build from Gitlab using Jenkins webhooks. I have created a token for my admin user and I gave to Gitlab a URL like this : https://user:token@myserver/jenkins/job/jobname/build
Then I got a banner saying:
My guess is that Yunohost is preventing my webhooks calls to get to jenkins, although "visitors" are authorized to access the app.
I think it's a nginx configuration to change ? Maybe it's not a bug and using Jenkins without LDAP is not supported by YuNoHost?
Context
Hardware: Old laptop computer (Intel i3)
YunoHost version: 11.2.30
I have access to my server: Through SSH | through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no (appart from not using LDAP for Jenkins)
Using, or trying to install package version/branch: 2.426.3~ynh2
Steps to reproduce
Create a freestyle job
To to Manage Users > Users in Jenkins
Select a user with the ability to build and generate an API token
Try to use the webhook with curl : curl -X POST https://myserver/jenkins/job/jobname/build --user username:token
Obtain a 401 from Yunohost Nginx
Expected behavior
The webhook trigger the build.
Logs
The request doesn't create access log inside jenkins, inferring that the request is not reaching it.
Hello!
Important: I am not using LDAP for Jenkins, but instead "Jenkins' own user database" as I want to manage myself the users.
I'm trying to trigger a build from Gitlab using Jenkins webhooks. I have created a token for my admin user and I gave to Gitlab a URL like this : https://user:token@myserver/jenkins/job/jobname/build Then I got a banner saying:
So I tried with cURL:
curl -X POST https://myserver/jenkins/job/jobname/build --user username:token
and I obtain the same 401 error.But if I gave my yunohost credential instead
--user ynh_user:ynh_pass
I obtain this, which seems to be the real 401 from Jenkins:My guess is that Yunohost is preventing my webhooks calls to get to jenkins, although "visitors" are authorized to access the app. I think it's a nginx configuration to change ? Maybe it's not a bug and using Jenkins without LDAP is not supported by YuNoHost?
Context
Steps to reproduce
Manage Users
>Users
in Jenkinscurl -X POST https://myserver/jenkins/job/jobname/build --user username:token
Expected behavior
The webhook trigger the build.
Logs
The request doesn't create access log inside jenkins, inferring that the request is not reaching it.