Question
Cognizant technology solutions
IN
Last activity: 4 Oct 2018 5:58 EDT
Can we connect to https on port other than 443 from connect-soap ??
if we try from other port it other than 443 it looks like pega doesnt try to connect to endpoint. plz help.
***Moderator Edit: Vidyaranjan | Updated SR details***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
IN
Pegasystems Inc.
US
I highly suggest raising an SR for this issue.
Pegasystems Inc.
US
Yes, raise an SR. We can discuss how Pega handles this and what your options are. Please reply here with SR # so that any resolution can be added here as well.
Cognizant technology solutions
IN
I raised an SR with SR-B66869. I forgot to mention the below information in SR description.
1) the URL is working as expected with https port other than 443 when i test in Sopa ui.
I got below respone from adam yesterday itself. But the required port was already enabled on windows server. can you provide the solution/comments on the SR.
You can run HTTPS on any port if it's configured correctly. From that error message, your ISA server (a networking and security program that runs on Windows Server) is not configured to allow HTTPS connections through the port you are using. The best thing to do is to talk to your Windows Server admin to have them open the ports. Or, you can use the default port of 443 - generally, there's no reason to change the default. There are no changes you need to make in Pega, just in the network environment.
Pegasystems Inc.
Please check the Application server configuration where Pega is hosted. There are specific files based on the Application server type where ports can be configured.
Pegasystems Inc.
US
Pega certainly allows SSL traffic on non-standard ports.
From your SR details, it appears the required port is not enabled. You need to have your application server admin review this more closely. The exception being throw is pointing at the network. "Transport error: 502 Error: Proxy Error ( The specified Secure Sockets Layer (SSL) port is not allowed. ISA Server is not configured to allow SSL requests from this port. Most Web browsers use port 443 for SSL requests. )"
The exception seen in your PegaRULES log is all WebLogic code. It doesn't appear there is anything in Pega here that could be causing this issue.
Pega certainly allows SSL traffic on non-standard ports.
From your SR details, it appears the required port is not enabled. You need to have your application server admin review this more closely. The exception being throw is pointing at the network. "Transport error: 502 Error: Proxy Error ( The specified Secure Sockets Layer (SSL) port is not allowed. ISA Server is not configured to allow SSL requests from this port. Most Web browsers use port 443 for SSL requests. )"
The exception seen in your PegaRULES log is all WebLogic code. It doesn't appear there is anything in Pega here that could be causing this issue.
Accepted Solution
Pegasystems Inc.
IN
Hello,
The SR was resolved with the below explanation.
You can run HTTPS on any port if it's configured correctly. Configure the ISA server (a networking and security program that runs on Windows Server) to allow HTTPS connections through the port you are using. The best thing to do is to talk to Windows Server admin to have them open the ports. Or, you can use the default port of 443 - generally, there's no reason to change the default.
Thanks!
Hello,
The SR was resolved with the below explanation.
You can run HTTPS on any port if it's configured correctly. Configure the ISA server (a networking and security program that runs on Windows Server) to allow HTTPS connections through the port you are using. The best thing to do is to talk to Windows Server admin to have them open the ports. Or, you can use the default port of 443 - generally, there's no reason to change the default.
Thanks!