HP Integrated Lights-Out 2 User Guide

For example, when User1 logs in, the Web server builds the initial frames view, with current user: User1in the top pane, menu items in the left pane, and page data in the lower-right pane. As User1 clicks fromlink to link, only the menu items and page data are updated.While User1 is logged in, if another user, User2, opens another browser window on the same client andlogs in, the second login overwrites the cookie generated in the original User1 session. Assuming thatUser2 is a different user account, a different current frame is built, and a new session is granted. Thesecond session is displayed in the Active Sessions section of the iLO 2 Status page as current user: User2.The second login has effectively orphaned the first session (User1) by wiping out the cookie generatedduring User1's login. This behavior is the same as closing User1's browser without clicking the Log Outlink. User1’s orphaned session is reclaimed when the session timeout expires.Because the current user frame is not refreshed unless the browser is forced to refresh the entire page,User1 can continue navigating using his or her browser window. However, the browser is now operatingusing User2's session cookie settings, even though it is not readily apparent.If User1 continues to navigate in this mode (User1 and User2 sharing the same process because User2logged in and reset the session cookie), the following can occur:• User1's session behaves consistently with the privileges assigned to User2.• User1's activity keeps User2's session alive, but User1's session can time out unexpectedly.• Logging out of either window causes both window sessions to terminate. The next activity in theother window can redirect the user to the login page as if a session timeout or premature timeoutoccurred.• Clicking Log Out from the second session (User2) results in a Logging out: unknown pageto display before redirecting the user to the login page.• If User2 logs out then logs back in as User3, User1 assumes User3's session.• If User1 is at login, and User2 is logged in, User1 can alter the URL to redirect to the index page. Itappears as if User1 has accessed iLO without logging in.These behaviors continue as long as the duplicate windows are open. All activities are attributed to thesame user, using the last session cookie set.Displaying the current session cookieAfter logging in, you can force the browser to display the current session cookie by enteringjavascript:alert(document.cookie) in the URL navigation bar. The first field visible is thesession ID. If the session ID is the same among the different browser windows, then these windows aresharing the same iLO 2 session.You can force the browser to refresh and reveal your true identity by pressing the F5 key, selectingView>Refresh, or using the refresh button.Preventing cookie-related user issuesTo prevent cookie-based behavioral problems:• Start a new browser for each login by double-clicking the browser icon or shortcut.• Click the Log Out link to close the iLO 2 session before closing the browser window.Inability to access ActiveX downloadsIf your network does not allow ActiveX controls you can capture the DVC.DLL from a single system andthen distribute the file to client machines on the network.1. Log into iLO 2.2. Type https://ilo_name/dvc.cab in the browser address bar.Troubleshooting iLO 2 167