Pega url after enabling SSL/TLS on app server doesnt work without hashed session id in url
Hi - Can some one please help me resolve the issue which I am facing after importing SSL/TLS certificates and performing other configuration on app server.
Now I can access my pega using url : https://xyz.mycompany.com/prweb/PRServlet/beEBp4uRVTogorRwSwWqbOtn9IL2fwdI*/!STANDARD
but I can not access pega using this url(without hashed requestor id in the url) https://xyz.mycompany.com/prweb/PRServlet. When I enter this url in my browser it seems trying to connect to server but after a minutes is shows "This page can't be displayed" error in IE browser instead of pega login screen in IE11.
I need to make sure that this url (https://xyz.mycompany.com/prweb/PRServlet) works without any session id in the url. So am I missing something in configuration?
My application details are as below:
Pega v7.1.5
Pega's native form based authentication(no custom authentication)
Hi - Can some one please help me resolve the issue which I am facing after importing SSL/TLS certificates and performing other configuration on app server.
Now I can access my pega using url : https://xyz.mycompany.com/prweb/PRServlet/beEBp4uRVTogorRwSwWqbOtn9IL2fwdI*/!STANDARD
but I can not access pega using this url(without hashed requestor id in the url) https://xyz.mycompany.com/prweb/PRServlet. When I enter this url in my browser it seems trying to connect to server but after a minutes is shows "This page can't be displayed" error in IE browser instead of pega login screen in IE11.
I need to make sure that this url (https://xyz.mycompany.com/prweb/PRServlet) works without any session id in the url. So am I missing something in configuration?
My application details are as below:
Pega v7.1.5
Pega's native form based authentication(no custom authentication)
TLS 1.2 on weblogic app server
Updated: 4 Nov 2015 12:52 EST
JPMC
US
Hi Chunzhi Hong - Thank you for your response! we are trying to implement SSL/TLS to access to pega. Web-logic admins have done their part and imported the certificate and done necessary changes on server side. Today we recycled server and cleaned up cache and now when we try to access pega using "https" (https://xyz.mycompany.com/prweb/PRServlet) it does not come up, for few seconds it seems trying to connect to pega and then it give give below error:
The connection has timed out
The server at xyz.mycompnay.com is taking too long to respond.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
This is happening only for pega application while other app hosted on same server instance are working using https url. Though pega application is working fine and is accessible using http url(http://xyz.mycompany.com/prweb/PRServlet )
Hi Chunzhi Hong - Thank you for your response! we are trying to implement SSL/TLS to access to pega. Web-logic admins have done their part and imported the certificate and done necessary changes on server side. Today we recycled server and cleaned up cache and now when we try to access pega using "https" (https://xyz.mycompany.com/prweb/PRServlet) it does not come up, for few seconds it seems trying to connect to pega and then it give give below error:
The connection has timed out
The server at xyz.mycompnay.com is taking too long to respond.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.
This is happening only for pega application while other app hosted on same server instance are working using https url. Though pega application is working fine and is accessible using http url(http://xyz.mycompany.com/prweb/PRServlet )
JPMC
US
Yes Chunzi! Now after server restart pega login screen it self is not coming when we use secure URL. Since it is kind of urgent I created a SR an hour back with all the screenshot and fiddler trace but I am yet to receive response from GCS team on this SR( SR-A12075). If you could help on this forum then I can withdraw the SR. Please suggest.
Pegasystems Inc.
JP
is your pega application deployed on a dedicated server instance?
there could be many server instances running on different ports for different applications.
Can you double check the server instance configuration to see if the ssl port is enabled as described in below link?
Pegasystems Inc.
JP
GCS team has better connections to SMEs and richer experiences for solving problems, so please keep contact with the GCS engineer who is handling your case. You can mention this mesh thread in your SR.
