Method and system for integrating additional functionality into a login system

• US 5,781,724 A
• Filed: 11/01/1996
• Issued: 07/14/1998
• Est. Priority Date: 11/01/1996
• Status: Expired due to Term

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Novell Incorporated (Open Text Corporation)
• Inventors: White, Kenneth Paul, Nevarez, Carlos A.
• Primary Examiner(s): Beausoliel, Jr., Robert W.
• Assistant Examiner(s): Baderman, Scott T.
• Application Number:
  US08/742,506
• Time in Patent Office: 620 Days
• Field of Search: 395/186, 395/187.01, 395/188.01, 395/609, 380/23, 380/25
• US Class Current: 726/17
• CPC Class Codes: G06F 21/31 User authentication

Abstract

A system and method for integrating additional functionality into a login system which includes registering a login extension operative to receive notification of an event generated by the login system. The login extension provides additional functionality and response to the received notification. The login extension is registered by the login system and authenticated to ensure that the login extension has proper access rights. An event manager of the login system communicates login events to the registered login extension which then provides additional desired functionality.

Claims

1. In a computer-implemented login system having event driven functionality, a method for integrating additional functionality into the login system, the method comprising:

(a) establishing a plurality of events, each event corresponding to a predetermined activity in the login process;

(b) registering with the login system a first login extension operative to receive notification of at least some of the events and operative to one of provide functionality in response to a received notification and take no action with regard to the received notification;

(c) initiating the registered first login extension;

(d) determining if the registered first login extension is a valid registered login extension, and if it is valid;

(i) enabling interaction with the registered first login extension, and

(ii) communicating the notification of the event to the registered first login extension, and if it is not valid;

(i) prohibiting interaction with the registered first login extension.

2. In a computer-implemented login system according to claim 1, wherein the determining step comprises:

receiving an authentication key from the registered first login extension;

determining if the authentication key is a valid authentication key, and if it is, returning an ok condition code to the registered first login extension.

3. In a computer-implemented login system according to claim 1, wherein the enabling step comprises passing to the login system a structure containing a pointer to the first registered login extension for invocation upon the generation of an event.

4. In a computer-implemented login system according to claim 3, further comprising maintaining a list of pointers to structures, each structure including a pointer to a registered login extension for invocation upon the generation of an event.

5. In a computer-implemented login system according to claim 1, further comprising registering the first login extension as one of a primary login extension and a secondary login extension.

6. In a computer-implemented login system according to claim 5, further comprising providing a default login extension, and registering the first login extension as a primary login extension to replace the default login extension.

7. In a computer-implemented login system according to claim 1, further comprising registering a first exception login extension associated with the registered first login extension, receiving from the registered first login extension a fail condition code, and communicating notification of the event to the registered first exception login extension in response to the receipt of the fail condition code.

8. In a computer-implemented login system according to claim 7, further comprising receiving from the registered first exception login extension a retry condition code, and recommunicating notification of the event to the registered first login extension in response to the receipt of the retry condition code.

9. In a computer-implemented login system according to claim 1, further comprising registering with the login system a second login extension operative to receive a notification of an event and operative to provide additional functionality in response to the received notification, and

controlling the communication of the event to the registered first and second login extensions as a function of a communication type of the event.

10. In a computer-implemented login system according to claim 1, further comprising

registering with the login system a second login extension operative to receive a notification of an event and operative to provide additional functionality in response to the received notification, and

controlling the communication of the event to the registered second login extension as a function of a returned condition code from the registered first login extension.

11. A method for integrating additional functionality into a login system, the method comprising:

establishing an plurality of event each event corresponding to a predetermined activity in the login process;

managing the processing of a plurality of events in a computer environment with an event manager capable of communicating events to multiple login extensions, the event manager having a default event interaction with a default login extension;

registering a login extension with the login system;

authenticating the login extension to the login system;

modifying the default event interaction in response to the registration to include communication of at least one event to the registered login extension.

12. In a method for integrating additional functionality into a login system according to claim 11, wherein the authentication step comprises:

receiving an authentication key from the registered login extension;

determining if the authentication key is a valid authentication key, and if it is, returning an ok condition code to the login extension.

13. In a computer-implemented login system according to claim 11, further comprising passing to the login system a structure containing a pointer to the login extension for invocation upon the generation of an event.

14. In a method for integrating additional functionality into a login system according to claim 11, wherein the modifying the default event interaction step comprises inhibiting communication of events to the default login extension.

15. In a method for integrating additional functionality into a login system according to claim 11, wherein the modifying the default event interaction step comprises communicating an event to the default login extension and to the registered login extension.

16. In a method for integrating additional functionality into a login system according to claim 15, further comprising communicating the event to the registered login extension as a function of a returned condition code from the default login extension.

17. In a method for integrating additional functionality into a login system according to claim 11, further comprising maintaining a list of pointers to structures, each structure having a pointer to a registered login extension, receiving an event, traversing the list of pointers to structures, and communicating the event to each registered login extension in the structures.

18. A login system capable of integrating additional functionality into the login system, comprising:

a plurality of events, each event corresponding to a predetermined activity in the login system process;

a first memory including an event manager operative to communicate a notification of an event to a plurality of login extensions;

a second memory including a default login extension operative to provide login functionality in response to the notification of the event;

a third memory including an authenticated registered login extension operative to receive the notification of the event and to provide additional functionality in response to the received notification,

a fourth memory including a list of registered login extensions.