JP7724556B2 - Program and information processing device - Google Patents

Description

The present invention relates to a program and an information processing device.

Conventionally, authentication registration systems have been known that accept registration requests from business servers, register users on the business servers, and perform authentication based on the registered information.

In this regard, Patent Document 1 discloses that a first server performs authentication in accordance with an authentication request from a user terminal and transmits authentication information to the user terminal, a second server (business server) generates a cookie in accordance with the authentication information transmitted from the user terminal and transmits it to the user terminal, and the second server then performs authentication in accordance with the cookie transmitted from the user terminal.

Patent No. 4758575

However, with the technology described in Patent Document 1, if the pre-registered items required for authentication differ between multiple business servers, only the items common to each business server are stored as registered items, and the missing registered items must be registered separately on the business server. Therefore, the technology described in Patent Document 1 has the problem of making user registration on the business server time-consuming.

The present invention was made in consideration of these problems, and its purpose is to provide a program and information processing device that allows users to easily register on a business server, even if the registration items required for registration differ between multiple business servers.

To solve the above problem, the program of the present invention causes a computer capable of communicating with a business server and a user terminal to function as: accepting means for accepting from the business server a registration request including user information about a user of the business server and registration items for registration at the business server; registration means for accepting from the user terminal input of the registration item and registering the registration item and the received content in the user registration information if the registration item is not registered in the user registration information about the user corresponding to the user information included in the registration request accepted by the accepting means; and issuing means for referencing the user registration information and issuing to the business server authentication information for authenticating the user corresponding to the user information included in the registration request.

Furthermore, the registration request includes a plurality of registration items related to the user, and the registration means registers, in the user registration information, any registration items among the plurality of registration items that are not included in the user registration information.

Furthermore, if the registration item is not included in the user registration information, the issuing means issues the authentication information after registration is performed by the registration means.

The computer is further caused to function as authorization means that performs authorization processing on the business server when the registration items are included in the user registration information or when registration is performed by the registration means.

In addition, the issuing means issues the authentication information after the authorization means has performed the authorization-related processing.

An information processing device of the present invention is an information processing device capable of communicating with a business server and a user terminal, and includes: a receiving means for receiving from the business server a registration request including user information about a user of the business server and registration items for registration at the business server; a registration means for receiving, if a registration item included in the registration request is not registered in user registration information about the user corresponding to the user information included in the registration request received by the receiving means, input of the registration item content from the user terminal and registering the registration item and the received content in the user registration information; and an issuing means for referencing the user registration information and issuing authentication information to the business server for authenticating the user corresponding to the user information included in the registration request.

According to the present invention, the program can easily register users on a business server even if the registration items required for registration differ between multiple business servers.

1 is a diagram illustrating an example of the overall configuration of an authentication registration system according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a hardware configuration of a server device illustrated in FIG. 1 . FIG. 2 is a diagram illustrating an example of a functional configuration of a server device illustrated in FIG. 1 . 2 is a diagram showing an example of user registration information stored in the server device shown in FIG. 1; FIG. FIG. 2 is a diagram showing an example of a processing flow in the authentication registration system shown in FIG. 1 . FIG. 2 is a diagram showing an example of a web page displayed on the user terminal shown in FIG. 1 . FIG. 2 is a diagram showing an example of a web page displayed on the user terminal shown in FIG. 1 . FIG. 2 is a diagram showing an example of a web page displayed on the user terminal shown in FIG. 1 . FIG. 2 is a diagram showing an example of a web page displayed on the user terminal shown in FIG. 1 .

Several embodiments of the present invention will be described below with reference to the accompanying drawings. To facilitate understanding, identical components and steps in each drawing will be designated by the same reference numerals whenever possible, and duplicate descriptions will be omitted.

<Overall structure>
1 is a diagram illustrating a schematic configuration of an authentication registration system 1 according to this embodiment. As shown in FIG. 1, the authentication registration system 1 mainly includes a server device 10, a user terminal 20, and a plurality of business server servers 30.

The server device 10 is an information processing device such as a desktop or laptop computer that can communicate with the user terminal 20 and the business server 30 via the communications network NT. The server device 10 accepts a registration request from the business server 30, performs user registration and authentication processing for the business server 30, and sends authentication information to the business server 30 if the user is successfully registered and authenticated, or sends an authentication result to the business server 30 indicating that registration and authentication are not possible if the user is not successfully registered or authenticated. Furthermore, during the user registration and authentication processing for the business server 30, the server device 10 requests input and instructions from the user terminal 20 as appropriate, accepts input and instructions from the user terminal 20, and performs the registration and authentication processing in accordance with the accepted input and instructions.

