May 27, 2010 at 09:06 PM

WinAD SSO errors for JAVA InfoView after SP3

27 Views

I had successfully deployed the WinAD SSO configuration for both the .NET and JAVA InfoView as documented in the SAP materials provided by Tim Ziemba and Miles Escow.

Yesterday, I applied the new BOE-XI (R-3.1) Service Pack 3 on our DEV server...and accepted the RE-DEPLOY WebApplications option during the install.

The .NET WinAD SSO is working 100% OK at http://<servername>/InfoViewApp/logon.aspx

However, after I updated all the server.xml and web.xml files as required for the Tomcat55 folders that were overwritten by the service pack - I am getting 404 "The requested resource is not available" errors for both the LogonService and the LogonNoSso.

http:// //InfoViewApp/logon/ logonService.do

http://<servername:8080>/InfoViewApp/logonNoSso.jsp

If I comment-out the REALM and FILTER MAPPING sections that are mentioned on Pages 17 and 18 of Tim Ziemba's "Complete" document then I get a Manual Login Screen that works - but no SSO.

Is it possible that the logonService.do and logonNoSso.jsp are broken by BOE-XI (R-3.1) Service Pack 3, and is there any way to get those components back...?