JP3677448B2 - Authentication relationship management system, server device used therefor, authentication relationship management method, and recording medium - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
  The present invention is an authentication relationship management system and method, and an element for constructing the authentication relationship management system.Server device,Furthermore, the present invention relates to a recording medium storing a program for realizing the function of the authentication relationship management system by software, and in particular, to a system for managing the relationship between a certifier and a person to be authenticated regarding various types of authentication performed in a company. Is preferred.
[0002]
[Prior art]
  In general, in order to perform various activities and work for members belonging to each department in a company, authentication of the supervisor is often required. For example, when an individual member enters the daily attendance status in the work slip, he / she is certified by his / her supervisor as to whether the status of late arrival, early departure, business trip, overtime, etc. is properly entered in addition to the presence of attendance. It is common to have to.
[0003]
  Conventionally, management related to attendance information has been performed on a paper basis. That is, each member of the department uses a time card or a dedicated work slip form to fill in the necessary items, and the boss confirms the contents and then performs the seal. In addition, the management of authentication related to which department members are authenticated by which boss was performed on a paper basis by the administrative staff for each affiliation in the company.
[0004]
  By the way, in recent years, there has been proposed an information system that realizes a business flow in a company by using a computer technology or a network technology such as an intranet or the Internet. In this information system, there is also proposed a system in which an authenticator who performs predetermined authentication and an authenticated person who receives the authentication are set separately.
[0005]
[Problems to be solved by the invention]
  However, in the conventional information system, it is necessary to input the names and the like of the authenticator and the person to be authenticated one by one using a keyboard or the like, and the input operation is very complicated. In particular, when there is an organizational change or personnel change, it is necessary to reset the relationship between the certifier and the person to be authenticated for all related departments. When there is a large amount, there is a problem that the amount of work becomes enormous.
[0006]
  Further, in the conventional information system, the management of authentication relations is left to each department in the company on the spot, and there is no mechanism for centrally managing the authentication relations. Also, in the event of a personnel change, there is no mechanism for linking the authentication relationship management in the department to which the transfer belongs and the authentication relationship management in the department to which the transfer belongs, so that the authentication relationship can be changed smoothly. There was also a problem that it could not be done.
[0007]
  That is, when there is a personnel change, it is necessary to delete the authentication relationship in the department to which the change belongs and newly set the authentication relationship in the department to which the change belongs. However, in the conventional information system, it is necessary to delete and reset this authentication relationship separately. Therefore, in the department to which the transfer source or transfer destination belongs, the authentication relationship before and after the transfer can be grasped collectively. It was difficult to set up or had to do very tedious work if possible.
[0008]
  It is possible to delete and reset the authentication relationship individually in the department to which the transfer source belongs and the transfer destination, but if this is not done on the same day, the authentication relationship setting will be inconsistent. In addition, for example, depending on the company, when a personnel change occurs, the transition period for changing the authentication relationship is not the supervisor at the transfer destination but the former supervisor before the change during the predetermined period from the date of the change order. In some cases, authentication is also required. However, in the conventional information system, it is very difficult to manage such a transition period.
[0009]
  The present invention has been made in view of such circumstances, and enables management of the relationship between a certifier and a person to be authenticated with a simple operation even if there is an organizational revision or personnel change. With the goal.
  In addition, the present invention provides a mechanism for centrally managing authentication relationships in each department, so that authentication relationships can be changed smoothly, and authentication relationship transition management can be easily performed. It is aimed.
[0010]
[Means for Solving the Problems]
  The present invention is an authentication-related matrix in which an authenticator and a person to be authenticated are represented on the X-axis and the Y-axis, and the check can be switched on / off by clicking the mouse on each square of the matrix. The matrix with the box insertedBased on personal information including first information representing personal affiliation and second information representing the presence or absence of authentication qualificationAn authentication relationship matrix providing means to be created and provided; and an authentication relationship registration means for associating the authenticator corresponding to the position where the check box is turned on with the person to be authenticated and registering it in the database as authentication relationship information.The authentication relationship matrix providing means extracts a target person belonging to the same group based on the first information, and the extracted target person is classified into the authenticator and the person to be authenticated based on the second information. Create the above matrix with distinctionIt is characterized by that.
