Proxy for Microsite Access
Hello,
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.
Thanks
Saikat
***Updated by moderator: Lochan to add Categories; add SR details***
Accepted Solution
Pegasystems Inc.
IN
Hello!
On reviewing the SR, we see that the issue was resolved after applying HFix-26802. Please create a request type of media request over the my support portal to obtain this hotfix.
Regards,
Pegasystems Inc.
US
Please refer to this link: https://pdn.pega.com/how-configure-reverse-proxy-server (follow the approach of Option A). Let us know if you have any further questions.
HCL Technologies BV
NL
Hi Kevin,
Thanks for the reply. In the document it is written like
Add the following information to the HTTP header:
PegaRULES-SetContextURI: http:// proxyserverinformation
where the value of the header is the proxy server URI.
Could you please elaborate more about Set-ContextURI part, where can we find it, also how to add it in the HTTP header for the microsite.
Pegasystems Inc.
US
that is specific to proxy server, e.g., this link gives you an example of using nginx as reverse proxy - work with your proxy server admin as needed.
HCL Technologies BV
NL
Hello Kevin,
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?
Thanks
Saikat
Tata Consultancy Services Australia
PH
Hi Kevin,
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
PegaRULES-SetContextURI: http:// proxyserverinformation
2. Updated the prconfig.xml file to set the ContextRewriteEnable entry to true:
<env name="Initialization/ContextRewriteEnabled" value="true" />
Thanks,
Hi Kevin,
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
PegaRULES-SetContextURI: http:// proxyserverinformation
2. Updated the prconfig.xml file to set the ContextRewriteEnable entry to true:
<env name="Initialization/ContextRewriteEnabled" value="true" />
Thanks,
Mariel
Thanks,
Mariel
Pegasystems Inc.
IN
Hi Saikat,
Please let us know if you do log an SR for this and its ID. That way we can track it and follow-up this discussion with the resolution.
Thank you,
Accepted Solution
Pegasystems Inc.
IN
Hello!
On reviewing the SR, we see that the issue was resolved after applying HFix-26802. Please create a request type of media request over the my support portal to obtain this hotfix.
Regards,