[JIRA] (JENKINS-50160) Can't add credentials through https

2 views
Skip to first unread message

istomanton@gmail.com (JIRA)

unread,
Mar 14, 2018, 4:08:02 AM3/14/18
to jenkinsc...@googlegroups.com
Anton Anonymous created an issue
 
Jenkins / Bug JENKINS-50160
Can't add credentials through https
Issue Type: Bug Bug
Assignee: Stephen Connolly
Components: credentials-plugin
Created: 2018-03-14 08:07
Environment: Jenkins version 2.89.3
Credentials Plugin version 2.1.16
Priority: Major Major
Reporter: Anton Anonymous

When I try to add credentials for example login/password for docker registry, nothing happens and I get following error in console:

 Mixed Content: The page at 'https://example.com/job/dfo-pm-staging_backend_develop/configure' was loaded over HTTPS, but requested an insecure form action 'http://example.com/descriptor/com.cloudbees.plugins.credentials.Cred...ials.SystemCredentialsProvider$ProviderImpl/context/jenkins/addCredentials'. This request has been blocked; the content must be served over HTTPS.

I can change form url to https instead of http using developer tools and then it submits correctly. How do I fix this issue?

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

istomanton@gmail.com (JIRA)

unread,
Mar 14, 2018, 4:11:04 AM3/14/18
to jenkinsc...@googlegroups.com
Anton Anonymous updated an issue
Change By: Anton Anonymous
When I try to add credentials for example login/password for docker registry, nothing happens and I get following error in console (domain name changed to example.com) :
{quote} Mixed Content: The page at 'https://example.com/job/dfo-pm-staging_backend_develop/configure' was loaded over HTTPS, but requested an insecure form action 'http://example.com/descriptor/com.cloudbees.plugins.credentials.Cred...ials.SystemCredentialsProvider$ProviderImpl/context/jenkins/addCredentials'. This request has been blocked; the content must be served over HTTPS.
{quote}

I can change form url to https instead of http using developer tools and then it submits correctly. How do I fix this issue?

stephen.alan.connolly@gmail.com (JIRA)

unread,
Mar 14, 2018, 4:50:02 PM3/14/18
to jenkinsc...@googlegroups.com
Stephen Connolly commented on Bug JENKINS-50160
 
Re: Can't add credentials through https

sounds like your reverse proxy is not set up correctly.

istomanton@gmail.com (JIRA)

unread,
Mar 15, 2018, 4:05:02 AM3/15/18
to jenkinsc...@googlegroups.com

stephen.alan.connolly@gmail.com (JIRA)

unread,
Oct 31, 2018, 6:00:21 AM10/31/18
to jenkinsc...@googlegroups.com
Stephen Connolly assigned an issue to Unassigned
 

Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA

Change By: Stephen Connolly
Assignee: Stephen Connolly
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

ddigtiar@cloudbees.com (JIRA)

unread,
Feb 13, 2019, 1:06:02 AM2/13/19
to jenkinsc...@googlegroups.com
Denys Digtiar commented on Bug JENKINS-50160
 
Re: Can't add credentials through https

Anton Anonymous The X-Forwarded-Proto is the header your reverse proxy also needs to set, as far as I know.

piotr.bladek@outlook.com (JIRA)

unread,
Jul 29, 2019, 2:47:02 AM7/29/19
to jenkinsc...@googlegroups.com

I ran into same problem, Im using jenkins behind apache2 https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Apache

In my case solution was to setup following HTTPS proxy headers properly:

RequestHeader set X-Forwarded-Proto "https"
RequestHeader set X-Forwarded-Port "443"

 

Reply all
Reply to author
Forward
0 new messages