I haven't tried it so I don't know if it works, but have you tried passing the Authorization header in the request rather than setting username & password as part of the URL? e.g. `Authorization:Basic username:apiToken` where the whole `username:apiToken` is base-64 encoded
Richard. On Thu, 19 Mar 2020 at 14:05, Jheison Rodriguez <[email protected]> wrote: > currently I'm using a webhooks token for trigger Jobs from GitLab to > Jenkins, I have a global user so a token set up for all project something > like this: https://USERID:APITOKEN@JENKINS_URL/project/YOUR_JOB > <https://USERID:APITOKEN@jenkins_url/project/YOUR_JOB> > > Additionally, when I create a new version of the Jenkins master the token > is updated and I need to update in each GitLab project. > > I'd like to know if someone has experienced this and had managed this kind > of set up in another way? Also to avoid expose the token in the webhooks' > URL (security concern) or update it (even with scripts) for each GitLab > project. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/7d84e91d-3682-4a56-b366-7b92dbbac51e%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/7d84e91d-3682-4a56-b366-7b92dbbac51e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAAy0hwf5A2xgwxsJzPteKQ78aYG1KSCy1jLOzcWCGsoJ14DX6w%40mail.gmail.com.