The user terminal 20 is a terminal device operated by a user, such as a mobile phone, smartphone, tablet, or personal computer. The user terminal 20 accepts user operations and executes processing in accordance with those operations. The user terminal 20 also transmits an authentication request to the business server 30 via the communications network NT. The user terminal 20 also accepts user inputs and instructions in response to requests for inputs and instructions transmitted from the server device 10 via the communications network NT, and transmits the inputs and instructions received from the user to the server device 10 via the communications network NT.

The business server 30 is an information processing device such as a desktop computer or laptop computer. The business server 30 transmits a registration request received from the user terminal 20 to the server device 10 via the communications network NT. If the server device 10 is able to register and authenticate the user, the business server 30 stores the user's authentication information transmitted from the server device 10 via the communications network NT, and provides the user terminal 20 with a service that corresponds to the case where the user has been authenticated. If the server device 10 is unable to register and authenticate the user, the business server 30 receives an authentication result from the server device 10 via the communications network NT indicating that the user could not be registered and authenticated, and transmits the authentication result to the user terminal 20.

<Hardware configuration>
Fig. 2 is a diagram illustrating an example of the hardware configuration of the server device 10 shown in Fig. 1. As shown in Fig. 2, the main part of the server device 10 includes, for example, a storage device 11, a CPU (Central Processing Unit) 12, a memory 13, and a communication device 14.

The storage device 11 is composed of a hard disk or the like. This storage device 11 stores various programs and information required for the CPU 12 to execute processing, as well as information on the processing results.

The CPU 12 functions as various functional means by executing predetermined programs stored in the memory 13 or storage device 11, etc. Details of these functional means will be described later.

Memory 13 temporarily stores predetermined programs and data required when the CPU 12 executes the predetermined programs.

The communication device 14 is composed of a communication interface for communicating with external devices. The communication device 14 transmits various information and requests to, for example, the user terminal 20 and the provider server 30. The communication device 14 also receives various information and requests from, for example, the user terminal 20 and the provider server 30.

The server device 10 can be realized using an information processing device such as a dedicated or general-purpose computer. The server device 10 may be configured from a single information processing device or multiple information processing devices. For example, the server device 10 may be configured from multiple information processing devices configured on a blockchain. Furthermore, Figure 2 only shows some of the main hardware components of the server device 10, and the server device 10 may also have other components that are generally included in a computer.

<Functional configuration>
Fig. 3 is a diagram showing an example of the functional configuration of the server device 10 shown in Fig. 1. As shown in Fig. 3, the server device 10 is configured to include, as functional components, a reception unit 110, an authentication unit 120, a registration unit 130, an authorization unit 140, an issuing unit 150, and a storage unit 160. The functional components other than the storage unit 160 are realized by the CPU 12 expanding and executing a program on the memory 13. The storage unit 160 is realized by the storage device 11 and/or the memory 13.

The reception means 110 receives a registration request from the business server 30, which includes user information about the user of the business server 30 and registration items for registration on the business server 30. The registration request also includes multiple registration items about the user. Here, the user information is, for example, information used to identify the user, such as an email address or user ID. The registration items are items set for each business server 30, and include items of information about the user that are necessary for the user to use the services of the business server 30 after the user has been registered.

The authentication means 120 performs authentication processing for the user corresponding to the user information accepted by the acceptance means 110. Specifically, if the user corresponding to the user information accepted by the acceptance means 110 is registered, the authentication means 120 authenticates the user as a registered user. Furthermore, if the user corresponding to the user information accepted by the acceptance means 110 is not registered, the authentication means 120 authenticates the user as a new, unregistered user.

The registration means 130 determines whether the registration items included in the registration request accepted by the acceptance means 110 are registered in the user registration information 161 for the user corresponding to the user information included in the registration request. If the registration items included in the registration request are not registered in the user registration information 161 for the user corresponding to the user information included in the registration request accepted by the acceptance means 110, the registration means 130 accepts input of the details of the registration items from the user terminal 20 and registers the registration items and the accepted details in the user registration information 161. The registration means 130 also registers, in the user registration information 161, any registration items not included in the user registration information 161, among the multiple registration items. The user registration information 161 will be explained later with reference to Figure 4, so its explanation will be omitted here.