[0011]
  In another aspect of the invention,Based on the authentication relation information already registered in the database, the authentication relation matrix providing means can authenticate a certifier belonging to a different affiliation associated with a certain affiliation subject to the same affiliation as the authentication subject. The matrix is created so as to be expressed in a mode different from that of a person.
[0012]
  Since the present invention comprises the above technical means, the relationship between the authenticator and the person to be authenticated is provided in the form of a matrix, and the authentication relationship can be easily confirmed. Further, according to the present invention, it is possible to register, change, delete, etc. authentication relationships by simply clicking a check box displayed on the matrix.
  Further, according to the present invention, since the matrix is created based on the personal information including the first information indicating the affiliation of the individual and the second information indicating the presence or absence of the authentication qualification, the organization revision or personnel change can be performed. Even if it occurs, the matrix is automatically updated based on the first information and the second information that are changed accordingly, and it is not particularly necessary to rework the matrix.
[0013]
  Further, according to another feature of the present invention, the certifier in the original department before the organizational change or personnel change is displayed on the matrix together with the certifier in the department to which the change is made. It is possible to delete the authentication relationship before the transfer and register the authentication relationship after the transfer in a single matrix. Therefore, it is possible to simplify the update operation of the authentication relationship, and it is possible to prevent the occurrence of inconsistency due to the update of the authentication relationship in both departments of the transfer source and the transfer destination. At this time, for example, when a predetermined period has elapsed from the date of the personnel change order, the original certifier's check box is unchecked and the new certifier's check box is turned on. It is also possible to easily manage the transition period such that the period is authenticated by the original certifier before the change.
[0014]
DETAILED DESCRIPTION OF THE INVENTION
  Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
  FIG. 1 is a diagram illustrating a configuration example of an authentication relationship management system according to the present embodiment. The authentication relationship management system of the present embodiment includes a web server 1, a database server (hereinafter referred to as a DB server) 2, and a plurality of client terminals 3._-1, 3_-2, 3_-3,..., A personal information DB 4 and an authentication relation DB 5. Servers 1 and 2 and client terminal 3_-1, 3_-2, 3_-3Are connected to each other via a network 6 such as an intranet so that they can communicate with each other.
[0015]
  The web server 1 is connected to each client terminal 3_-1, 3_-2, 3_-3In response to a request from the client terminal 3 of the request source_-1, 3_-2, 3_-3,... Are provided with information such as HTML (Hyper Text Markup Language). Specifically, authentication relationship information representing the relationship between the certifier and the person to be authenticated in each department in the company is provided in a matrix display as shown in FIG.
[0016]
  The DB server 2 registers information and authentication related information about each individual in the company in the personal information DB 4 and the authentication related DB 5, or receives personal information and authentication related information corresponding to the request in response to a request from the web server 1. A process of retrieving and providing from the personal information DB 4 and the authentication relation DB 5 is performed. The web server 1 displays an HTML screen on which authentication-related information is displayed in a matrix as a client terminal 3._-1, 3_-2, 3_-3,..., An inquiry is made to the DB server 2 to obtain necessary information.
[0017]
  Client terminal 3_-1, 3_-2, 3_-3,... Are so-called personal computers used by persons in charge in each department in the company or persons in charge in the personnel department. Each client terminal 3_-1, 3_-2, 3_-3,... Above, a web browser program is operated, and personal information and authentication related information are registered in the personal information DB 4 and the authentication related DB 5 through the web server 1 and the DB server 2, or desired information is registered from the personal information DB 4 and the authentication related DB 5. Can be obtained.
