Posted: 28 Apr 2017 10:39 EDT Last activity: 1 Aug 2017 11:12 EDT
Proxy for Microsite Access
We have implemented microsite and that link is included in the email sent to customer. This public URL and microsite URL we have give some proxy URL so that the pega server is not visible by the customer and inside redirection is happening. But while redirecting to PRPCGateway we are facing issue like: 301, we have changed the gateway url from the web mashup as the proxy url but that proxy URL is not coming here. It is coming as https://<domainname>.prgateway/PRPCGateway. Could anyone please let me know from where I can change so that while entering in PRPCGateway it comes with the proxy URL.
***Updated by moderator: Lochan to add Categories; add SR details***
Our infra team has provided one proxy address like: https://<servername>/abc/xyz and we are putting the same in the public URL and in the microsite url instead of Pega URL. Through F5 it is getting redirected to the specific pega server. Now when it is coming to PRPCGateway then it is taking as https://<servername>/prgateway/PRPCGateway ,here server name is the proxy server name.
What kind of configuration do we have to do in the web.xml file in pegateway.ear so that it is redirected to pega server?
We have implemented SSO SAML Authentication using reverse proxy junction and followed Option A in the link: https://pdn.pega.com/how-configure-reverse-proxy-server . After SSO Authentication, the request was redirected to the Pega server URL. How can we remove the redirections so the Proxy URL is retained? Is there any additional configurations that need to be done either on the Pega or Web Proxy side? Option A doesn't seem to work.
This is what we've done so far:
1. Set the context URI on the Web proxy config for HTTP header