Closed
Solved
URLs Redirection after migration to Kubernetes
On our current VM deployment with PEGA 8.7.3, we have configured some redirection and Snapstart URL shortcuts using the Tomcat index.jsp file (Tomcat/webapps/ROOT/index.jsp).
After migrating to Kubernetes and Platform 23, is there an alternative way to perform such redirections on the Kubernetes deployment? such as redirection for the SSO URL and Snapstart redirections (url/c-XXXX) etc..
***Edited by Moderator Rupashree to add Capability tags***
To see attachments, please log in.
Accepted Solution
Posted: 2 years ago
Updated: 1 year ago
Updated: 30 Apr 2024 12:10 EDT
MOD
Pegasystems Inc.
GB
@ElieC319 our SME has provided the following:
" By default, in the Pega provided docker runtime image, we redirect any unauthenticated request without a context in the URL (i.e. the ROOT context) to prweb. So if you are using our image, you should get this behavior for free. If you need something more elaborate, or a different behavior, then redirection can also be handled via their load balancer configuration (e.g. https://doc.traefik.io/traefik/middlewares/http/redirectregex/)
Once traffic reaches Infinity’s context (e.g. prweb), then the platform also allows clients to manage their Authentication Service to a specific URL pattern to avoid any web.xml customization and redeployment:
https://docs.pega.com/bundle/platform-88/page/platform/security/servlet-management.html
We do support web.xml customization in the Pega Helm charts if that is required however :
https://github.com/pegasystems/pega-helm-charts/tree/9ccd6b510493e83d7a33c56cfee2d886491c03b0/charts/pega#pega-configuration-files
We are not sure how Snapstart fits into your question.
@ElieC319 our SME has provided the following:
" By default, in the Pega provided docker runtime image, we redirect any unauthenticated request without a context in the URL (i.e. the ROOT context) to prweb. So if you are using our image, you should get this behavior for free. If you need something more elaborate, or a different behavior, then redirection can also be handled via their load balancer configuration (e.g. https://doc.traefik.io/traefik/middlewares/http/redirectregex/)
Once traffic reaches Infinity’s context (e.g. prweb), then the platform also allows clients to manage their Authentication Service to a specific URL pattern to avoid any web.xml customization and redeployment:
https://docs.pega.com/bundle/platform-88/page/platform/security/servlet-management.html
We do support web.xml customization in the Pega Helm charts if that is required however :
https://github.com/pegasystems/pega-helm-charts/tree/9ccd6b510493e83d7a33c56cfee2d886491c03b0/charts/pega#pega-configuration-files
We are not sure how Snapstart fits into your question.
I can only find references to Snapstart in the ‘Other resources’ page.
The documentation links to an old ‘collaborate’ Limitations of Snapstart url in SPA discussion of the Pega Support Centre :