[0018]
  That is, the client terminal 3_-1, 3_-2, 3_-3,..., In accordance with a URL (Uniform Resource Locator) designated by the user, the web browser requests the web server 1 having the URL to transmit HTML information. Upon receiving this HTML information transmission request, the web server 1 inquires the DB server 2 and acquires necessary information corresponding to the request from the personal information DB 4 and the authentication relation DB 5. Then, a web page in a matrix display as shown in FIG. 2 is constructed using the acquired information, and is returned to the web browser as HTML source code.
[0019]
  The web browser analyzes the HTML source code received from the web server 1 and displays text information included in the source code on the screen. Such web server 1 and client terminal 3_-1, 3_-2, 3_-3The client terminal 3 is exchanged with the web browser on the side._-1, 3_-2, 3_-3,..., A web page including an authentication-related matrix display as shown in FIG. 2 is displayed.
[0020]
  Furthermore, it is also possible for the user to input information as necessary on the web browser screen displayed as shown in FIG. 2 and to make a registration request for the input information to the web server 1. Upon receiving this registration request, the web server 1 makes an inquiry to the DB server 2 and registers the authentication information included in the registration request in the authentication relationship DB 5. It is also possible for a user to input personal information on a personal information registration screen (not shown) other than that shown in FIG. 2 as necessary, and to register the personal information in the personal information DB 4 through the web server 1 and the DB server 2. It is.
[0021]
  When the personal information and the authentication related information are registered in the personal information DB 4 or the authentication related DB 5, the web server 1 configures a web page of a confirmation screen informing that the registration is completed, and transmits it to the web browser as an HTML source code. Return it. The web browser notifies the user that registration has been completed successfully by analyzing and displaying the HTML source code received from the web server 1.
[0022]
  Next, the screen of FIG. 2 will be described in detail. As shown in FIG. 2, in this embodiment, the relationship between the authenticator and the person to be authenticated is displayed in a matrix 21. In the matrix 21, the authentication relationship can be displayed for any department in the company (XXX in the case of FIG. 2), and the horizontal axis (X axis) indicates the target persons (certifiers A to E) who can be authenticators. All are displayed, and all belonging members (work slip input persons a to f) excluding the certifier are displayed on the vertical axis (Y axis).
[0023]
  Which department's authentication relationship is displayed depends on the client terminal 3_-1, 3_-2, 3_-3,... Can be arbitrarily specified on the web browser, and can be specified by transmitting to the web server 1 together with a transmission request for HTML information. Further, it may be uniquely specified according to an input person who has made a transmission request for HTML information (in the case of FIG. 2, person in charge α). For example, when there is an input from the person in charge α who is in charge of managing the authentication relationship with respect to the XXX portion, a mode of uniquely displaying the authentication relationship of the XXX portion is conceivable.
[0024]
  Regarding the identified department, the authenticators A to E displayed on the X axis and the affiliated members a to f displayed on the Y axis are identified using personal information stored in the personal information DB 4.
  FIG. 3 is a diagram illustrating a configuration example of personal information. The personal information includes the name, affiliation code, residence code, and qualification code of each individual.
[0025]
  The affiliation code is a code for uniquely identifying each department of the company organization. The residence code is a code for uniquely identifying the residence location of each individual. When the same department exists in a plurality of regions, this resident code identifies the resident member of the resident area. If the same department does not exist in multiple areas, this location code is not required.
[0026]
  The qualification code is a code for identifying whether each individual has a qualification to authenticate. As this qualification code, it is sufficient to have at least two codes with / without authentication qualification, but it is also possible to use a position code arbitrarily determined by a company. In this case, it is only necessary to define which positions have authentication qualifications and which positions do not have authentication qualifications.
[0027]
  In the case of the example in FIG. 2, all the subjects A to E and a to f belonging to the same code are extracted by the affiliation code and the residence code (first information), and they are authenticated by the qualification code (second information). And is displayed as a matrix 21 for each person.