The authorization means 140 performs processing related to authorization of the business server 30 when a registration item is included in the user registration information 161 or when registration is performed by the registration means 130. Details of the authorization processing will be explained later with reference to Figure 5, so a detailed explanation will be omitted here.

The issuing means 150 references the user registration information 161 and issues authentication information 162 to the business server 30 for authenticating the user corresponding to the user information included in the registration request. Furthermore, if the registration item is not included in the user registration information 161, the issuing means 150 issues the authentication information 162 after registration by the registration means 130. Furthermore, the issuing means 150 issues the authentication information 162 after authorization processing by the authorization means 140.

The storage means 160 stores various information that needs to be stored in the server device 10. Specifically, the storage means 160 stores, for example, user registration information 161 for each user and authentication information 162 for each user.

User registration information 161 will be described with reference to Figure 4. Figure 4 is a diagram showing an example of user registration information 161 stored by server device 10 shown in Figure 1. As shown in Figure 4, user registration information 161 is an information table containing multiple registration items and user-related information associated with each registration item. User registration information 161 is also configured to allow new registration items other than the predetermined registration items and user-related information associated with the new registration items to be added. Predefined registration items in user registration information 161 include, for example, ID, name, username, email address, gender, date of birth, telephone number, address, and blood type. New registration items that can be added to user registration information 161 may be any item as long as they are related to the user.

Returning to Figure 3, authentication information 162 is information indicating that a user has been authenticated, and is, for example, an ID token. Authentication information 162 includes, for example, information for identifying the user, information about the issuer of authentication information 162, information about the recipient of authentication information 162, registration items from user registration information 161 that are required to use the services of business operator server 30, and information about the user corresponding to those registration items, and is encoded in a predetermined format.

<An example of a series of processing steps>
The functional configuration of the server device 10 has been described above. Next, a series of processing flows of the server device 10 will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of a series of processing flows of the server device 10 shown in Fig. 1.

(Step SP10)
The user terminal 20 sends a registration request to the business server 30. Then, the process proceeds to step SP12.

(Step SP12)
The business entity server 30 accepts a registration request from the user terminal 20 and adds to the accepted registration request the registration items necessary for using the services of the business entity server 30. The business entity server 30 transmits to the server device 10 a registration request including the registration items added for registration at the business entity server 30. Then, the process proceeds to step SP14.

(Step SP14)
The server device 10 receives a registration request from the business server 30 via the reception means 110. The server device 10 then requests the user terminal 20 that sent the registration request to input user information via the authentication means 120. In Fig. 5, the server device 10 requests input of a user ID as the user information. Then, the process proceeds to step SP16.

(Step SP16)
The user terminal 20 receives a request for inputting user information transmitted from the server device 10 and displays the request on the screen to prompt the user to input the user information. An example of a specific process performed by the user terminal 20 when requesting input of user information will now be described with reference to FIG. 6 . FIG. 6 is a diagram illustrating an example of a web page 600 displayed on the user terminal 20 shown in FIG. 1 . The user terminal 20 displays the web page 600 transmitted from the server device 10 on the screen of the user terminal 20. The web page 600 includes, for example, a text box 601 for inputting a user ID and a button 602 for user registration or login. The user terminal 20 receives a user operation, and when the user ID is input into the text box 601 and the button 602 is selected, the user terminal 20 transmits the user information to the server device 10, taking the user ID as user information. Then, the process proceeds to step SP18.

(Step SP18)
The server device 10 receives user information transmitted from the user terminal 20 via the reception means 110. The server device 10 then performs authentication processing on the user corresponding to the received user information via the authentication means 120. Specifically, the server device 10 causes the authentication means 120 to refer to the storage means 160 and determine whether there is user registration information 161 corresponding to the user information received by the reception means 110. If the determination is affirmative, the server device 10 causes the authentication means 120 to authenticate the user who transmitted the registration request as the user corresponding to the user registration information 161. If the determination is negative, the server device 10 causes the authentication means 120 to authenticate the user who transmitted the registration request as a new, unregistered user, and generates new user registration information 161 corresponding to the user and stores it in the storage means 160. Then, the process proceeds to step SP20.

