Environment
Novell Access Manager 3.1 Linux Novell Identity Server
Novell Access Manager 3.1 Windows Novell Identity Server
Novell Access Manager 3.1 Support Pack 2 applied
Novell Access Manager 3.1 Windows Novell Identity Server
Novell Access Manager 3.1 Support Pack 2 applied
Situation
Administrator customised the login pages at the Identity (IDP) server. After applying the changes, users trying to access the Identity Server login page would see the new customised login page correctly. Without entering the credentials to login, if the user then initiated a new session in another tab to the same Identity server login page (by hitting ctrl-T within Firefox for example) on the same browser, the login page would not be displayed. An error would be reported instead with the following details:
"An unsupported request was received and cannot be completed."
"An unsupported request was received and cannot be completed."
Resolution
Make sure that the custom login pages do not reference any objects from within the /nidp/idff/ path. In the case above, a request was coming into the IDP server for /nidp/idff/namcust.css.
Assuming IDP logging is enabled, the catalina.out file will show the following type of entry when the problem is detected
Walking back through the logs, one can see that the previous request to the IDP server was the following:
Assuming IDP logging is enabled, the catalina.out file will show the following type of entry when the problem is detected
<amLogEntry> 2010-09-07T17:32:29Z INFO NIDS Application:
AM#500105039: AMDEVICEID#2B666715DE7323BA:
AMAUTHID#F8E14FEC5E83DA826F0CA8623426F628: Error on session id
F8E14FEC5E83DA826F0CA8623426F628, error 2B666715DE7323BA, An unsupported request
was received and cannot be completed. null </amLogEntry>
Walking back through the logs, one can see that the previous request to the IDP server was the following:
<amLogEntry> 2010-09-07T17:32:29Z DEBUG NIDS Application:
Method: NIDPProxyableServlet.myDoGetWithProxy
Thread: http-10.240.111.17-8443-Processor1
****** HttpServletRequest Information:
Method: GET
Scheme: https
Context Path: /nidp
Servlet Path: /idff
Query String: null
Path Info: /namcust.css
Server Name: login.star.com
Server Port: 443
Content Length: -1
Content Type: null
Auth Type: null
:
Method: NIDPProxyableServlet.myDoGetWithProxy
Thread: http-10.240.111.17-8443-Processor1
****** HttpServletRequest Information:
Method: GET
Scheme: https
Context Path: /nidp
Servlet Path: /idff
Query String: null
Path Info: /namcust.css
Server Name: login.star.com
Server Port: 443
Content Length: -1
Content Type: null
Auth Type: null
:
:
<amLogEntry> 2010-09-07T17:32:29Z DEBUG NIDS Application:
Method: NIDPServletURLSchemaManager.A
Thread: http-10.240.111.17-8443-Processor1
Unable to find command in URL: logincust.css </amLogEntry>
Method: NIDPServletURLSchemaManager.A
Thread: http-10.240.111.17-8443-Processor1
Unable to find command in URL: logincust.css </amLogEntry>
What you have done is customised the login page and included a css file in
the /nidp/idff/ path ... which is a reserved path for all the services.