Posted: Fri Oct 21, 2016 3:01 am Post subject: Secure Gateway Client picks SSL Proxy objects instead of TCP
Voyager
Joined: 04 Sep 2012 Posts: 77 Location: UK beyond the meadows of RocknRoll
Hi All,
I encountered a very weird problem yesterday and have been able to replicate it.
So here are my flows and ports accessed are shown in brackets.
1st flow:
X App-->(3001)HTTPS FSH-->MPGW-->(5001)TCP Proxy Service(5101)-->SG Client-->Bluemix Zone which has SG fronting API.
2nd flow:
I had a separate SSL Proxy that I was testing to have HTTPs Mutual Auth and its configuration were Incoming Port 5201 and outgoing to SG client 5301. No MPGW configuration to SSL Proxy.
When testing the first flow, I noticed during reply, it was able to access the SSL Client Profile present in SSL Proxy and was throwing certificate related errors. Now how did this happen, I have no idea and once I change the SSL Client Profile in my SSL Proxy to no Server Certificate Validation, everything starts working again.
Why does a req sent via TCP Proxy Service into Secure Gateway client end up with a response that sees my SSL Proxy Service which is not even configured to be on that port. _________________ A Colorblind man may appear disadvantaged but he always sees more than just colors...
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum