SYSTEMS AND METHODS FOR PROVIDING SESSION CONTINUITY ACROSS A CHASSIS MANAGEMENT CONTROLLER FAILOVER
A method for maintaining a continuous authenticated session in an information handling system including first and second chassis management controllers (CMCs) is provided. The first CMC receives user authentication information from a user, authenticates the user for a communication session based on the received user authentication information, generates session information regarding the communication session based at least on the received user authentication information, and stores the session information in memory accessible to the second CMC. Upon a failover from the first CMC to the second CMC, the second CMC automatically accesses the session information from the memory and uses the accessed session information to continue the communication session.
1 . A method for maintaining a continuous authenticated session in an information handling system including at least a first chassis management controllers (CMC) and a second CMC, the method comprising:
a first CMC receiving user authentication information from a user;
the first CMC authenticating the user for a communication session based on the received user authentication information;
the first CMC generating session information regarding the communication session based at least on the received user authentication information;
the first CMC storing the session information in memory accessible to the second CMC;
in response to a failover from the first CMC to the second CMC, the second CMC automatically accessing the session information from the memory; and
the second CMC using the accessed session information to continue the communication session.
2 . A method according to claim 1 , wherein the second CMC uses the accessed session information to continue the communication session without requiring re-authentication by the user.
3 . A method according to claim 1 , wherein the received user authentication information includes a username and a password.
4 . A method according to claim 1 , wherein generating session information regarding the communication session includes:
identifying the user based on the received user authentication information; and
automatically accessing privilege data associated with the identified user;
wherein the session information includes at least a portion of the user authentication information and at least a portion of the accessed privilege data.
5 . A method according to claim 1 , wherein generating session information regarding the communication session includes:
accessing a database corresponding user privilege data with user authentication information for each of multiple users;
identifying from the database user privilege data corresponding to the user authentication information received from the user; and
including at least a portion of the identified user privilege data in the session information.
6 . A method according to claim 1 , wherein generating session information includes:
determining a session type based at least on a type of communication link by which the user is connected to the first CMC; and
identifying the session type in the session information.
7 . A method according to claim 1 , wherein:
the first and second CMCs are located in a blade server chassis; and
the first CMC stores the session information in a persistent storage device shared by the first the second CMCs.
8 . A method according to claim 7 , wherein the persistent storage device comprises a chassis EEPROM in a local control front panel of the blade server chassis.
9 . An information handling system, comprising:
a first chassis management controller (CMC);
a second CMC; and
memory accessible to both the first and second CMCs;
the first CMC being configured to:
receive user authentication information from a user;
authenticate the user for a communication session based on the received user authentication information;
generate session information regarding the communication session based at least on the received user authentication information; and
cause the session information to be stored in the memory; and
the second CMC being configured to:
automatically access the session information from the memory in response to a failover from the first CMC to the second CMC; and
use the accessed session information to continue the communication session.
10 . An information handling system according to claim 9 , wherein the second CMC uses the accessed session information to continue the communication session without requiring re-authentication by the user.
11 . An information handling system according to claim 9 , wherein generating session information regarding the communication session includes:
identifying the user based on the received user authentication information; and
automatically accessing privilege data associated with the identified user;
wherein the session information includes at least a portion of the user authentication information and at least a portion of the accessed privilege data.
12 . An information handling system according to claim 9 , wherein generating session information regarding the communication session includes:
accessing a database corresponding user privilege data with user authentication information for each of multiple users;
identifying from the database user privilege data corresponding to the user authentication information received from the user; and
including at least a portion of the identified user privilege data in the session information.
13 . An information handling system according to claim 9 , wherein generating session information includes:
determining a session type based at least on a type of communication link by which the user is connected to the first CMC; and
identifying the session type in the session information.
14 . An information handling system according to claim 9 , further comprising a blade server chassis configured to house the first CMC, the second CMC, and the memory;
wherein the memory comprises a persistent storage device shared by the first the second CMCs.
15 . An information handling system according to claim 14 , wherein the persistent storage device comprises a chassis EEPROM in a local control front panel of the blade server chassis.
16 . Logic instructions for maintaining a continuous authenticated session in an information handling system including at least a first chassis management controllers (CMC) and a second CMC, the logic instructions embodied in tangible computer readable media and executable by a processor, comprising:
instructions for receiving user authentication information from a user;
instructions for authenticating the user for a communication session based on the received user authentication information;
instructions for generating session information regarding the communication session based at least on the received user authentication information;
instructions for storing the session information in memory accessible to the second CMC such that upon a failover from the first CMC to the second CMC, the second CMC can automatically access the session information from the memory and use the accessed session information to continue the communication session without requiring re-authentication by the user.
17 . Logic instructions according to claim 16 , wherein instructions for generating session information regarding the communication session include:
instructions for identifying the user based on the received user authentication information; and
instructions for accessing privilege data associated with the identified user;
instructions for including at least a portion of the user authentication information and at least a portion of the accessed privilege data in the session information.
18 . Logic instructions according to claim 16 , wherein instructions for generating session information regarding the communication session include:
instructions for accessing a database corresponding user privilege data with user authentication information for each of multiple users;
instructions for identifying from the database user privilege data corresponding to the user authentication information received from the user; and
instructions for including at least a portion of the identified user privilege data in the session information.
19 . Logic instructions according to claim 16 , wherein instructions for generating session information regarding the communication session include:
instructions for determining a session type based at least on a type of communication link by which the user is connected to the first CMC; and
instructions for identifying the session type in the session information.
20 . Logic instructions according to claim 16 , wherein instructions for storing the session information in memory accessible to the second CMC include instructions for storing the session information in a persistent storage device in a local control front panel of a blade server chassis that includes the first and second CMCs.