[0028]
  A check box 22 is displayed on each square of the matrix 21. It is possible to newly register / add / update / delete authentication relation information in the authentication relation DB 5 by turning on / off the check box 22 by clicking the mouse and clicking the registration button 23.
[0029]
  In the initial stage, all the check boxes 22 are in an off state (a state in which the check symbol “re” is not entered). In this state, the check box 22 at an arbitrary position is switched to an on state (a state in which a check symbol “re” is entered), and when the registration button 23 is clicked, the authentication related information in the part where the check box 22 is on is authenticated. Registered in the relation DB5. One or more certifiers can be registered for one member.
[0030]
  FIG. 4 is a diagram illustrating a configuration example of authentication relationship information registered in the authentication relationship DB 5. As shown in FIG. 4, the authentication related information is configured by table information describing the relationship between the authenticator and the person to be authenticated. According to this table information, for example, with respect to the member a, an authentication relationship is registered that authentication is required from two certifiers A and B.
[0031]
  Once the authentication relationship information is registered, the check symbol “re” is displayed in the check box 22 of the subject who has been associated with the authentication relationship based on the authentication relationship information registered in the authentication relationship DB 5 from the next time. The matrix 21 is displayed in a state where is entered. When it is necessary to change the authentication relationship due to organizational changes or personnel changes, the corresponding check box 22 is switched on / off and the registration button 23 is clicked to easily add, change, or delete the authentication related information. Can be done.
[0032]
  When an organizational change or personnel change occurs, personal information (affiliation code, residence code, qualification code) is changed by a personnel officer, for example, using a registration screen (not shown). As a result, the contents of the matrix 21 are also automatically changed. However, in this case, only the personal information in the personal information DB 4 is changed, and the authentication related information in the authentication related DB 5 has not been changed yet. Therefore, in the present embodiment, the certifier specified by the authentication-related information before the change is displayed on the right end of the X axis of the matrix 21 with a display color different from that of other certifiers.
[0033]
  For example, it is assumed that member y is added to the XXX department due to personnel changes. Further, it is assumed that the certifier before the transfer of the member y is the certifier Z belonging to a department other than the XXX department. In this case, since the member y can be confirmed to belong to the XXX section based on the affiliation code and the residence code in the personal information DB 4 changed by the person in charge of personnel, the member y on the Y axis of the matrix 21 as shown in FIG. Is newly added and displayed.
[0034]
  Regarding this member y, it is necessary to update the authentication related information by designating a new certifier among the certifiers A to E in the XXX section, but based on the authentication related information before the update at the stage before the update. The previous authenticator Z is displayed in a color (for example, red) different from the other authenticators A to E (for example, black) at the right end of the X axis of the matrix 21. Client terminal 3_-1, 3_-2, 3_-3,... Turn off the check box 22 of the certifier Z at the required timing, turn on any check box 22 of the certifiers A to E, and click the registration button 23 to thereby obtain authentication related information. Update.
[0035]
  Thereby, even if there is a personnel change, the previous authenticator Z can be confirmed at a glance if the authentication-related matrix 21 is displayed. Further, by displaying the previous certifier Z in a different display color, it is possible to call attention that the certifier Z is not a member of the same affiliation and that the designation of the certifier should be updated. In addition, it is possible to easily manage the transition period so that the former supervisor before the change is authenticated for a predetermined period from the date of the personnel change issuance.
[0036]
  In this embodiment, when registering authentication-related information, it is possible to designate and register a main authenticator and a sub-authenticator. The main certifier is a person who always authenticates unless there are special circumstances. The sub-certifier is a person who performs authentication as a proxy when the main certifier cannot be authenticated due to a business trip or the like. The screens of FIGS. 2 and 5 show the state where the main authentication person is designated and the authentication related information matrix 21 is displayed as displayed in the title 24.
