Environment
NetIQ Access Manager 4.2 Identity Server
NetIQ Access Manager 4.2 Mobile Access
NetIQ Access Manager 4.2 Mobile Access
Situation
Access Manager installed and working fine. Administrator manually restarts the Identity Server by running the 'rcnovell-idp restart' command at the server console. To test the IDP functionality after this restart, the administrator brings up a browser and tries to login. Instead of getting the IDP login page, the admin received a blank page - hitting the IDP login URL again does return a valid login page.
Resolution
Wait up to 2 mins before hitting the IDP server in the case where it is restarted manually. If fronted by load balancers, the IDP servers will probably not be brought into the rotation until this happens.
There is a sync issue that can cause the NIDP Portal page to not load (and execution remains at the end user login landing page). In the normal case of an IDP update from the UI, the sync issue should not arise because the IDP and the Portal should stay in sync. If however an admin is restarting the IDP manually, the IDP may be out of sync for up to two minutes. While the IDP is restarting, blank pages or a missing automatic redirection to the portal page (from the end user login page) are common. This sync problem will happen every time the IDP is manually restarted.
There is a sync issue that can cause the NIDP Portal page to not load (and execution remains at the end user login landing page). In the normal case of an IDP update from the UI, the sync issue should not arise because the IDP and the Portal should stay in sync. If however an admin is restarting the IDP manually, the IDP may be out of sync for up to two minutes. While the IDP is restarting, blank pages or a missing automatic redirection to the portal page (from the end user login page) are common. This sync problem will happen every time the IDP is manually restarted.