# Patent

## Title
Automated password authentication

## Abstract

A system connected to an existing computer includes a unit for monitoring the screen and provides input, and a storage unit that stores data that pair screen buffer regions with authentication details. The system learns new pairs via user training and presents stored authentication details when the screen buffer matches a related stored region which is paired with a region of the screen.

## Background
The present application is a Continuation application of U.S. patent application Ser. No. 12/201,108, filed on Aug. 29, 2008 now U.S. Pat. No. 8,234,502, the entire content of which is incorporated herein by reference.


BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention generally relates to a method and system for automated password authentication, and more specifically to a method and system for automated password authentication for all websites and software, on a laptop, a desktop, or a mainframe accessed via a terminal emulator.
2. Description of the Related Art
One of the biggest problems for a user of a desktop, a laptop, or a main frame computer is authentication. Each system requires a password matching with a different criterion. Each password may expire at a different interval and therefore at a different time. Ironically, these protection measures start to weaken the protection because users have to find a way to remember these many different passwords.
The more naive and careless users may still use paper to write the passwords down. Some of the savvier users might use a software-based password vault, protecting all their passwords with a sign-on to the password vault. People start to resort to easily deduced passwords, even though they fit the security pattern. Examples are consecutive keys on a keyboard or a word on a poster/wall (e.g., in one call center many users had been using a heading of a billboard outside their office window).
Regardless of how well people deal with the situation, there will be few people who have not found this situation annoying, while using a computer.
SUMMARY OF THE INVENTION
In view of the foregoing and other exemplary problems, drawbacks, and disadvantages of the conventional methods and structures, an exemplary feature of the present invention is to provide a method for automated password authentication.
Inventions already exist to store passwords in a vault, protected by a single password. However, a need exists to capture a password and a user-id in the first place, and then to use this information in future logins. An exemplary purpose of this invention is to automate log-in processes without the interface requesting authentication being aware. Further, the user needs to take no action for this automated authentication to take place.
In an exemplary embodiment of the present invention, the invention software recognizes a user as the person at the machine and automatically and seamlessly logs into any authentication request that is presented to it for which the user has an account. The software uses authentication information (i.e., user-id and password), which are not stored on the machine. New authentications will be easily added with minimal configuration.
In sum, implementation of the system and method of the present invention ensures the following benefits:

    
    
        No more remembering passwords;
        Authentication is stronger because no one sees the user typing anything;
        Authentication is stronger because passwords do not need to be human-memorable;
        Systems and websites that the user is authenticating with do not need to be aware of the invention software (i.e., totally backwards compatible);
        Passwords are not stored anywhere on the computer; itself, and therefore less at risk from identity theft;
        Passwords are not stored on the computer, and therefore the user can use them on any computer; and
        Personal and business passwords are separated, and therefore one does not weaken the other.
    
    





BRIEF DESCRIPTION OF THE DRAWINGS
The foregoing and other exemplary purposes, aspects and advantages will be better understood from the following detailed description of an exemplary embodiment of the invention with reference to the drawings, in which:
FIG. 1 illustrates an overview of a system 100 for learning a new user name and password according to an exemplary aspect of the present invention;
FIG. 2 illustrates a system 200 for automatically entering a username and a password when a screen is encountered according to an exemplary aspect of the present invention;
FIG. 3 illustrates a flow chart 300 of a method for automated password authentication according to an exemplary aspect of the present invention;
FIG. 4 illustrates an exemplary hard are/information handling system 400 for incorporating the present invention therein; and
FIG. 5 illustrates a signal bearing medium 500 (e.g., storage medium) for storing steps of a program of a method according to the present invention.



DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS OF THE INVENTION
Referring now to the drawings, and more particularly to FIGS. 1-5, there are shown exemplary embodiments of the system and method according to the present invention.
FIG. 1 illustrates an exemplary embodiment of a system 100 for learning a new user name and password based on the present invention. In the system, a computer displays an authentication request (e.g., to a piece of software, a website, a remote system, etc.) (101). Then, a user gestures to a software that the system has asked for authentication (e.g., by pressing a predefined key) (102). The software asks the user to draw one or more rectangles on the screen to define pixels that show the computer is asking for a password (103). The user draws rectangles which are stored to a disk for pattern matching later (104). Finally, the software enters keystroke recording mode, and the user enters a user name and a password, which are captured by the software (105).
FIG. 2 illustrates an exemplary aspect of the present invention of a system 200 for automatically entering a username and a password when a screen is encountered. In the system, a computer displays authentication request (e.g., to a piece of software, a website, a remote system etc.) (201). Then, a software pattern matches and recognizes pieces of the screen bound by rectangles at time of learning (202). The system recognizes that a username and a password, recorded previously, need to be entered. Finally, the software automatically submits the username and password to the system (203).
FIG. 3 depicts a flow chart 300 of a method for automated password authentication according to an exemplary aspect of the present invention. As exemplary purpose of implementing the method is to trigger a sequence of one or more events, based on pattern matching of a signature matrix from a screen buffer with a matrix recorded at an earlier date.
The method 300 performs the automated password authentication by pattern matching regions of screen pixels against a repository of previously captured regions. When the screen regions match an existing region-set in the repository, a username and a password stored with those regions in the repository are submitted for authentication. The repository data includes bit map regions and associated user names and passwords that are from previous training by the user.
In step 301, a user inserts an article (e.g., a memory stick), containing an autorunnable application (the invention software), which triggers the software to startup. In step 302, the software challenges the user for a master password to access an encrypted database held on the memory stick.
Step 303 is an alternative flow to step 302, in which the memory stick is able to detect a radio frequency identification (RFID) device carried by the user which acts as an authorization token when the user is within a certain range of the memory stick.
In step 304, following a successful authorization of the user, the invention software runs as a background task. It checks if the user has removed the memory stick device. If it has, then the invention software is triggered to terminate in step 314, otherwise it moves onto step 305.
In step 305, the invention software checks if it has been triggered by the user, using a pre-defined key sequence or clicking an icon on the screen to notify the invention software that the user is about to enter a new password. If so, then the invention software moves to step 306, otherwise it moves onto step 309.
In step 306, the invention software prompts the user to highlight one or more rectangles around a text or an image which uniquely identifies a login panel (screen), and then captures the username and password as they are entered by the user. Once complete, the user continues with his work and the invention software returns to a background task in step 304.
In step 309, the invention software monitors the screen buffer looking for a matching signature based on the rectangles previously drawn by the user in step 306.
In step 313, the invention software checks if it has successfully found a matching signature in the screen buffer. If it has, then the invention software moves onto step 308, otherwise it returns to step 304.
In step 308, the invention software automatically enters the username and password. Typically, the user will continue working and the invention software returns to a background task in step 304.
Step 307 shows an alternative flow to step 305 when the processing required to constantly monitor the screen buffer is considered unacceptable. If the user has not triggered the invention software in step 305, using a pre-defined key sequence, then the invention software returns to step 304, bypassing the computationally expensive task 309. Otherwise, in this alternative flow, the invention software moves to step 307.
In step 307, the invention software detects if the user has triggered the invention software with the pre-defined key sequence to indicate a new login screen. If so, then the invention software moves to step 306, otherwise it moves to step 309.
Occasionally, following step 308, the user can be prompted that the password has expired, as shown in step 310.
In that case, in step 311, the user triggers the invention software by a pre-defined key sequence that the password just used is to be changed. As the user enters the new password, the invention software updates its record. Once complete, the user can continue working while the invention software returns to a background task in step 304.
Step 312 is an alternative to step 311, in which the user triggers the invention software by a predefined key sequence informing it that the password has expired and allowing the invention software to generate a new password for the login panel on behalf of the user. Once complete, the user can continue working, while the invention software returns to a background task in step 304.
Finally, when the user wants to finish with the computer, the user removes the memory stick in step 304, on which all the usernames, passwords, and unique signatures are stored. This triggers the software to terminate in step 314.
FIG. 4 illustrates a typical hardware configuration of an information handling/computer system for use with the invention and which preferably has at least one processor or central processing unit (CPU) 411.
The CPUs 411 are interconnected via a system bus 412 to a random access memory (RAM) 414, read only memory (ROM) 416, input/output (I/O) adapter 418 (for connecting peripheral devices such as disk units 421 and tape drives 440 to the bus 412), user interface adapter 422 (for connecting a keyboard 424, mouse 426, speaker 428, microphone 432, and/or other user interface device to the bus 412), a communication adapter 434 for connecting an information handling system to a data processing network, the Internet, an Intranet, a personal area network (PAN), etc., reader/scanner 441, and a display adapter 436 for connecting the bus 412 to a display device 438 and/or printer 440.
In addition to the hardware/software environment described above, a different aspect of the invention includes a computer implemented method for performing the above-described method. As an example, this method may be implemented in the particular environment discussed above.
Such a method may be implemented, for example, by operating a computer, as embodied by a digital data processing apparatus, to execute a sequence of machine readable instructions. These instructions may reside in various types of signal bearing storage media.
This signal bearing storage media may include, for example, a RAM contained within the CPU 411, as represented by the fast access storage for example. Alternatively, the instructions may be contained in another signal bearing media, such as a magnetic data storage diskette 500 (FIG. 5), directly or indirectly accessible by the CPU 411.
Whether contained in the diskette 500, the computer/CPU 411, or elsewhere, the instructions may be stored on a variety of machine readable data storage media, such as DASD storage (e.g., a conventional “hard drive” or a RAID array), magnetic tape, electronic read only memory (e.g., ROM, EPROM, or EEPROM), an optical storage device (e.g. CD ROM, WORM, DVD, digital optical tape, etc.), paper “punch” cards. In an illustrative embodiment of the invention, the machine readable instructions may comprise software object code, compiled from a language such as “C”, etc.
FIG. 5 illustrates a signal bearing medium 500 (e.g., storage medium such as floppy disk) and CD ROM 502 for storing steps of a program of a method according to the present invention.
It should be noted that other purposes, features, and aspects of the present invention will become apparent in the entire disclosure. Modifications may be done without departing from the gist and scope of the present invention as disclosed herein and claimed as appended herewith.
In addition, it should be noted that any combination of the disclosed and/or claimed elements, matters and/or items may fall under the modifications aforementioned.

## Claims

1. A system connected to an existing computer, said system comprising:
a unit for monitoring the screen and for providing an input;
a storage unit that stores data that pairs screen buffer regions with authentication details, wherein the system learns new pairs via user training and presents stored authentication details when the screen buffer regions match a related stored region which is paired with a region of the screen;
a unit that compares said screen buffer regions with a reference set to determine which of stored passwords need to be presented to the system by a pattern matching of regions of screen pixels against a repository of previously captured regions; and
a unit that is configured to check whether a user has triggered an autorunnable application by a pre-defined key sequence to notify the autorunnable application that the user is about to enter a new password,
wherein, if the user has triggered the autorunnable application, then the system is configure to:
prompt the user to highlight at least one rectangle around a text or an image which uniquely identifies a login panel;
capture a username and a password when entered by the user; and
return the autorunnable application to a background task,

wherein, if the user has not triggered the autorunnable application, then the method proceeds with monitoring a screen buffer for a matching signature based on the rectangle drawn by the user,
wherein, if the matching signature is not found, then the autorunnable application returns to a background task, and
wherein, if the matching signature is found, then the autorunnable application automatically enters a username and a password, and returns to a background task.

2. The system of claim 1, wherein said authentication details comprise the user name and the password.

3. The system of claim 2, wherein said system compares one of the screen buffer regions, as displayed to the user, with a set of stored regions.

4. The system of claim 3, wherein, after said system compares the screen buffer with the set of the stored regions, said system presents appropriate authentication details to simulate a manual user input.

5. The system of claim 4, wherein, after the system is enabled by the user, the system is configured to be instructed by the user to store a region such that the user provides login details.

6. A method of automated password authentication in a system, said method comprising:
pattern matching regions of screen pixels against a repository of previously captured regions;
submitting a username and a password stored with the regions of the screen pixels for authentication, said authentication comprising:
inserting a memory stick by a user;
challenging the user for a master password to access an encrypted database held on the memory stick;

running an autorunnable application as a background task following a successful authorization of the user;
checking whether the user has triggered the autorunnable application by a pre-defined key sequence to notify the autorunnable application that the user is about to enter a new password; and
comparing said regions of said screen pixels with a reference set to deter mine which of stored passwords need to be presented to the system,
wherein, if the user has triggered the autorunnable application, then the method proceeds with:
prompting the user to highlight at least one rectangle around a text or an image-which uniquely identifies a login panel;
capturing a username and a password when entered by the user; and
returning the autorunnable application to a background task,

wherein, if the user has not triggered the autorunnable application, then the method proceeds with monitoring a screen buffer for a matching signature based on the rectangle drawn by the user,
wherein, if the matching signature is not found, then the autorunnable application returns to a background task, and
wherein, if the matching signature is found, then the autorunnable application automatically enters a username and a password, and returns to a background task.

7. The method of claim 6, further comprising:
terminating the autorunnable application by removing the memory stick.

8. The method of claim 7, wherein the repository comprises bit map regions, and associated user names and passwords from a previous training by the user.