JP2002202954A - User authentication system, user authentication method and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To realize a member authentication and retrieval of personal information giving flexibility to every company and every service content in a user authentication system, a user authentication method and a recording medium for managing the authentication of a user using a service. SOLUTION: This user authentication system, user authentication method and recording medium comprise an authentication table for storing the authentication information for a user; a service identification table for storing a service identifier for identifying a service and an authentication table identifier for identifying the authentication table for storing the authentication information related to the user of the service; and an authentication means for specifying the authentication table corresponding to the using service in reference to the service identification table when receiving an authentication request from the user, and performing the authentication of the user in reference to the authentication table.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a user authentication system, a user authentication method, and a recording medium for managing authentication information of a user who uses a service.

[0002]

2. Description of the Related Art Conventionally, registration and authentication of users on the Internet are provided by different companies and services, and therefore, user management (authentication ID, e-mail address, password, etc.) corresponding to each service for each company. User management).

[0003]

For this reason, it is necessary to create a user management system individually according to different companies and different service contents. Even if there is a similar user management system, other users can be diverted. No versatility,
There is a problem that the creation work is difficult and a user management system that can respond quickly cannot be constructed.

[0004] The present invention solves these problems,
An object of the present invention is to realize user authentication and retrieval of personal information with versatility for each company and each service content.

[0005]

Means for solving the problem will be described with reference to FIG. In FIG. 1, a member management system 1 manages user authentication information for different services or different providers, and the like.
Here, it is configured by the authentication means 6, the member DB 7, and the like.

[0006] The authentication means 6 performs user authentication and searches for user information (described later with reference to FIG. 2 and the like). The member DB 7 registers and manages information for user authentication and user information.
The first to fourth tables are provided.

Next, the operation will be described. A first table (homepage identification table 8) for registering an authentication table ID in association with an identification code of a homepage accessed by a user in the member management system 1, and an authentication table ID registered in the first table. A second table (e.g., mail address table 9 and authentication ID table 10) for registering user authentication information, and corresponding user authentication information or corresponding authentication information on the second table to the first table. Third table for registering user information in association with the corresponding identification code (basic item table 11)
The authentication means 6 searches the first table, the second table, and the third table to authenticate the user or to authenticate the user and the information thereof.

At this time, a fourth table for registering the user's extended information in association with the authentication information of the second table or the authentication information of the second table and the extended item table ID registered in the first table. Is provided.

Further, the first and third tables are common to all users, and the second table and the fourth table are provided for each service or each provider. Therefore, it is possible to perform user authentication and personal information search with versatility for each company and each service content.

[0010]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, an embodiment and operation of the present invention will be described in detail with reference to FIGS. In the following, members of a company or members who have registered as members to receive services will be described below. However, the present invention is not limited to such members, and general users (users registered with authentication information) Similarly, the invention is applicable.

FIG. 1 shows a system configuration diagram of the present invention.
In FIG. 1, a member management system 1 manages member authentication information for different services or different providers (enterprises), and includes a server 2 and a member DB 7 in this case.

The server 2 performs member authentication and authentication and member information search.
And so on. The processing device 4 performs various processes in accordance with a program, and here includes a registration unit 5, an authentication unit 6, and the like.

The registration unit 5 registers information (member name, code, e-mail ID, password, etc.) necessary for member authentication and member information (member name, etc.) in the member DB 7. is there.

The authentication means 6 performs member authentication, member authentication, and information retrieval (described later with reference to FIG. 2 and the like). The member DB 7 registers information (member code, e-mail address, password, etc.) necessary for member authentication and member information (name, address, etc.). It comprises a table 9, an authentication ID table 10, a basic item table 11, an extended item table 12, and the like.

[0015] Homepage table (first table)
Reference numeral 8 denotes information in which information (homepage identification code, table name, extension item table name, etc.) is registered in association with the URL of the homepage accessed by the member.

The mail address table (second table) 9 is for registering information for performing member authentication. In this case, the member ID, mail address, password and the like are registered.

Authentication ID table (second table) 10
Is registered information for performing member authentication. In this example, the member ID, authentication ID, and password are registered.

Basic item table (third table) 11
Is information that is registered in common for all members.
Information such as a homepage identification code, a member ID, a name, an address, a telephone number, a date of birth, and gender is registered.

Extended item a table (fourth table) 1
2. An extended item b table (fourth table) 12 is provided for each service or provider, and the basic item table 1
The extension information of the member who cannot be registered in No. 1 is registered.