(Step SP20)
The server device 10 uses the registration means 130 to refer to the user registration information 161 of the user corresponding to the user information included in the registration request from the storage means 160. The server device 10 uses the registration means 130 to determine whether each of the registration items included in the registration request is included in the referenced user registration information 161. If the server device 10 determines using the registration means 130 that all of the registration items included in the registration request are included in the referenced user registration information 161, it transmits information indicating that the user is registered to the user terminal 20.

Here, referring to FIG. 8, we will explain the processing of the user terminal 20 when all registration items included in the registration request are included in the referenced user registration information 161. FIG. 8 is a diagram showing an example of a web page 800 displayed on the user terminal 20 shown in FIG. 1. As shown in FIG. 8, the web page 800 includes, for example, registration items required for registration on the business server 30, a registration information field 801 indicating whether each registration item has been registered, and a button 802 for transmitting confirmation of the registration information field 801. The user terminal 20 receives the web page 800 from the server device 10 and displays the web page 800 indicating that the user has been registered. The user terminal 20 receives selection of button 802 from the user and, in accordance with the selection of button 802, transmits information to the server device 10 confirming that the user has been registered. The server device 10 receives information confirming that the user has been registered from the user terminal 20. Returning to FIG. 5, the processing then proceeds to step SP28.

Furthermore, if the server device 10 determines via the registration means 130 that any one of the registration items included in the registration request is not included in the referenced user registration information 161, it transitions the processing to step SP22.

(Step SP22)
The server device 10, via the registration means 130, transmits to the user terminal 20 registration items necessary for using the services of the business server 30 that are not included in the user registration information 161, and requests the user terminal 20 to input information corresponding to the registration items not included in the user registration information 161. A specific process will be described with reference to FIG. 7 . FIG. 7 is a diagram illustrating an example of a web page 700 displayed on the user terminal 20 shown in FIG. 1 . As shown in FIG. 7 , the web page 700 includes, for example, a registration information field 701 indicating the registration items necessary for registration on the business server 30 and whether each registration item has been registered, a text box 702 for entering information corresponding to the unregistered registration items, and a button 703 for submitting the information corresponding to the registration items. The server device 10 transmits the web page 700 to the user terminal 20. Returning to FIG. 5 , the process then proceeds to step SP24.

(Step SP24)
The user terminal 20 displays registration items necessary for using the services of the provider server 30 that are not included in the user registration information 161 and receives input from the user of information corresponding to the registration items not included in the user registration information 161. The user terminal 20 transmits to the server device 10 information corresponding to the registration items not included in the user registration information 161 that has been input by the user. Specific processing will be described with reference to FIG. 7 . The user terminal 20 displays a web page 700 transmitted from the server device 10. The user terminal 20 receives information input into a text box 702 and selection of a button 703 from the user, and transmits the information input into the text box 702 to the server device 10 in accordance with the user's selection of the button 703. Returning to FIG. 5 , the processing proceeds to step SP26.

(Step SP26)
The server device 10 receives from the user terminal 20 information corresponding to registration items necessary for using the services of the business server 30 that are not included in the user registration information 161. The server device 10 registers the received information in the user registration information 161 of the user using the registration means 130. Then, the process proceeds to step SP28.

(Step SP28)
The server device 10, through the authorization means 140, requests the user terminal 20 to issue an instruction regarding whether or not to authorize the business entity's server 30 to access the user registration information 161, etc. stored in the server device 10. Then, the process proceeds to step SP30.

(Step SP30)
The user terminal 20 receives a request for an instruction regarding whether or not to authorize the provider's server 30 to access the server device 10, and displays a message on the screen prompting the user to input the instruction. The user terminal 20 receives an instruction regarding whether or not to authorize the provider's server 30 to access the server device 10 through user input, and transmits the received instruction to the server device 10. Then, the process proceeds to step SP32.

(Step SP32)
The server device 10 receives, via the authorization means 140, an instruction from the user terminal 20 regarding whether to authorize the provider server 30 to access the server device 10. If the received instruction indicates that the provider server 30 should not be authorized to access the server device 10, the server device 10 transmits, via the authorization means 140, information to the provider server 30 and the user terminal 20 indicating that authentication of the provider server 30 has been denied because authorization to the server device 10 has been denied, and terminates the series of processes shown in Fig. 5. Furthermore, if the received instruction indicates that the provider server 30 should be authorized to access the server device 10, the server device 10 causes the authorization means 140 to transition the process to step SP34.

