Environment
Novell Access Manager 3 Linux Access Gateway
Novell Access Manager 3 Access Administration
Novell Access Manager 3 Support Pack 4 applied
Novell Access Manager 3 Access Administration
Novell Access Manager 3 Support Pack 4 applied
Situation
Linux Access Gateway (LAG) proxy service setup with protected resources. All working fine with Access Manager 3.0 Support Pack 2 applied. After upgrading the Access Manager system to Support pack 4, users started reporting errors accessing one of the patch based multihomed services on the LAG.
The proxy service experiencing the issue had a path based multihomed resource of /SSO. There was a protected resource with two URLs defined for this path based resource:
/SSO/SSO.CAB
/SSO/WebAppMail.aspx
When the browser generated a HTTP request for http://www.pippo.com/SSO/WebAppMail.aspx, the web server would generate a 302 redirect to http://www.pippo.com/SSO/SSO.CAB. The proxy would process the response and return the 302 response to the browser as http://www.pippo.com/SSO/SSO.CAB/.
The browser would issue the HTTP request for http://www.pippo.com/SSO/SSO.CAB/, which resulted in a 404 not found error.
The proxy service experiencing the issue had a path based multihomed resource of /SSO. There was a protected resource with two URLs defined for this path based resource:
/SSO/SSO.CAB
/SSO/WebAppMail.aspx
When the browser generated a HTTP request for http://www.pippo.com/SSO/WebAppMail.aspx, the web server would generate a 302 redirect to http://www.pippo.com/SSO/SSO.CAB. The proxy would process the response and return the 302 response to the browser as http://www.pippo.com/SSO/SSO.CAB/.
The browser would issue the HTTP request for http://www.pippo.com/SSO/SSO.CAB/, which resulted in a 404 not found error.
Resolution
Merged the two protected resources URLs into a combined /SSO/* protected resource to work around the issue.