We have modified web.xml to allow users to login using custom servlet url instead using custom authentication. The login is taking to 404 error or PRBasic screen. The same changes are working on 8.x versions in production today.
https://xxxx.com/poc/**login** - This is the url we would want the end users to use to login to Pega environment
Attached the web.xml we have modified to make this happen
Note: The same customized web.xml configuration is working today in 8.x environment
@VinodkumarG5467 It seems like there might be an issue with the servlet mapping in your web.xml file. Ensure that the servlet-name in your servlet-mapping matches the servlet-name in your servlet definition. Also, check if the url-pattern in your servlet-mapping is correctly defined. If you’re migrating from an older version of Pega to a newer one, there might be changes in the way servlets are handled, so ensure your customizations are compatible with the new version. If the issue persists, it might be helpful to check the server logs for more detailed error messages.]
This is a GenAI-powered tool. All generated answers require validation against the provided references.
Custom url required for login page
If you still need help please log a support issue via the MSP and provide the INC id here.
@VinodkumarG5467 can you confirm that you logged support ticket on May 2nd?
INC-B17993
Unable to login using customized Servlet url
The case has been resolved with the details as following:
Issue primary reason description:
As part of upgrading our Pega environments from 8.x to 23.1 using Containerized environemnt we have intsalled a a sandbox environemnt and modified the web.xml to allow users to login using custom url instead of default Pega default . The login is taking to 404 error or PRBasic screen
https://xxxx.com/poc/**login** - This is the url we would want the end users to use to login to Pega environment
Attached the web.xml we have modified to make this happen
Note: The same customized web.xml configuration is working today in 8.x environment
Explanation description:
Client was making changes under prweb instead of poc so it was not reflecting.
Once the web.xml change was done under poc, it is working as expected.
Can you please mark this with ‘Accept Solution’ to close off this thread?