How to Invoke target url via https

Support Installation and Deployment
1

Imported Google Group message. Original thread at: Redirecting to Google Groups Import Date: 2016-01-19 21:07:52 +0000.
Sender:Jayadatta Vallabhaneni.
Date:Tuesday, 17 March 2015 19:47:14 UTC.

Hi,

could you please let me know if there is any parameter that needs to be enabled to post the data to target url via https.

In my scenario, client is post the data via http. TYK is forwarding it to an endpoint which can be accessed via https (one way certificate).

Thanks,
Jayadatta

2

Imported Google Group message.
Sender:Jayadatta Vallabhaneni.
Date:Wednesday, 18 March 2015 05:19:58 UTC.

Martin,

I was able to resolve this by manually adding the upstream target ca cert to /etc/ssl/certs/ca-certificates.crt file(i am using Ubuntu14.x). Now it is no more throwing the error.

Thanks,
Jayadatta

  • show quoted text -
3

Imported Google Group message.
Sender:Martin Buhr.
Date:Tuesday, 17 March 2015 20:15:24 UTC.

Hi,

There are no additional parameters, is your upstream URL set to use https? The gateway should just attempt to post to the proxy. However it might fail if the certificate is self signed, it’s something we’re looking at as an enhancement in future versions as many B2B scenarios have this.

I may be misunderstanding though?

Thanks,
Martin

4

Imported Google Group message.
Sender:Martin Buhr.
Date:Tuesday, 17 March 2015 21:07:01 UTC.

Hi Martin,

Yes, the upstream URL is using self signed certificate.

Thanks,
Jayadatta

  • show quoted text -
5

Imported Google Group message.
Sender:Jayadatta Vallabhaneni.
Date:Tuesday, 17 March 2015 21:11:21 UTC.

That could be causing your issues :slight_smile:

It’s a known problem and an enhancement that will be considered in an upcoming version (Custom SSL Certificate at the Target Endpoint · Issue #46 · TykTechnologies/tyk · GitHub)

Watch this space! :wink:

Thanks,
Martin

6

Imported Google Group message.
Sender:Martin Buhr.
Date:Wednesday, 18 March 2015 05:19:58 UTC.

Martin,

I was able to resolve this by manually adding the upstream target ca cert to /etc/ssl/certs/ca-certificates.crt file(i am using Ubuntu14.x). Now it is no more throwing the error.

Thanks,
Jayadatta

  • show quoted text -