The service 21 for company A members is an image of providing services to members of company A, and includes a homepage screen 22 and a member registration screen 2.
3 and the like.

The homepage screen 22 is a homepage screen for providing services to members of the company A. The member registration screen 23 is a member registration screen for becoming a member of the company.

Authentication ID: The mail address 24 is the company A
The e-mail address (and password) is used as the authentication for providing services to members of the member management system 1
2 shows a state of transmission and authentication through the Internet 41.

Similarly, the service 31 for company B members
This is a visual representation of providing services to members of the company B, and includes a homepage screen 32, a member registration screen 33, and the like.

The homepage screen 32 is a homepage screen for providing services to members of the company A. The member registration screen 33 is a member registration screen for becoming a member of the company.

Authentication ID: Unique system authentication ID 34 is used as authentication for providing services to members of company B.
A state in which an authentication ID (and password) of a unique system is transmitted to the member management system 1 via the Internet 41 for authentication is shown.

Next, the operation of the configuration of FIG. 1 will be described in detail according to the order of the flowchart of FIG. FIG. 2 shows an operation explanation flowchart (authentication) of the present invention.

In FIG. 2, S1 inputs a URL. In this method, the member inputs the URL of the homepage to receive the service on the browser. S2 connects / displays to the Web server (public homepage). this is,
The user connects to the home page of the URL entered in S1 via the Internet, downloads the data (HTML document) of the home page, and displays it on the member's screen. For example, a home page screen shown in FIG.

In step S3, an entrance only for the member is selected. In this case, a member's site is selected (clicked) on the homepage screen of FIG. In step S4, an authentication screen is displayed. In response to the selection of the entrance only by the member in S3, an authentication screen, for example, an authentication screen of FIG. 5A described later is downloaded and displayed.

In step S5, an ID / password is input. For example, on the authentication screen of FIG. 5A, the authentication ID “abc0
001 ”and the password“ a9871 ”(note that
On the actual screen, the password is displayed on the screen as “****
* ”To prevent plagiarism).

In step S6, the URL information, ID and password are taken as authentication information. In step S7, homepage authentication is performed. This is performed by the following S11 to S20.

Step S11 refers to the homepage identification table 8 of the member DB. A step S12 decides whether or not the homepage identification code is "a". This is, for example, the homepage identification table 8 shown in FIG. 3A described later in the URL of the homepage accessed by the member at the URL input in S1.
To determine whether the home page identification code of the entry for which the URL is set is “a”. In the case of YES, the process proceeds to S13. On the other hand, in the case of NO in S12,
Proceed to S15.

In S13, since the homepage identification code is determined to be "a" in YES in S12, the authentication ID table 10 shown in FIG. 3C determined by the homepage identification code is referred to, for example.

In step S14, an ID check is performed. this is,
The ID input in S5 (here, the authentication I in FIG. 5)
It is checked whether D) is registered in the authentication ID table 10 of FIG. In the case of YES, it is determined that the user has been registered, and the process proceeds to the next password check in S18. On the other hand, in the case of NO in S14, it is determined that it has not been registered, so ERR (error) is set as the authentication check result in S20, and the process proceeds to S8.

In step S18, a password check is performed. This is because the ID check is OK in S17,
It is determined whether the password corresponding to the ID matches.
If YES, OK is determined as the authentication result in S19, and S8
Proceed to. On the other hand, if NO in S18, ER
R (error) is set as the authentication result, and the process proceeds to S8.

In step S8, the result of the authentication check is determined. E
In the case of RR, the process returns to S4 and repeats. In the case of OK, reference to the member site is permitted. As described above, members
Enter the RL to access and download the homepage, display the homepage screen, select the entrance where only members can enter, display the member registration screen, enter the ID (authentication ID, e-mail address), and password, and enter the homepage. Referring to the homepage identification table 8 in FIG. 3A based on the URL of the authentication ID table 1 shown in FIG.
0 or by referring to the mail address table 9 or the like, and authenticating based on the input ID (authentication ID, e-mail address) and password, and permitting participation in the member site when OK, so that the provider ( It is possible to perform member authentication with versatility for each (company) and each service.

FIG. 3 shows an example of a member DB according to the present invention. FIG.
(A) shows an example of a homepage identification table (first table). This homepage identification table 8
The following information shown in the figure is registered in association with each company (provider).

URL (homepage URL): homepage identification code: authentication table name: extended item table name: other: Here, the URL is a URL for each company (provider), and the homepage identification code is a company. (Provider) homepage identification code, the authentication table name is the authentication table name used to authenticate the member of the company, and the extension item table name is the table name that stores the extended information of the member of the company. It is.

As described above, by registering and referencing the homepage identification code, the authentication table name, and the extension item table name in association with the URL of the homepage, the authentication table (for each company (provider)) and each service is different. The mail address table 9 or the authentication ID table 10) and the member information which cannot be included in the basic item table 11 common to all members are stored in the individual extended item table 12
It can be registered and referred to, and can be realized by a general-purpose mechanism even if the company and service are different.