[0037]
  When a sub-authenticator is designated, the same screen as that shown in FIGS. 2 and 5 (only the title 24 is different) is displayed separately, and authentication related information can be registered in the same manner. Here, the main certifier and the sub-certifier are registered on different screens, but the present invention is not limited to this example. For example, both may be registered on the same screen, and the main authenticator and the sub-authenticator may be distinguished from each other by the difference in display color of the check symbol “re”.
[0038]
  Further, a certifier addition button 25 is displayed on the display screens of FIGS. 2 and 5. This certifier addition button 25 is used when it is desired to add another certifier in addition to the certifier specified by the same affiliation code and residence code. In day-to-day corporate activities, there are cases where human resources are crossed from multiple departments and a project for a certain period is formed. In such a case, when it is necessary to set the supervisor of the project as a certifier, by clicking the certifier addition button 25, any supervisor belonging to a different affiliation code or residence code can be designated as a certifier. Can be added as
[0039]
  FIG. 6 shows the client terminal 3_-1, 3_-2, 3_-3,... Is a flowchart showing an operation of accessing the web server 1 to display an authentication-related matrix 21 and registering authentication-related information.
  Client terminal 3_-1, 3_-2, 3_-3,..., The user inputs the URL of the web server 1 on the web browser to access the web server 1 and requests acquisition of a matrix display screen representing the authentication relationship of a certain department (step S1).
[0040]
  Receiving this request, the web server 1 inquires the DB server 2 about the subject belonging to the requested department and the authentication relationship (step S2). In response to this inquiry, the DB server 2 extracts all persons of the same affiliation code and the same residence code corresponding to the department from the personal information DB 4 (step S3). Further, the authenticator and the person to be authenticated are distinguished and extracted from all the extracted subjects based on the qualification code (step S4).
[0041]
  Furthermore, the DB server 2 extracts authentication relationship information related to the subject extracted in step S3 from the authentication relationship DB 5 (step S5). Then, based on the extracted authentication-related information, the certifier associated with each person to be authenticated who has not been extracted in step S4 (that is, the original in the case where there is an organizational revision or personnel change) Is extracted from the personal information DB 4 (step S6).
[0042]
  The DB server 2 transmits the personal information extracted in steps S3 to S6 and the authentication related information to the web server 1. Using the received personal information, the web server 1 creates a matrix 21 in which the certifier is placed on the X axis and the person to be authenticated is placed on the Y axis (step S7). At this time, if there are certifiers belonging to different affiliations and different residences, the matrix 21 is created so that this is displayed in red on the right end of the X axis.
[0043]
  In the present example, the authenticator and the person to be authenticated are distinguished based on the qualification code in the DB server 2. Therefore, if personal information or the like is transmitted to the web server 1 in a state in which the distinction is understood, the DB server 2 Therefore, only the name of the target person needs to be sent to the web server 1 for the personal information. However, the qualification code may be transmitted to the web server 1 together with the name of the subject person so that the web server 1 can distinguish between the authenticator and the person to be authenticated.
[0044]
  In addition, the web server 1 completes the matrix 21 by turning on the check box 22 of the subject who has been associated with the authentication relationship based on the authentication relationship information received from the DB server 2. A web page is created and sent back to the web browser (step S8). The web browser displays the web page of the matrix 21 acquired from the web server 1 on the screen (step S9).
[0045]
  Furthermore, the client terminal 3_-1, 3_-2, 3_-3,..., The user switches on / off the check box 22 at an arbitrary position in the matrix 21 as necessary, and clicks the registration button 23 (step S10). Thereby, the registration request for the added, changed or deleted authentication relationship is transmitted to the web server 1 together with the authentication related information. At this time, only the updated part of the authentication related information may be transmitted, or the updated authentication related information of the entire matrix 21 may be transmitted.
[0046]
  Receiving this registration request, the web server 1 issues a registration inquiry to the DB server 2 (step S11). Upon receiving this inquiry, the DB server 2 sends the client terminal 3_-1, 3_-2, 3_-3,... Are registered in the authentication relationship DB 5 (step S12).
[0047]
  Then, the DB server 2 transmits a message indicating that registration has been completed to the web server 1 (step S13). Upon receiving this message, the web server 1 creates a web page notifying the completion of registration, and the client terminal 3 that has requested registration_-1, 3_-2, 3_-3,... Are returned to the web browser (step S14). The web browser displays the registration confirmation web page acquired from the web server 1 on the display screen (step S15).
[0048]
  As described above in detail, according to the authentication relationship management system of this embodiment, since the relationship between the authenticator and the person to be authenticated is displayed in the matrix 21, the authentication relationship can be easily confirmed. . Further, by registering authentication related information in the authentication relationship DB 5 and connecting them via a network 6 such as an intranet, the authentication relationship in each department in the company can be managed in a centralized manner. Authentication management can be easily managed by the human resources department.
[0049]
  In addition, a check box 22 is displayed on the matrix 21, and new registration, addition, change, and deletion of authentication relations are performed by clicking the mouse on the check box 22. Therefore, the names of the authenticator and the person to be authenticated are displayed on the keyboard. Compared to the conventional system that has been used for input one by one, it is possible to perform registration-related registration updates and the like with a very simple operation. Thereby, the workload of the person in charge can be reduced.
[0050]
  Further, when an organizational change or personnel change occurs, the matrix 21 is automatically updated and displayed based on the affiliation code, the residence code, and the qualification code. There is no need to rework 21.
[0051]
  The authentication relationship may be updated in the department to which the change is made, and no update work is required at the transfer source. That is, in this embodiment, the original certifier before the change is also displayed on the matrix 21. Therefore, the deletion of the authentication relationship in the department belonging to the transfer source and the addition of the authentication relation in the department belonging to the transfer destination are changed. This can be done simply by switching on / off the corresponding check box 22 on the matrix 21 representing the previous authentication relationship. Therefore, it is possible to remarkably reduce the work load on the person in charge, and it is possible to prevent the occurrence of authentication-related inconsistencies.
[0052]
  At this time, when a predetermined period has elapsed from the date of the personnel change order, the original certifier check box 22 is turned off and the new certifier check box 22 is turned on, so that the date of the change order is issued. It is easy to manage the transition period, such as receiving authentication from the former supervisor before the change for a certain period.
[0053]
  The authentication relationship management system of the present embodiment described above is configured by a computer CPU or MPU, RAM, ROM, and the like, and can be realized by operating a program stored in the RAM or ROM. Therefore, a program that causes a computer to perform the above functions can be realized by recording the program on a recording medium such as a CD-ROM and causing the computer to read the program. As a recording medium for recording the program, a floppy disk, a hard disk, a magnetic tape, an optical disk, a magneto-optical disk, a DVD, a nonvolatile memory card, and the like can be used in addition to the CD-ROM.
[0054]
  In addition, the functions of the above-described embodiments are realized by executing a program supplied by a computer, and the program is used in cooperation with an OS (operating system) or other application software running on the computer. When the functions of the above-described embodiment are realized, or when all or part of the processing of the supplied program is performed by a function expansion board or a function expansion unit of the computer, the function of the above-described embodiment is realized. Such a program is included in the embodiment of the present invention.
[0055]
  The present invention is used in a network environment, and includes a web server 1, a DB server 2, and a client terminal 3._-1, 3_-2, 3_-3,... May be downloaded via the Internet or the like. Further, all or a part of this program may be executed by another computer.
[0056]
  Note that the authentication relationship management system of this embodiment can be applied to a system that supports the workflow when each member in the company inputs the daily attendance status into the work slip and receives the supervisor's authentication. is there. Further, the system to which this embodiment is applied is not limited to such a work slip system, and any system that performs authentication can be applied. For example, the present invention can be applied to a system that supports an authentication workflow that must be received when a member of a company purchases a product from another company in a transaction between companies.
