What are the consequences of disabling servlet mappings in pega


We have come across few pega default servlet mappings in web.xml file in 7.3.1, where on hitting the server with these servlets pega is opening local login page. But in our application we are using Single Sign On and we dont want the external users hitting the local login page.

So, we are planning to block these servlets URLs at the to not to display the local login page.

Do we have any best way to do this and if we block the Servlets, will it have any issues while working with the application?


Keep up to date on this post and subscribe to comments

October 3, 2019 - 11:53am

That doesn't strike me as an unheard of thing to do.

You may want to consider still having some kind of admin node (outside of the user cluster set), in case you need to revert to these other servlets, so with them still being available in the web.xml for that node.

October 3, 2019 - 12:15pm