FIG. 3B shows an example of a mail address table (second table). The mail address table 9 is referred to when the authentication ID table name is "mail address table" in the case of a member of the defg company in the homepage identification table 8 of FIG. Email address and password).

FIG. 3C shows an authentication ID table (second
Table 2) shows an example. This authentication ID table 10
Is ab in the homepage identification table 8 of FIG.
In the case of a member of company c, the authentication ID table name is "authentication ID
Refer to the table when it is "
bc company-specific authentication ID and password).

Based on the mail address table 9 or the authentication ID table 10 shown in FIGS. 3B and 3C, a member authentication (mail address / authentication ID) is generally performed using an authentication table for each company. , Password authentication)
Can be performed.

FIG. 3D shows a basic item table (third item table).
Table 2) shows an example. This basic item table 11
Are registered in such a manner that the following items common to all members shown below can be distinguished by the homepage identification code.

・ Homepage identification code: ・ ID (member ID): ・ Name: ・ Address: ・ Phone number: ・ Date of birth: ・ Gender: ・ Others: FIG. 4). The extension item a table 12 is a table in which the following items shown in the drawing are registered in association with the homepage identification code a, and cannot be stored in the basic item table 11 of FIG. Is provided individually for each company or service and can be registered and referenced.

ID (member ID): Hobbies: Address: Family: Number of children: Other: FIG. 3E shows an example of the extended item b table (fourth table). The extension item b table 12 is a table in which the following items shown in the figure are registered in association with the homepage identification code b, and are items that cannot be stored in the basic item table 11 of FIG. Is provided individually for each company or service and can be registered and referenced.

ID (Member ID): Purchase paper: Reading: Writer: Occupation: Job title: Other: FIG. 4 shows an example of a public homepage of each company of the present invention.

FIG. 4A shows an example of a public homepage of abc. This is ab in FIG. 3A described above.
An example of the public homepage (URL: www.abc.com) of Company c is shown. The "members site" part of this public homepage is the entrance where only members can enter,
When this is selected (S3 in FIG. 2 described above), the screen transits to the “authentication screen” on the abc company homepage in FIG. 5A (S4 in FIG. 3 described above).

FIG. 4B shows an example of a public homepage of defg. This corresponds to d of FIG.
efg's public homepage '(URL: www.defg.c
o.jp). The "members site" part of this public homepage is the entrance where only members can enter, and if this is selected (S3 in FIG. 2 described above), the "authentication" of the defg company homepage in FIG. Screen ”(S4 in FIG. 3 described above).

FIG. 5 shows an example of an authentication screen of each company according to the present invention. FIG. 5A shows an example of an authentication screen of the abc company homepage. In the part on this authentication screen, here,
Enter the following as shown.

Authentication ID: abc0001 Password: a9871 Here, the name of the authentication table of the entry matching the URL of the homepage page in the homepage identification table 8 shown in FIG. ID table ", and the authentication is set in the" authentication table "of FIG. 3 (c). Therefore, on this authentication screen," authentication ID "(abc's unique A system authentication ID) and a "password" are input. In addition, in order to avoid plagiarism when actually inputting and displaying the echo, "********
* ”Is displayed.

FIG. 5B shows an example of an authentication screen of the defg company homepage. In this example, the following shown in the figure is entered in the portion 'on the authentication screen. -E-mail address: yamada @ aaa. com • Password: 1234 Here, the defg company has entered the URL of the homepage page in the homepage identification table 8 in FIG.
Is set as the "mail address table" of the entry that matches, and the authentication is set to be performed in the "mail address table" of FIG. 3B. In addition, it is made to input 'email address' and 'password'. Note that the password is actually displayed as "****" to avoid plagiarism when it is input and echo-displayed.

Fig. 6 shows an example of a member site page of each company of the present invention "a homepage that only members can put in." Fig. 6 (a) shows an example of a homepage of a site for members of abc company. The user inputs the authentication ID and the password on the authentication screen shown in FIG. 5A, and matches the authentication ID and password in the authentication ID table 10 in the authentication ID table 10 shown in FIG. (S11 of FIG. 2 already described)
From S19 to S19), and is the displayed homepage.