[0057]
  Moreover, in the said embodiment, although the authentication relationship management system was comprised as an intranet in a company, it is not limited to this. For example, an authentication relationship management system may be configured using a wider network such as the Internet, or may be configured as a stand-alone type authentication relationship management device without using a network.
[0058]
  In addition, the above-described embodiment is merely an example of the embodiment for carrying out the present invention, and the technical scope of the present invention should not be construed in a limited manner. In other words, the present invention can be implemented in various forms without departing from the spirit or main features thereof.
[0059]
【The invention's effect】
  As described above, according to the present invention, the relationship between the authenticator and the person to be authenticated can be easily confirmed in the form of a matrix. Also, registration, change, deletion, etc. of authentication relations can be performed by simply clicking a check box displayed on the matrix. Also,According to the present invention,Even when an organizational change or personnel change occurs, the matrix is automatically updated based on the first information that indicates the affiliation of each individual and the second information that indicates the presence or absence of authentication qualifications. You can eliminate it. According to another feature of the present invention, authentication-related information in each department within a company can be centrally managed as a database accessible via a network.
  Therefore, even if there is an organizational revision or personnel change, the relationship between the authenticator and the person to be authenticated can be managed with a simple operation.
[0060]
  In addition, according to another feature of the present invention, the authentication relationship before the change and the registration of the authentication relationship after the change can be collectively performed in one matrix, thereby simplifying the update operation of the authentication relationship. As a result, it is possible to perform this smoothly, and it is possible to prevent the occurrence of inconsistency due to the update of the authentication relationship in the department to which both the transfer source and the transfer destination belong. At this time, for example, when a predetermined period has elapsed from the date of the personnel change order, the original certifier's check box is unchecked and the new certifier's check box is turned on. The transition period can be easily managed such that the period is authenticated by the original certifier before the change.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating a configuration example of an authentication relationship management system according to an embodiment.
FIG. 2 is a diagram showing an example of an authentication relationship matrix display screen according to the present embodiment.
FIG. 3 is a diagram illustrating a configuration example of personal information according to the present embodiment.
FIG. 4 is a diagram illustrating a configuration example of authentication-related information according to the present embodiment.
FIG. 5 is a diagram showing another example of an authentication relationship matrix display screen according to the present embodiment.
FIG. 6 is a flowchart showing an operation of displaying an authentication relationship matrix and registering authentication relationship information.
[Explanation of symbols]
1 Web server
2 DB server
3_-1, 3_-2, 3_-3  Client terminal
4 Personal information DB
5 Authentication DB
6 network
21 Authentication-related display matrix
22 Check box
23 Registration button
24 titles
25 Certifier add button

Claims (9)

