In fact, you can add or modify jsp files within any of the subdirectories under deploy/itg.war/web/knta/ and they will be recompiled before use after the next bounce. Any changes will need to be reapplied after an upgrade, though.
We added a button on the login page that opens a specific request form without having the user log in. This is done by hardcoding a user name and password in the form containing that button. This user name has very restricted access that limits it to the one specific activity.
This workaround is not possible with our environment. We've been implemented Web Remote Single Sign On. We no longer go thru PPM logon page. Besides this jsp will be access by another system thru URL and there's no human interaction. Any other workaround in mind?
PPM validation can be set on an individual user record while most users are configured for a different validation mechanism. The predefined login credentials can be (and in fact would need to be) built into the page for the URL used by the users.
I am attaching a stripped down version of the page we are generating. It is derived from the code in Logon.jsp and extended as necessary to meet our needs. I have not executed this specific file so I cannot guarantee it will work as is, but it should convey the basic idea. For instance, the references to PPM files would need to either be extended to have full paths or be deleted.