(Step SP34)
The server device 10 generates an access token using the authorization means 140 in accordance with the user information included in the registration request, and transmits the generated access token to the business server 30. Here, the access token is information that includes the user information and information indicating that authorization to the server device 10 is permitted, and is information for permitting the user corresponding to the user information to access the server device 10. Then, the processing proceeds to step SP36.

(Step SP36)
The business server 30 accepts the access token transmitted from the server device 10. The business server 30 generates a request for authentication of the server device 10 in accordance with the access token, and transmits the generated request to the server device 10. The request includes at least a portion of the information contained in the access token. Then, the process proceeds to step SP38.

(Step SP38)
The server device 10 receives an authentication request from the business server 30 via the authorization means 140 and determines whether the received request is valid for authorization to the server device 10. If the server device 10 determines that the request is not valid for authorization to the server device 10, the authorization means 140 transmits information indicating that authorization to the server device 10 has been denied to the business server 30 and the user terminal 20, and the series of processes shown in Fig. 5 ends. If the server device 10 determines that the request is valid for authorization to the server device 10, the authorization means 140 causes the process to proceed to step SP40.

(Step SP40)
The server device 10 issues, via the issuing means 150, authentication information 162, which is information indicating that the user has been authenticated and authorized, to the server device 10. The server device 10 transmits the issued authentication information 162 to the business entity server 30 via the issuing means 150.

(Step SP42)
The business operator server 30 receives the authentication information 162 transmitted from the server device 10 and stores the received authentication information 162 in the business operator server 30. The business operator server 30 also transmits to the user terminal 20 information indicating that the authentication and authorization to the server device 10 has been successful.

The information transmitted by the provider server 30 to the user terminal 20 in step SP42 will be described with reference to FIG. 9. FIG. 9 is a diagram showing an example of a web page 900 displayed on the user terminal 20 shown in FIG. 1. As shown in FIG. 9, the web page 900 is intended to notify the server device 10 that authorization and authentication have been successful, and includes a button 901 for transmitting confirmation that authorization and authorization have been successful. The user terminal 20 displays the web page 900 transmitted from the server device 10. The user terminal 20 accepts the selection of button 901 from the user, and, in accordance with the user's selection of button 901, accesses the provider server 30 in a state in which user authentication and authorization have been completed. Returning to FIG. 5, the provider server 30 responds to various requests transmitted from the user terminal 20 in a manner that indicates that user authentication and authorization have been completed. The series of processes shown in FIG. 5 then ends.

In this embodiment, in the processing of step SP42, the business server 30 transmits information to the user terminal 20 indicating that authentication and authorization to the server device 10 have been successful, but this is not limited to this, and the information does not have to be transmitted to the server device 10. In this case, in the processing of step SP52, the business server 30 accepts the authentication information 162 transmitted from the server device 10, stores the accepted authentication information 162 in the business server 30, and then responds to various requests transmitted from the user terminal 20 in a manner that indicates that user authentication and authorization have been completed.

<Effects>
As described above, in this embodiment, the server device 10 receives, via the accepting means 110, a registration request from the business server 30, the registration request including user information about a user of the business server 30 and registration items for registration at the business server 30. Furthermore, if the registration items included in the registration request received by the accepting means 110 are not registered in the user registration information 161 about a user corresponding to the user information included in the registration request, the server device 10 receives, via the registration means 130, input of the registration items from the user terminal 20 and registers the registration items and the received content in the user registration information 161. Furthermore, the server device 10 references the user registration information 161 via the issuing means 150 and issues, to the business server 30, authentication information 162 for authenticating the user corresponding to the user information included in the registration request. Therefore, the server device 10 can easily register users at the business server 30 even if the registration items required for registration differ among multiple business servers 30.

Furthermore, in this embodiment, the registration request includes multiple registration items related to the user. Furthermore, the registration means 130 registers, in the user registration information 161, those registration items among the multiple registration items that are not included in the user registration information 161. Therefore, since the server device 10 registers only the registration items that are not included in the user registration information 161, the effort required to register registration items can be reduced when registration items overlap between business servers 30.

Furthermore, in this embodiment, if a registration item is not included in the user registration information 161, the issuing means 150 issues authentication information 162 after registration by the registration means 130. Therefore, when registration is performed by the registration means 130, the server device 10 issues authentication information 162 without accepting a new registration request sent from the business server 30, thereby reducing the effort and time required for the user when issuing authentication information 162.

