com.dabsquared.gitlabjenkins.gitlab.api.impl.ResteasyGitLabClientBuilder$LoggingFilter filter
Call GitLab:
HTTP method: GET
URL: https://gitlab-ee-internal/api/v4/user
Request headers: [
Accept = [application/json],
PRIVATE-TOKEN = [****FILTERED****]
]
com.dabsquared.gitlabjenkins.gitlab.api.impl.ResteasyGitLabClientBuilder$LoggingFilter filter
Got response from GitLab:
URL: https://gitlab-ee-internal/api/v4/user
Status: 400 Bad Request
Response headers: [
Connection = [close],
Content-Length = [246],
Content-Type = [text/html],
Date = [ Wed, 03 Apr 2019 20:36:49 GMT],
Server = [nginx]
]
Response Body: <html>
<head><title>400 No required SSL certificate was sent</title></head>
<body bgcolor="white">
<center><h1>400 Bad Request</h1></center>
<center>No required SSL certificate was sent</center>
<hr><center>nginx</center>
</body>
</html>
Problem description
Describe your problem in a meaningful way:
I'm trying to test the connection in Jenkins->Manage Jenkins->Configure System: GitLab. I've inserted the Connection name, GitLab host URL, and Credentials with the API token. I click the Test Connection button, and the above error happens.
I'm expecting this to successfully connect to GitLab. Using a curl command to verify this, the Jenkins server certs are able to access https://gitlab-ee-internal/api/v4/user with the Private Token and successfully return back a response. Am I missing a configuration setting to tell Jenkins to use server certs with the GitLab plugin?
Before submitting an issue I have first:
Issue
Context
Logs & Traces
Problem description
Describe your problem in a meaningful way:
Thanks for any help!