An authentication-related matrix that represents the certifier and the person to be authenticated on the X-axis and Y-axis, and a check box that can be switched on / off by clicking the mouse is inserted on each square of the matrix. An authentication relationship matrix providing means for creating and providing a matrix based on personal information including first information indicating personal affiliation and second information indicating the presence or absence of authentication qualifications ;
Authentication relation registration means for associating the authenticator corresponding to the position where the check box is turned on with the person to be authenticated and registering it in the database as authentication relation information ;
The authentication relationship matrix providing means extracts a target person belonging to the same affiliation based on the first information, and divides the extracted target person into the certifier and the person to be authenticated based on the second information. An authentication relationship management system, wherein the matrix is created separately . An authentication relationship management system in which a server device and a client device are connected to be communicable with each other via a network,
The server device includes personal information storage means for storing, as a first database, personal information including first information representing personal affiliation and second information representing presence or absence of authentication qualifications;
A matrix of authentication relations representing the authenticator and the person to be authenticated on the X-axis and the Y-axis based on the personal information stored in the personal information storage means, and clicking the mouse on each square of the matrix An authentication relationship matrix providing unit that creates a matrix in which a check box that can be switched on and off by an operation is inserted and provides the matrix to the client device;
An authentication relationship registration means for associating an authenticator corresponding to a position where the check box is turned on in the client device with the person to be authenticated and registering it as authentication relationship information;
Authentication relationship storage means for storing the authentication relationship information registered by the authentication relationship registration means as a second database;
The client device includes matrix display means for displaying a matrix provided from the server device on a display device;
A registration request unit that switches on / off of a check box at an arbitrary position on the matrix by clicking a mouse and requests the authentication relationship registration unit of the server device to register the authentication relationship information ;
The authentication relationship matrix providing means extracts a target person belonging to the same affiliation based on the first information, and divides the extracted target person into the certifier and the person to be authenticated based on the second information. An authentication relationship management system, wherein the matrix is created separately . The authentication relationship matrix providing means, based on authentication relationship information that has already been registered, refers to a certifier belonging to a different affiliation that is associated with a certifier belonging to a certain affiliation. The authentication relationship management system according to claim 1 or 2 , wherein the matrix is created so as to be expressed in a different manner. A server device that provides information related to an authentication relationship in response to a request from a client device that is communicably connected via a network,
An authentication-related matrix that represents the certifier and the person to be authenticated on the X-axis and Y-axis, and a check box that can be switched on / off by clicking the mouse is inserted on each square of the matrix. An authentication relationship matrix providing means for creating a matrix based on personal information including first information representing personal affiliation and second information representing the presence or absence of authentication qualification, and providing the matrix to the client device;
Authentication relation registration means for associating the authenticator corresponding to the position where the check box is checked in the client device with the person to be authenticated and registering it in the database as authentication relation information ;
The authentication relationship matrix providing means extracts a target person belonging to the same affiliation based on the first information, and divides the extracted target person into the certifier and the person to be authenticated based on the second information. A server apparatus that creates the matrix separately . The authentication relationship matrix providing unit is configured to authenticate certifiers belonging to different affiliations associated with a certain affiliation subject based on the authentication reliance information already registered in the database. The server device according to claim 4 , wherein the matrix is created so as to be expressed in a different form from a person. A server device that provides information related to an authentication relationship in response to a request from a client device that is communicably connected via a network,
Personal information storage means for storing, as a first database, personal information including first information representing personal affiliation and second information representing presence / absence of authentication qualification,
In response to a request given from the outside, a target person belonging to the same affiliation is extracted using the first information as a key, and the extracted target person is classified into an authenticator and a person to be authenticated based on the second information. Personal information providing means provided separately;
Authentication relationship registration means for registering authentication relationship information between the certifier whose association is specified in the client device and the person to be authenticated;
Authentication relationship storage means for storing the authentication relationship information registered by the authentication relationship registration means as a second database;
A server apparatus comprising: authentication related information providing means for providing authentication related information related to the subject extracted by the personal information providing means. A first step of extracting subjects belonging to the same affiliation based on the first information representing the affiliation of the individual ;
A second step of distinguishing the extracted target person into an authenticator and a person to be authenticated based on the second information indicating the presence or absence of authentication qualification ;
A matrix of the authentication relationship represents and the authenticator and the authentication subject to X-axis and Y-axis, the check boxes that you can be switched on / off by a mouse click operation on each cell of the matrix A third step of creating and displaying the inserted matrix on a display device ;
An authentication relationship management method comprising: a fourth step of associating an authenticator corresponding to a position where the check box is turned on with a person to be authenticated and registering it in the database as authentication relationship information. 7. A computer-readable recording medium in which a program for causing a computer to function as each means according to claim 1 is recorded. A computer-readable recording medium having recorded thereon a program for causing a computer to execute the processing procedure of the authentication relationship management method according to claim 7 .

Images