In addition, in this embodiment, if the registration item is included in the user registration information 161 by the authorization means 140 or if registration is performed by the registration means 130, the server device 10 performs authorization processing on the registered information, etc. related to the user to the business server 30. Therefore, the server device 10 can perform not only authentication and registration but also authorization processing.

Furthermore, in this embodiment, the issuing means 150 issues authentication information 162 after the authorization process has been performed by the authorization means 140. Therefore, the server device 10 can improve the robustness of the authentication process using an authorized access token to access information about a user stored in the business operator server 30.

<Modification>
The present invention is not limited to the above-described embodiments. In other words, variations of the above-described embodiments, which are appropriately modified by a person skilled in the art, are also included within the scope of the present invention as long as they include the features of the present invention. Furthermore, the elements of the above-described embodiments and the modifications described below can be combined to the extent technically possible, and such combinations are also included within the scope of the present invention as long as they include the features of the present invention.

For example, in this embodiment, the server device 10 performs authorization processing using the authorization means 140, but this is not limited to this. After the authentication means 120 determines that a registration item is registered in the user registration information 161, or after the registration means 130 registers a registration item not included in the user registration information 161, the server device 10 may issue authentication information 162 using the issuing means 150 without performing authorization processing.

With this configuration, the server device 10 can easily register users on the business server 30 even when authorization processing is not required and the registration items required for registration differ between multiple business servers 30.

In addition, in this embodiment, the server device 10 uses an access token in the authorization process, but this is not limited to this. The server device 10 may use any method in the authorization process.

With this configuration, regardless of which method is used in the authorization process, the server device 10 can easily register users on the business server 30 even if the registration items required for registration differ between multiple business servers 30.

In addition, in this embodiment, the authentication registration system 1 includes a server device 10, a user terminal 20, and multiple business servers 30 that are communicatively connected via the communication network NT, but is not limited to this. For example, the authentication registration system 1 may not include the server device 10 and the business server 30, and may instead be composed only of multiple user terminals 20 that are connected to the cloud via the communication network NT. In this case, in the authentication registration system 1, each user terminal 20 will perform the functions and operations of both the server device 10 and the business server 30.

With this configuration, when various services are operated on a cloud that does not include a specific server such as the server device 10 or the provider server 30, the user terminal 20 can reduce the effort required for the user to register items when there are overlapping registration items between services.

10...server device, 20...user terminal, 30...business server, 110...receiving means, 130...registration means, 140...authorization means, 150...issuing means

Claims (5)

A computer that can communicate with the business server and the user terminal,
a receiving means for receiving, from the business server, a registration request including user information relating to a user of the business server and registration items for registration in the business server;
authentication means for performing authentication processing of the user corresponding to the user information accepted by the accepting means;
a registration means for, when a registration item included in the registration request received by the reception means is not registered in user registration information relating to the user corresponding to the user information included in the registration request, receiving input of the content of the registration item from the user terminal and registering the registration item and the received content in the user registration information;
an authorization means for performing a process related to authorization for the business server when the registration item is included in the user registration information or when registration is performed by the registration means;
issuing means for issuing authentication information indicating that the user has been authorized and authenticated to the business server;
A program that functions as a the registration request includes a plurality of registration items related to the user;
the registration means registers, in the user registration information, registration items that are not included in the user registration information among the plurality of registration items;
The program according to claim 1. If the registration item is not included in the user registration information, the issuing means issues the authentication information after registration by the registration means.
The program according to claim 2. the issuing means issues the authentication information after the authorization means has performed a process related to the authorization.
The program according to any one of claims 1 to 3 . An information processing device capable of communicating with a business server and a user terminal,
a receiving means for receiving, from the business server, a registration request including user information relating to a user of the business server and registration items for registration in the business server;
authentication means for performing authentication processing of the user corresponding to the user information received by the receiving means;
a registration means for, when a registration item included in the registration request received by the reception means is not registered in user registration information relating to the user corresponding to the user information included in the registration request, receiving input of the content of the registration item from the user terminal and registering the registration item and the received content in the user registration information;
an authorization means for performing a process related to authorization for the business server when the registration item is included in the user registration information or when registration is performed by the registration means;
issuing means for issuing authentication information indicating that the user has been authorized and authenticated to the business server;
An information processing device comprising: