This application is based upon and claims the benefit of priority from Japanese Patent Application No. 2011-135066, filed on Jun. 17, 2011, the entire contents of which are incorporated herein by reference.
Embodiments described herein relate generally to an information processor, an information processing method, and a computer program product.
Generally, in application programs, computer systems, network systems, and the like, user authentication is performed to check whether the user who is about to use them is a valid user.
Although there have been proposed a variety of user authentication technologies, the combination of a user ID and a password corresponding thereto is the most common method of authentication. To further improve the security, there has been proposed a technology in which the location of objects, such as operation buttons, on the authentication screen is changed each time.
For the user to be authenticated, if the location of objects on the authentication screen is changed each time, he/she has to search for a desired button each time. This is troublesome and inconvenient for the user.
A general architecture that implements the various features of the invention will now be described with reference to the drawings. The drawings and the associated descriptions are provided to illustrate embodiments of the invention and not to limit the scope of the invention.
In general, according to one embodiment, an information processor comprises a display module and an operation module. The display module is configured to display a plurality of display objects each at a predetermined display position. The display objects are selected in advance by a user from a plurality of objects and comprises authentication objects. The operation module is configured to be used for operation to select the authentication objects in a predetermined order upon user authentication.
In the first embodiment, an example will be explained in which images of playing cards (images of a total of 52 cards including 13 ranks of each of four suits, clubs, diamonds, hearts, and spades) are displayed on the display screen of the touch panel display 16 as display object. More specifically, if a user selects cards selected in advance by himself/herself from the cards displayed on a user authentication screen (login screen) in the order specified in advance by himself/herself, the user authentication is determined to be successful.
When the user starts up the PC 10 and an initial-setup application is activated, all or part of selectable cards (unselected display objects) are displayed on the display screen of the display 17. In the case where part of selectable cards are displayed, there may be provided a button to display other cards that are not displayed. In the following, for the sake of simplicity, the case will be described where all selectable cards are displayed on the display screen of the display 17.
The cards (display objects) used in the user authentication screen includes a first specified number of cards (in the first embodiment, five cards) as authentication objects and a second specified number of cards (in the first embodiment, three cards) as non-authentication objects that are displayed so that others cannot easily find out the authentication objects. The authentication objects and the non-authentication objects are collectively referred to as display objects.
In the first embodiment, display objects are selected in such a manner that, for example, authentication objects are selected first and then non-authentication objects are selected.
First, the MPU 11 displays all cards that can be selected as authentication objects (unselected display objects) on the display screen of the display 17 that constitutes the touch panel display 16 to prompt the user to select authentication objects (S11).
With this, the user selects any of the cards through the touch panel 18 that constitutes the touch panel display 16 (S12). The MPU 11 indicates that the cards are selected as authentication objects (S13). More specifically, for example, the images of the cards selected as authentication objects are each displayed as being surrounded with a frame or highlighted with a number nearby corresponding to the order in which they are selected. Alternatively, a new window is opened to display the images of the selected cards in the order in which they are selected to clearly indicate the selected objects.
The MPU 11 then determines whether the number of the authentication objects currently selected reaches the first specified number (S14). If the number of the authentication objects currently selected reaches the first specified number (Yes at S14), the MPU 11 associates the authentication objects currently selected with the user as well as registering and storing them in the external storage device 14 together with information on the selection order in which they are selected (S16).
If the number of the authentication objects currently selected is yet to reach the first specified number (No at S14), the MPU 11 determines whether the user finishes to select authentication objects (S15).
If the user has not yet finished to select authentication objects (No at S15), the process returns to S11 to repeat the same process. In this case, for example, if two authentication objects have already been selected, at S11, remaining 50 cards (52−2 cards) are displayed as all cards that can be selected as authentication objects (unselected display objects).
On the other hand, if the user has finished to select authentication objects (Yes at S15), the MPU 11 stores and registers information specifying all the authentication objects selected by the user and the information on their selection order in the external storage device 14 in association with the user ID (S16).
Next, the MPU 11 displays all cards that can be selected as non-authentication objects (unselected display objects) on the display screen of the display 17 that constitutes the touch panel display 16 to prompt the user to select non-authentication objects (S17). For example, if five cards have already been selected as authentication objects, the MPU 11 displays the remaining 47 cards.
With this, the user selects any of the cards through the touch panel 18 that constitutes the touch panel display 16 (S18). The MPU 11 indicates that the cards are selected as non-authentication objects (S19). More specifically, for example, the images of the cards selected as non-authentication objects are each displayed as being surrounded with a frame of a different color from that of authentication objects or displayed blinking. Alternatively, a new window is opened to display the images of the selected cards together with the selected authentication objects to clearly indicate the selected objects.
The MPU 11 then determines whether the number of the non-authentication objects currently selected reaches the second specified number (S20). If the number of the non-authentication objects currently selected reaches the second specified number (Yes at S20), the MPU 11 registers and stores the non-authentication objects currently selected in the external storage device 14 in association with the user and the authentication objects corresponding to the user (S22).
If the number of the non-authentication objects currently selected is yet to reach the second specified number (No at S20), the MPU 11 determines whether the user finishes to select non-authentication objects (S21).
If the user has not yet finished to select non-authentication objects (No at S21), the process returns to S17 to repeat the same process. In this case, for example, if two non-authentication objects have already been selected, at S17, remaining 45 cards (52−5−2 cards) are displayed as all cards that can be selected as non-authentication objects (unselected display objects).
On the other hand, if the user has finished to select non-authentication objects (Yes at S21), the MPU 11 stores and registers information specifying all the non-authentication objects selected by the user in the external storage device 14 in association with the user ID (S22).
The authentication object specifying data 32 includes n pieces of authentication object data 34-1 to 34-n (in the first embodiment, n is a natural number not larger than 5, i.e., the maximum number of n=5). Each authentication object data 34-x (x: a natural number equal to or less than n) includes object specifying data 35 and location data 36. The object specifying data 35 specifies an authentication object. The location data 36 specifies the location (display position) of the authentication object specified by the object specifying data 35 on the user authentication screen (login screen).
The non-authentication object specifying data 33 includes m pieces of non-authentication object data 37-1 to 37-m (in the first embodiment, m is a natural number not larger than 3, i.e., the maximum number of m=3). Each non-authentication object data 37-y (y: a natural number equal to or less than m) includes object specifying data 38 and location data 39. The object specifying data 38 specifies a non-authentication object. The location data 39 specifies the location (display position) of the non-authentication object specified by the object specifying data 38 on the user authentication screen (login screen).
The user authentication screen will be described.
The login user selection screen 50 is displayed on the display screen 16A of the touch panel display 16. The login user selection screen 50 comprises a message area 51, a first login user selection button 52A, a second login user selection button 52B, and a third login user selection button 52C. Displayed in the message area 51 is a message that prompts the user to select a login user. The first login user selection button 52A is used to specify a user A as a login user. The second login user selection button 52B is used to specify a user B as a login user. The third login user selection button 52C is used to specify a user C as a login user. While
By touching any one of the first to third login user selection buttons 52A to 52C, the user selects and specifies a login user through the touch panel 18 (S32). The MPU 11 specifies a login user selection button 52Z (Z: A to C) touched by the user, and reads the authentication data 30 (see
Further, “4 of spades” card, “8 of clubs” card, “10 of hearts” card, and “King of diamonds” card are displayed as display objects in the display areas P5, P6, P7, and P8, respectively. Displayed in the operation area OP is a selection button “others” to allow the user to select another authentication method (e.g., common password authentication, etc.).
In the following, it is assumed that, among the display objects, five cards “2 of spades”, “3 of diamonds”, “4 of spades”, “10 of hearts”, and “King of diamonds” are set as authentication objects, while three cards “Ace of hearts”, “3 of clubs”, and “8 of clubs” are set as non-authentication objects.
In the valid selection order of the authentication objects for the valid user, “3 of diamonds”, “4 of spades”, “2 of spades”, “King of diamonds”, and “10 of hearts” are set in this order. This order may be the ascending order of the value of x of the authentication object data 34-x (x: a natural number equal to or less than n). That is, in the above case, the authentication object data are stored in such a manner that the data 34-1 corresponds to “3 of diamonds”, the data 34-2 corresponds to “4 of spades”, the data 34-3 corresponds to “2 of spades”, the data 34-4 corresponds to “King of diamonds”, and the data 34-5 corresponds to “10 of hearts”. If the user selects any of the display objects by touching the touch panel 18 (S35), the MPU 11 determines whether the selection is valid (S36).
More specifically, if the user touches the “3 of diamonds” card first, the selection is determined to be valid. If the user touches another card than “3 of diamonds”, the selection is determined to be invalid. Having determined that the selection is invalid (No at S36), the MPU 11 performs error process such as to notify the user that user authentication fails and login is not allowed, or, if user authentication fails successively a plurality of times, to notify the user that login is not allowed on that day (S39).
On the other hand, having determined that the selection is valid (Yes at S36), the MPU 11 determines whether the user finishes to select all the display objects (S37). If all the display objects have not yet been selected (No at S37), the process returns to S35 to repeat the above process for the next selection.
Having determined that all the display objects have been selected, i.e., the cards are touched in the order of “3 of diamonds”, “4 of spades”, “2 of spades”, “King of diamonds”, and “10 of hearts” (Yes at S37), the MPU 11 performs login permission process to notify the user that login is allowed and to create an operation environment corresponding to the user (S38).
As described above, according to the first embodiment, each user can arbitrarily select playing cards (authentication objects and non-authentication objects) used for user authentication. Thus, user authentication process can be reliably retained. Besides, the location of playing cards (authentication objects and non-authentication objects) used for user authentication is unchanged on the user authentication screen 40, which further facilitates to retain the authentication process. This improves the convenience for the user.
In the first embodiment, 52 playing cards are used as authentication objects. According to a second embodiment, for example, four suits (clubs, diamonds, hearts, and spades) and 13 ranks (Ace, 2 to 10, Jack, Queen, and King) are considered as different objects, and only the 13 ranks are actually used as authentication objects in user authentication process.
In this case, the suits of the cards have no meaning as authentication objects. Thus, by setting the suits at random, a different looking user authentication screen can be displayed each time. This can improve the security.
More specifically, if the ranks “Ace”, “King”, “7”, “3”, and “Queen” correspond to authentication objects, while the ranks “Jack”, “4”, and “9” correspond to non-authentication objects, “Ace of hearts”, “King of clubs”, “7 of diamonds”, “3 of hearts”, and “Queen of spades” are displayed as authentication objects and “Jack of diamonds”, “4 of clubs”, and “9 of spades” are displayed as non-authentication objects on the authentication screen for a certain user on one occasion. On another occasion, “Ace of clubs”, “King of clubs”, “7 of hearts”, “3 of spades”, and “Queen of diamonds” are displayed as authentication objects and “Jack of hearts”, “4 of diamonds”, and “9 of clubs” are displayed as non-authentication objects on the authentication screen for the same user.
As a result, differently from conventional authentication using a combination of numbers as an authentication key, the user authentication screen is not the same every time and can be displayed differently. This can further ensure the security.
As described above, according to the second embodiment, the security in effect can be improved without reducing the operability of the user authentication screen for the user.
In the above embodiments, the information processor is described by way of example as a stand-alone PC. The information processor may be a PC connected to a server using a browser in a cloud computing system.
In effect, the PCs 73-A to 73-C provide the same function as the touch panel display 16 described in the first embodiment, the authentication server 71 provides the same function as the MPU 11, the ROM 12, and the RAM 13, and the Internet 72 as a communication network provides the same function as the bus 19.
Referring back to
The touch panel display 95 comprises a display 96 and a touch panel 97. The display 96 is a display module comprising, for example, an LCD or an EL display. The touch panel 97 is an operation module comprising, for example, a resistive touch panel or a capacitance touch panel.
Referring again to
In this state, as will be described below, the user selects a predetermined number of cards (in the following description, eight cards) used in the user authentication screen.
First, the MPU 81 of the authentication server 71 displays all cards that can be selected as authentication objects (unselected display objects) on the display screen of the display 96 that constitutes the touch panel display 95 of the PC 73-A to prompt the user to select authentication objects (S11).
With this, the user selects any of the cards through the touch panel 97 that constitutes the touch panel display 95 (S12). The MPU 81 of the authentication server 71 indicates that the cards are selected as authentication objects on the display 96 (S13).
The MPU 81 of the authentication server 71 then determines whether the number of the authentication objects currently selected reaches the first specified number (S14). If the number of the authentication objects currently selected reaches the first specified number (Yes at S14), the MPU 81 associates the authentication objects currently selected with the user as well as registering and storing them in the external storage device 84 together with information on the selection order in which they are selected (S16).
If the number of the authentication objects currently selected is yet to reach the first specified number (No at S14), the MPU 81 of the authentication server 71 determines whether the user finishes to select authentication objects (S15).
If the user has not yet finished to select authentication objects (No at S15), the process returns to S11 to repeat the same process. In this case, for example, if two authentication objects have already been selected, at S11, remaining 50 cards (52−2 cards) are displayed as all cards that can be selected as authentication objects (unselected display objects).
On the other hand, if the user has finished to select authentication objects (Yes at S15), the MPU 81 stores and registers information specifying all the authentication objects selected by the user and the information on their selection order in the external storage device 84 in association with the user ID (S16).
Next, the MPU 81 of the authentication server 71 displays all cards that can be selected as non-authentication objects (unselected display objects) on the display screen of the display 96 that constitutes the touch panel display 95 to prompt the user to select non-authentication objects (S17).
With this, the user selects any of the cards through the touch panel 97 that constitutes the touch panel display 95 (S18). The MPU 81 of the authentication server 71 indicates that the cards are selected as non-authentication objects on the display 96 (S19).
The MPU 81 of the authentication server 71 then determines whether the number of the non-authentication objects currently selected reaches the second specified number (S20). If the number of the non-authentication objects currently selected reaches the second specified number (Yes at S20), the MPU 81 registers and stores the non-authentication objects currently selected in the external storage device 84 in association with the user and the authentication objects corresponding to the user (S22).
If the number of the non-authentication objects currently selected is yet to reach the second specified number (No at S20), the MPU 81 of the authentication server 71 determines whether the user provides input to finish selecting non-authentication objects via the touch panel 97 that constitutes the touch panel display 95 (S21).
If the user has not yet finished to select non-authentication objects (No at S21), the process returns to S17 to repeat the same process.
On the other hand, if the user has finished to select non-authentication objects (Yes at S21), the MPU 81 of the authentication server 71 stores and registers information specifying all the non-authentication objects selected by the user in the external storage device 84 in association with the user ID (S22).
In the following, referring again to
In response to a login request from the PC 73-A, the MPU 81 of the authentication server 71 displays the login user selection screen on the display 96 (S31).
By touching any one of the first to third login user selection buttons 52A to 52C on the touch panel display 95, the user selects and specifies a login user through the touch panel 97 (S32). The MPU 81 of the authentication server 71 specifies the login user selection button 52Z (Z: A to C) touched by the user, and reads the authentication data 30 (see
The display 96 of the PC 73-A displays the authentication object selection screen 60 as illustrated in
Having determined that the selection is invalid (No at S36), the MPU 81 of the authentication server 71 performs error process such as to notify the user that user authentication fails and login is not allowed, or, if user authentication fails successively a plurality of times, to notify the user that login is not allowed on that day (S39).
On the other hand, having determined that the selection is valid (Yes at S36), the MPU 81 determines whether the user finishes to select all the display objects (S37). If all the display objects have not yet been selected on the PC 73-A (No at S37), the process returns to S35 to repeat the above process for the next selection.
Having determined that all the display objects have been selected (Yes at S37), the MPU 81 of the authentication server 71 performs login permission process to notify the user that login is allowed and to create an operation environment corresponding to the user (S38). After that, the authentication server 71 provides its content to the PC 73-A regarding the user as a valid user.
As described above, according to the third embodiment, even on a PC that does not operate standalone such as those in a cloud computing system, each user can arbitrarily select playing cards (authentication objects and non-authentication objects) used for user authentication. Thus, user authentication process can be reliably retained. Besides, the location of playing cards (authentication objects and non-authentication objects) used for user authentication is unchanged on the user authentication screen 40, which further facilitates to retain the authentication process. This improves the convenience for the user.
According to the embodiments described above, substantially the same user authentication screen is displayed for each user each time they log in. This makes authentication easier. Thus, it is possible to improve the convenience for the user as well as to improve the security.
Although display objects are described herein byway of example as images of playing cards, they may be, for example, images of mahjong tiles, images of other playing cards, or the like.
While the information processor is described herein by way of example as a PC, it may be, for example, a portable information processor provided with a touch panel display such as a smartphone, a bank's automated teller machine (ATM), or the like.
Further, while the above embodiments are described herein byway of example as being applied to user authentication, they may be applied to any other types of authentication.
The control program executed on the information processor of the embodiments may be stored in a computer connected via a network such as the Internet so that it can be downloaded therefrom via the network. The control program may also be provided or distributed via a network such as the Internet. The control program may also be provided as being stored in advance in a ROM or the like.
Further, the control program may be provided as being stored in a computer-readable storage medium, such as a compact disc-read only memory (CD-ROM), a flexible disk (FD), a compact disc recordable (CD-R), and a digital versatile disc (DVD), as a file in an installable or executable format.
The various modules of the systems described herein can be implemented as software applications, hardware and/or software modules, or components on one or more computers, such as servers. While the various modules are illustrated separately, they may share some or all of the same underlying logic or code.
While certain embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the inventions. Indeed, the novel embodiments described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the embodiments described herein may be made without departing from the spirit of the inventions. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of the inventions.
Number | Date | Country | Kind |
---|---|---|---|
2011-135066 | Jun 2011 | JP | national |
Number | Name | Date | Kind |
---|---|---|---|
5559961 | Blonder | Sep 1996 | A |
6980081 | Anderson | Dec 2005 | B2 |
7266693 | Potter et al. | Sep 2007 | B1 |
7574739 | Shirakawa | Aug 2009 | B2 |
7841000 | Kawano et al. | Nov 2010 | B2 |
7873995 | Bagga et al. | Jan 2011 | B2 |
7953983 | Holt et al. | May 2011 | B2 |
7992202 | Won et al. | Aug 2011 | B2 |
8117458 | Osborn et al. | Feb 2012 | B2 |
8145912 | McLean | Mar 2012 | B2 |
8214892 | Cohen et al. | Jul 2012 | B2 |
8281147 | Florencio et al. | Oct 2012 | B2 |
8336086 | Seo | Dec 2012 | B2 |
8387126 | Di Crescenzo | Feb 2013 | B2 |
8464324 | Mechaley, Jr. | Jun 2013 | B2 |
20030210127 | Anderson | Nov 2003 | A1 |
20040030934 | Mizoguchi et al. | Feb 2004 | A1 |
20040172564 | Federova et al. | Sep 2004 | A1 |
20040230843 | Jansen | Nov 2004 | A1 |
20040250138 | Schneider | Dec 2004 | A1 |
20050071686 | Bagga et al. | Mar 2005 | A1 |
20050144484 | Wakayama | Jun 2005 | A1 |
20060174339 | Tao | Aug 2006 | A1 |
20060206717 | Holt et al. | Sep 2006 | A1 |
20060206919 | Montgomery et al. | Sep 2006 | A1 |
20060248344 | Yang | Nov 2006 | A1 |
20070130618 | Chen | Jun 2007 | A1 |
20070226784 | Ueda et al. | Sep 2007 | A1 |
20070234063 | Ueda et al. | Oct 2007 | A1 |
20070266428 | Downes et al. | Nov 2007 | A1 |
20070277224 | Osborn et al. | Nov 2007 | A1 |
20080222417 | Downes et al. | Sep 2008 | A1 |
20080244700 | Osborn et al. | Oct 2008 | A1 |
20090172810 | Won et al. | Jul 2009 | A1 |
20090178136 | Ruddy | Jul 2009 | A1 |
20090300732 | Hwang et al. | Dec 2009 | A1 |
20100169958 | Werner et al. | Jul 2010 | A1 |
20100287382 | Gyorffy et al. | Nov 2010 | A1 |
20100322485 | Riddiford | Dec 2010 | A1 |
20110016520 | Cohen et al. | Jan 2011 | A1 |
20110053685 | Kim et al. | Mar 2011 | A1 |
20110096997 | Marciszko et al. | Apr 2011 | A1 |
20110154444 | Sriraghavan et al. | Jun 2011 | A1 |
20110202982 | Alexander et al. | Aug 2011 | A1 |
20110321125 | Kyohgoku et al. | Dec 2011 | A1 |
20120036573 | Yang | Feb 2012 | A1 |
20120159614 | Griffin et al. | Jun 2012 | A1 |
20120159615 | Griffin et al. | Jun 2012 | A1 |
20120159616 | Griffin et al. | Jun 2012 | A1 |
20120167199 | Riddiford | Jun 2012 | A1 |
20120272311 | Althammer et al. | Oct 2012 | A1 |
20120291120 | Griffin | Nov 2012 | A1 |
20130036461 | Lowry | Feb 2013 | A1 |
Number | Date | Country |
---|---|---|
10-097500 | Apr 1998 | JP |
2001-282738 | Oct 2001 | JP |
2002-297546 | Oct 2002 | JP |
2005-044121 | Feb 2005 | JP |
2008-242589 | Oct 2008 | JP |
WO 2010-092922 | Aug 2010 | WO |
Entry |
---|
Japanese Patent Application No. 2011-135066; Notification of Reasons for Refusal; Mailed Aug. 7, 2012 (English translation). |
Satoshi Yoneda, [Security] Easy and Quick! “Single-point Security” Products to Prevent Information Leakage, COMPUTERWORLD Get Technology Right, vol. 2, No. 10, Japan, IDG Japan, Inc., Oct. 1, 2005, pp. 88-95. |
Number | Date | Country | |
---|---|---|---|
20120324570 A1 | Dec 2012 | US |