FIG. 6B shows an example of a homepage of a site for members of defg. This is the same as FIG.
(B), enter the e-mail address and password on the authentication screen, and in the e-mail address table 9 of FIG. 2 from S11 to S19), which is the displayed homepage.

Next, a new member registration will be described in detail with reference to FIGS. 7 and 8. FIG. FIG. 7 shows an example of a public homepage of each company of the present invention.

FIG. 7A shows an example of an abc company homepage. On the abc company homepage, select the part of the application for membership (the Internet general member selects the entrance of the membership application procedure). When the entrance is selected, the application screen of FIG. 8A is downloaded and displayed on the member screen.

FIG. 7B shows an example of a defg company homepage. On the defg company's homepage, select the part of the application for membership (the Internet general member selects the entrance of the application procedure for membership). When "entrance" is selected, the application screen of FIG. 8B is downloaded and displayed on the member screen.

FIG. 8 shows an example of a member application screen of each company according to the present invention. FIG. 8A shows an example of an application screen for joining an abc member. In the part on this application screen, here, the following shown in the figure is input.

Authentication ID: abc0003 Password: b0394 Here, the abc company has the authentication table name of the entry whose URL of the homepage page in the homepage identification table 8 in FIG. ID table ", and the authentication is set in the" authentication table "of FIG. 3C. Therefore, on this authentication screen," authentication ID "(the unique A system authentication ID) and a "password" are input. In addition, in order to avoid plagiarism when actually inputting and displaying the echo, "********
* ”Is displayed.

The member authentication ID and password newly input from the application screen as described above are newly added and registered as shown in the entry of the authentication ID table 10 in FIG. 3C described above. I do. Similarly, the new member information is registered in the basic item table 11 of FIG. 3D, and the new member information is registered in the extended item a table 12 of FIG. 3E.

FIG. 8B shows an example of an application screen on the defg company homepage. Here, the following shown in the figure is entered in the section 'on the application screen. -E-mail address: itou @ bbb. com / password: 9012 Here, the defg company determines the URL of the homepage page in the homepage identification table 8 of FIG.
Is set as the "mail address table" of the entry that matches, and the authentication is set to be performed in the "mail address table" of FIG. 3B. In addition, it is made to input 'email address' and 'password'. Note that the password is actually displayed as "****" to avoid plagiarism when it is input and echo-displayed.

The mail address and password of the member newly input from the application screen as described above are newly added and registered as shown in the entry of the mail address 9 in FIG. 3B. I do. And, similarly, FIG.
The new member information is registered in the basic item table 11 shown in FIG. 3D, and the new member information is registered in the extended item b table 12 shown in FIG.

(Supplementary Note 1) In a member authentication system for managing member authentication for different services or different providers, a first table for registering an authentication table ID in association with an identification code of a homepage accessed by a member; Authentication table I registered in the first table
A member authentication system, comprising: a second table corresponding to D for registering member authentication information; and means for searching and authenticating the first table and the second table.

(Supplementary Note 2) In a member authentication system for managing member authentication for different services or different providers, a first table for registering an authentication table ID in association with an identification code of a homepage accessed by a member; Authentication table I registered in the first table
D, a second table for registering the member authentication information, and the corresponding authentication information of the member on the second table or the corresponding authentication information and the corresponding identification code of the first table. A third table for registering information; and a means for searching the first table, the second table, and the third table for authentication or for searching authentication and personal information. Member authentication system.

(Supplementary Note 3) The authentication information of the second table or the authentication information of the second table and the first table
3. The member authentication system according to claim 2, further comprising a fourth table for registering the member's extension information in association with the extension item table ID registered in said table.

(Supplementary Note 4) The first and third tables are common to all members, and the second table and the fourth table are provided for each service or each provider. The member authentication system according to claim 1 or 2.

(Supplementary Note 5) In a member authentication method for managing member authentication for different services or different providers, a first table for registering an authentication table ID in association with an identification code of a homepage accessed by a member; A second table for registering the member authentication information corresponding to the authentication table ID registered in the first table; and the corresponding authentication information or the corresponding authentication information of the member on the second table and the first table. A third table for registering member information in association with the corresponding identification code, and searching the first table, the second table, and the third table to search for authentication or authentication and personal information A member authentication method characterized by:

(Supplementary Note 6) The authentication information of the second table or the authentication information of the second table and the first
And a fourth table for registering the member's extended information in association with the extended item table ID registered in the third table. After the third table, the fourth table is searched for authentication or authentication and personal information. The member authentication method according to claim 5, wherein is searched.

(Supplementary Note 7) The first table and the third table are common to all members, and the second table and the fourth table are provided for each service or each provider. The member authentication method according to claim 5 or 6.

(Supplementary Note 8) A first table for registering an authentication table ID in association with an identification code of a home page accessed by a member, and member authentication information corresponding to the authentication table ID registered in the first table And a third table for registering member information in association with the corresponding authentication information of the member on the second table or the corresponding authentication information and the corresponding identification code of the first table.
And a computer-readable recording medium storing a program that functions as a means for searching the first table, the second table, and the third table to perform authentication or to search for authentication and personal information. .

(Supplementary Note 9) The authentication information of the second table or the authentication information of the second table and the first table
And a fourth table for registering the member's extended information in association with the extended item table ID registered in the third table. After the third table, the fourth table is searched for authentication and personal information. The computer-readable recording medium according to claim 8, wherein the computer-readable recording medium stores a program that functions as a means for executing the program.

[0070]

As described above, according to the present invention,
It becomes possible to perform member authentication and search for personal information with versatility for each provider (company) and for each service content.

As a result, conventionally, each member company or service content is constructed, so that there are a plurality of member management systems, and it is necessary to create each member in spite of the same member management system. To eliminate the current situation where resources only increase without
Member management can be realized according to each requirement for each company or each service content.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram of the present invention.

FIG. 2 is an operation explanatory flowchart (authentication) of the present invention.

FIG. 3 is an example of a member DB of the present invention.

FIG. 4 is an example of a public homepage of each company of the present invention.

FIG. 5 is an example of an authentication screen of each company according to the present invention.

FIG. 6 is an example of a member site page of each company of the present invention (a home page that only members can enter).

FIG. 7 is an example of a public homepage of each company of the present invention.

FIG. 8 is an example of an application screen of each company according to the present invention.

[Explanation of symbols]

 1: Member management system 2: Server 4: Processing device 5: Registration means 6: Authentication means 7: Member DB 8: Homepage identification table 9: E-mail address table 10: Authentication ID table 11: Basic item table 12: Extended item table 21 , 31: Services for corporate members 22, 32: Homepage screen 23, 33: Member registration screen

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Kosuke Hibi 4-1-1, Kamiodanaka, Nakahara-ku, Kawasaki-shi, Kanagawa Prefecture Inside Fujitsu Limited (72) Inventor Takashi Ariyama 4 Kamikadanaka, Nakahara-ku, Kawasaki-shi, Kanagawa Prefecture 1-1-1, Fujitsu Limited (72) Inventor Hiroshi Mizuno 4-1-1, Kamiodanaka, Nakahara-ku, Kawasaki City, Kanagawa Prefecture Fujitsu Limited (72) Inventor Yoko Suzuki 4 Ueodanaka, Nakahara-ku, Kawasaki City, Kanagawa Prefecture 1-1-1, Fujitsu Limited (72) The inventor Manabu Nishiyama 4-1-1, Kamidadanaka, Nakahara-ku, Kawasaki-shi, Kanagawa F-term in Fujitsu Limited 5B085 AE23 BG07

Claims (5)

[Claims] 1. A user authentication system for managing authentication information of a user who uses a service, an authentication table for storing authentication information of the user, a service identifier for identifying the service, and authentication for the user of the service. A service identification table for storing an authentication table identifier for identifying the authentication table for storing information; and an authentication table corresponding to a service to be used by referring to the service identification table when receiving an authentication request from a user. A user authentication system for identifying the user and referring to the authentication table to authenticate the user. 2. The system according to claim 1, further comprising a personal information table for storing personal information on the user.
User authentication system as described. 3. The user authentication system according to claim 2, wherein said personal information table is provided for each of said services. 4. A user authentication method for managing authentication information of a user who uses a service, comprising: receiving an authentication request from a user; a service identifier for identifying a service based on the request; Referring to a service identification table that stores an authentication table identifier that identifies an authentication table that stores authentication information about the user, and identifying an authentication table corresponding to a service to be used. Performing a user authentication with reference to the user authentication method. 5. A step of receiving an authentication request from a user, a service identifier for identifying a service based on the request, and an authentication table identifier for identifying an authentication table for storing authentication information on a user of the service. A program for executing the steps of: referring to a service identification table storing the authentication table and identifying an authentication table corresponding to a service to be used; and performing the step of authenticating the user by referring to the identified authentication table A computer-readable recording medium storing a computer.