JP2020154767A - Service providing device, service providing program, and service providing system - Google Patents

Abstract

To provide service to a regular user who is already registered as a user who receives the service.SOLUTION: A service providing device uses a token received from an affiliated authentication management device to confirm that service registration information on the user corresponding to the token is already registered, confirms whether a request for service is a request from the user represented with the service registration information, and then performs control to provide the service that the user requests on condition that it is confirmed that the service registration information corresponding to the token is already registered and the request for the service is the request from the user represented with the service registration information.SELECTED DRAWING: Figure 2

Description

The present invention relates to a service providing device, a service providing program, and a service providing system.

Patent Document 1 describes a system in which a first service system including a first management server and a second service system including a second management server cooperate with each other to provide services. The management server includes a means for performing user authentication and acquiring tenant information indicating the tenant to which the authenticated user belongs, and a means for making a client registration request to the second service system. The management server includes means for sending a registration result including client registration according to the client registration request and group information indicating a group to which the authenticated user belongs to the first management server, and the first management server. Is provided with means for receiving the group information and storing the received group information in association with the tenant information of the authenticated user, and the second management server responds to the authentication request from the registered client. The first management server is provided with means for sending ID information including group information of authenticated users to the first management server, and the first management server receives the ID information and has an account corresponding to the account indicated by the received ID information. A service providing system is disclosed, which comprises means for determining the above and means for generating a new account when the determination means determines that the account does not exist.

Patent Document 2 describes a server device that can communicate with a terminal device via a network, and receives user information including a unique ID of a user of the terminal device from the terminal device and a receiving means by the receiving means. The unique ID included in the user information including the attribute information specified by the terminal device among the specified user information and the uniqueness of the user included in the user information including the attribute information among the user information authenticated by the server device. A server device having a generation means for generating ID mapping information related to authentication cooperation between the terminal device and the server device by associating with an ID is disclosed.

Japanese Unexamined Patent Publication No. 2016-57737 Japanese Unexamined Patent Publication No. 2016-85638

There is known an authentication management device that cooperates with a plurality of service providing devices and authenticates a service provided by each service providing device with one authentication information set by a user.

If the authentication management device does not take measures to deal with the unauthorized change of the authentication information, the administrator of the malicious authentication management device illegally changes the user's authentication information, and the administrator etc. It is conceivable to impersonate the user who changed the authentication and illegally enjoy the service of the service providing device.

According to the present invention, when the user authentication of the provided service is performed in cooperation with the authentication management device, the user who receives the service is provided even if the authenticity of the authentication information registered in the authentication management device is not guaranteed. It is an object of the present invention to provide a service providing device, a service providing program, and a service providing system capable of providing a service to a legitimate user registered in advance as.

The service providing device according to the first aspect uses the management information received from the authentication management device that supports the authentication of a plurality of affiliated services, and confirms whether the user registration information corresponding to the management information has been registered. At the same time, a confirmation unit that confirms whether the service request is a request from the user represented by the registration information. The registration information has already been registered in the confirmation unit, and the service request is represented by the registration information. It is provided with a control unit that controls the provision of the service requested by the user when it is confirmed that the request is from the user.

The service providing device according to the second aspect is the service providing device according to the first aspect, and the confirmation unit registers the management information received from the authentication management device in a management table that manages the registration information for each user. If not, it is confirmed whether the service request is a request from the user represented by the registration information by using the contact information included in the management information received from the authentication management device.

In the service providing device according to the third aspect, when the contact information included in the management information is an e-mail address in the service providing device according to the second aspect, the confirmation unit transmits the service to the e-mail address. By accepting the consent notification that approves the use of the service in response to the confirmation e-mail confirming whether the user is the user who requested the service, it is confirmed that the request for the service is a request from the user represented by the registration information.

The service providing device according to the fourth aspect is the service providing device according to any one of the first to third aspects, and the confirmation unit is the password for the registration information when the registration information has already been registered. Is requested to the user, and when the entered password is the same as the password of the registration information, it is confirmed that the service request is a request from the user represented by the registration information, and the control unit determines. , Controls associating the management information received from the authentication management device with the registration information.

The service providing device according to the fifth aspect is the service providing device according to any one of the first to fourth aspects, and the confirmation unit uses the identifier of the registered information including the management ID of the management information as the identifier. If the contact information included in the management information is different from the contact information, a password is requested, and if the obtained password is the same as the password of the registration information, the service request is represented by the registration information. After confirming that the request is from the user, the control unit controls to change the identifier of the registration information to the contact information of the management information received from the authentication management device.

The service providing device according to the sixth aspect is the service providing device according to the fifth aspect, and the confirmation unit requests the input of the contact information included in the management information in addition to the password of the registration information. When the password obtained is the same as the password of the registration information and the contact obtained is the same as the contact included in the management information, the service request is from the user represented by the registration information. Confirm that it is a request.

The service providing device according to the seventh aspect is the service providing device according to any one of the first to sixth aspects, when the service request is received from the user without going through the authentication management device. The control unit controls to release the association between the management information and the registration information when the management information of the user who requested the service from the authentication management device is requested but the management information is not obtained. I do.

The service providing device according to the eighth aspect is the service providing device according to any one of the first to seventh aspects, and the control unit is predetermined from the authentication associated with the use of the provided service for each user. When the period has elapsed, control is performed to cancel the association between the management information of the user whose predetermined period has passed and the registration information.

The service providing device according to the ninth aspect is the service providing device according to any one of the first to eighth aspects, and the confirmation unit receives from the authentication management device whose authenticity of information is guaranteed. Treat management information as correct information for the user who requested the service.

The service providing program according to the tenth aspect is a program for causing the computer to function as each part of the service providing device according to any one of the first to ninth aspects.

The service providing system according to the eleventh aspect registers the service providing device according to any one of the first to ninth aspects, and management information including an identifier for identifying the user and the contact information of the user for each user. When the registered user requests the service provided by the service providing device, the management information of the user requesting the service is transmitted to the service providing device, and the service providing device is linked with the service providing device. Includes an authentication management device that assists in authenticating a user requesting a service with the service providing device.

According to the first aspect, the tenth aspect, and the eleventh aspect, the authenticity of the authentication information registered in the authentication management device is not guaranteed when the user authentication of the provided service is performed in cooperation with the authentication management device. Even in this case, it has the effect that the service can be provided to a legitimate user who is registered in advance as a user who receives the service.

According to the second aspect, even when the administrator of the authentication management device tries to access the service providing device by impersonating a user who is not registered in the service providing device, the management information received from the authentication management device is displayed. It has the effect of being able to determine whether the management information is correct for the user who requested the service.

According to the third aspect, there is an effect that it is possible to confirm whether the service is requested from the user from the service providing device.

According to the fourth aspect, even when the same management information as the management information included in the registration information managed by the service providing device is received from the authentication management device, the user who requested the service responds to the registration information. It has the effect of further confirming that the user is the correct user and associating the management information with the registration information.

According to the fifth aspect, even when a contact different from the identifier of the registration information managed by the service providing device is received from the authentication management device, the user who requested the service is managed by the service providing device. It has the effect of confirming that the user is the correct user corresponding to the registered information and changing the identifier of the registered information to the contact information of the management information.

According to the sixth aspect, it is strictly confirmed whether the user who requested the service is the correct user corresponding to the registration information managed by the service providing device, as compared with the case where the identity is confirmed only by the password. It has the effect of being able to.

According to the seventh aspect, when the user cancels the usage contract of the cooperation authentication to the service providing device using the authentication management device, the information regarding the cooperation with the authentication management device stored in the service providing device. Has the effect of being able to delete.

According to the eighth aspect, even if the user who has canceled the usage contract of the linked authentication to the service providing device using the authentication management device does not use the service provided by the service providing device, it is stored in the service providing device. It has the effect that the information related to the cooperation with the authentication management device that has been performed can be deleted.

According to the ninth aspect, there is an effect that the identity verification performed every time the service is used can be omitted for the user who is considered not to be impersonating.

It is a figure which shows the system configuration example of the service providing system. It is a sequence diagram which showed an example of the flow of authentication in a service providing system. It is a figure which shows an example of the reception screen of a service providing apparatus. It is a block diagram which shows the functional configuration example of the authentication management apparatus. It is a figure which shows an example of the authentication management table. It is a block diagram which shows the functional configuration example of a service providing apparatus. It is a figure which shows an example of a service management table. It is a block diagram which shows the functional configuration example of a user apparatus. It is a figure which shows the example of the main part composition of the electric system in an authentication management device, a service providing device, and a user device. It is a flowchart which shows an example of the flow of the service provision process in a service provision apparatus. It is a flowchart which shows an example of the flow of the account creation process in a service providing apparatus. It is a flowchart which shows an example of the flow of ID association processing in a service providing apparatus. It is a flowchart which shows an example of the flow of ID change processing in a service providing apparatus. This is an example of a flowchart showing the flow of updating the service management table in the service providing device. This is an example of a flowchart showing the flow of periodic update processing of the service management table in the service providing device.

Hereinafter, the present embodiment will be described with reference to the drawings. The components and processes having the same function are given the same code throughout the drawings, and duplicate description is omitted.

FIG. 1 is a diagram showing a system configuration example of the service providing system 1 according to the present embodiment. The service providing system 1 includes an authentication management device 10, a service providing device 20, and a user device 30, and the authentication management device 10, the service providing device 20, and the user device 30 are each connected by a communication line 2.

The communication line 2 may be a wired line or a wireless line, or may be a line in which a wired line and a wireless line are mixed. Further, the communication line 2 may be a dedicated line or a public line that shares a line with an unspecified number of devices such as the Internet.

The authentication management device 10 manages the authentication information of the user registered in the authentication management device, and when the user registered in the authentication management device 10 uses the service provided by the service providing device 20, the authentication management device 10 manages the authentication information. It is a device that provides an authentication service that enables the service providing device 20 to authenticate the user by notifying the service providing device 20 of the authentication information of the user.

That is, the authentication management device 10 uses the service provided by the service providing device 20 with common authentication information if the service providing device 20 is affiliated with the authentication management device 10 for the user registered in the authentication management device 10. Achieve a Single Sign On (SSO) function that allows. Hereinafter, the authentication of the service providing device 20 in cooperation with the authentication management device 10 will be referred to as "cooperation authentication".

The service providing device 20 affiliated with the authentication management device 10 is a service providing device 20 that authenticates a user by using linked authentication with the authentication management device 10. The authentication management device 10 manages the authentication information of the user who uses the linked authentication.

Hereinafter, since the cooperative authentication is used, the identifier used for the authentication performed by the authentication management device 10 when the user accesses the authentication management device 10 is referred to as "management ID (Identification)". Further, since the user receives the service without using the cooperative authentication, the identifier used for the authentication performed by the service providing device 20 when the user directly accesses the service providing device 20 is referred to as the "service ID".

When the user requests the service, the service providing device 20 authenticates whether the user who requested the service is a registered user registered in advance in the service providing device 20, and performs the requested service after the authentication is completed. It is a device to be provided. There are no restrictions on the content of the service provided by the service providing device 20, and any content may be used as long as the service is accepted through the communication line 2.

In order for the user to use the service provided by the service providing device 20 by using the cooperative authentication, the user accesses the authentication management device 10 in advance. In order for the user to use the service provided by the service providing device 20 without using the cooperation authentication, the service providing device 20 may be accessed, the user registration may be performed, and the service ID may be registered in the service providing device 20.

Although the example of the service providing system 1 shown in FIG. 1 includes only one service providing device 20, the service providing system 1 may include a plurality of service providing devices 20 affiliated with the authentication management device 10. In this case, once the user is authenticated by the authentication management device 10, the authenticated user can receive the service provided by each service providing device 20.

The information used for authentication of the authentication management device 10 and the service providing device 20 is not only the management ID and the service ID, but also confidential information known only to the user associated with each ID, that is, a password. The password associated with the management ID is called a "management password", and the password associated with the service ID is called a "service password". Further, the management ID and management password used for authentication of the authentication management device 10 are collectively referred to as "management login information", and the service ID and service password used for authentication of the service providing device 20 are collectively referred to as "service login information". ..

The user device 30 is a device operated by a user who uses the service provided by the service providing device 20, and connects to the authentication management device 10 or the service providing device 20 through the communication line 2 to request a service. When the requested service is provided through the communication line 2, for example, the provision of support information of the device purchased by the user, the user device 30 receives the service provision from the service providing device 20 and notifies the user.

That is, the user device 30 is subjected to data communication through an input / output function that provides an interface with a user, a processing function that processes information, and a communication line 2, such as a desktop computer, a tablet computer, a smartphone, and a wearable terminal. An information device equipped with a communication function to perform is used.

FIG. 2 is a sequence diagram showing an example of the authentication flow in the service providing system 1. The authentication process of the service providing device 20 using the cooperative authentication will be described with reference to FIG.

When the user connects the user device 30 to the service providing device 20 through the communication line 2, the reception screen 35 for receiving the service login information is displayed on the user device 30.

FIG. 3 is a diagram showing an example of a reception screen 35 of the service providing device 20 that receives service login information. The reception screen 35 includes a service ID input area 36 for inputting a service ID, a service password input area 37 for inputting a service password, and a login button 38. When the user enters the service ID and service password in each area and presses the login button 38 instructing the start of the authentication process using the entered service ID and service password, the service providing device does not use the linked authentication. Authentication is performed at 20. In this way, the user inputs the service ID and the service password registered in advance in the service providing device 20 into the service ID input area 36 and the service password input area 37 of the reception screen 35 to be authenticated by the service providing device 20. It is called "direct authentication".

On the other hand, the reception screen 35 also includes a link character string 39 displayed as, for example, "login by the authentication management service". The link character string 39 is associated with a URL (Uniform Resource Locator) that displays a reception screen (not shown) of the authentication management device 10 that receives management login information.

When the user presses the link character string 39 instead of entering the service ID and service password on the reception screen 35, a login request using linked authentication is notified to the service providing device 20 (FIG. 2: F1), and the authentication management device. A redirect (FIG. 2: F2) is performed so that the login screen (not shown) of 10 is displayed. As a result, the service providing device 20 for which the login request using the cooperative authentication is made by the authentication management device 10 is grasped, and the login screen of the authentication management device 10 is displayed on the user device 30 (Fig.). 2: F3).

When the user inputs the management login information on the login screen (not shown) of the authentication management device 10 displayed on the user device 30, the management login information is transmitted to the authentication management device 10 (FIG. 2: F4).

The authentication management device 10 that has received the management login information authenticates whether or not the combination of the management ID and the management password included in the management login information is registered in the authentication management device 10 in advance. When the authentication management device 10 determines that the management login information includes a combination of the management ID and the management password of the user registered in advance, the authentication management device 10 uses the linked authentication to provide the service provided by the service providing device 20. Recognize that there is a login request from the user.

Therefore, the authentication management device 10 gives the user who has requested the login the authority to connect to the service providing device 20 and generates a token. Then, the authentication management device 10 performs a redirect accompanied by a token in order to allow the service providing device 20 that made the redirect request to the authentication management device 10 in F2 of FIG. 2 to take over the subsequent authentication processing (FIG. 2: 2: F5). The "token" is management information including the user's management ID and the user's contact information managed in the authentication management device 10. However, the information contained in the token is not limited to this, and other information used for cooperative authentication may be included as needed.

The service providing device 20 that has received the token verifies the token in order to perform an authentication process for the user represented by the token by using the management ID included in the token.

Then, the service providing device 20 makes a confirmation request to the user associated with the management ID in order to confirm whether the service request is made by the user represented by the management ID notified by the token ( FIG. 2: F6). The method of confirming whether the user is the user who actually requested the service differs depending on the registration status of the management ID included in the token in the service providing device 20. The method of identity verification for confirming whether the user represented by the management ID notified by the token is the user who requested the service to the service providing device 20 will be described in detail later.

Upon receiving confirmation information indicating who the user is from the user device 30 for which the user confirmation request is requested, the service providing device 20 confirms the identity of the user. The service providing device 20 manages the registration information for associating or canceling the association between the management ID and the service ID according to the confirmation result, and the user represented by the management ID notified by the token is assigned to the service providing device 20. When the user who requested the service is authenticated, the service is provided to the user through the user device 30 that has transmitted the confirmation information.

In the sequence diagram shown in FIG. 2, when the user makes a login request to the service providing device 20, the user inputs the management login information to the login screen (not shown) of the authentication management device 10 displayed on the user device 30, and the authentication management device. Although the authentication with 10 has been performed, the user may authenticate with the authentication management device 10 before making a login request to the service providing device 20. In this case, the user makes a login request to the authentication management device 10, and if the user authentication is completed before the authentication management device 10 accepts the redirect shown in F2 of FIG. 2, the login screen is displayed on the user device 30. Token is generated without controlling the display of.

Next, a functional configuration example of each device included in the service providing system 1 will be described.

FIG. 4 is a block diagram showing a functional configuration example of the authentication management device 10. As shown in FIG. 4, the authentication management device 10 includes each functional unit of the user interface (UI) unit 11, the control unit 12, and the communication unit 13, and the authentication management database (Database: DB) 14.

The UI unit 11 receives instructions from the administrator who manages the authentication management device 10, and notifies the administrator of various information such as the authentication status and the authentication result in the authentication management device 10, for example.

The control unit 12 controls the authentication management device 10 so that the corresponding processing is performed according to the instruction received from the UI unit 11 and the information received from the communication unit 13. Specifically, when the control unit 12 receives the management login information from the user device 30, the control unit 12 generates a token by referring to the authentication management DB 14, and manages the registration information including the registered management login information for each user. Take control.

The communication unit 13 transmits and receives various information to and from each device connected to the communication line 2 under the control of the control unit 12.

The authentication management DB 14 stores an authentication management table 16 that manages registration information used for authentication of a user who uses linked authentication. Hereinafter, the registration information stored in the authentication management DB 14 will be referred to as "management registration information".

FIG. 5 is a diagram showing an example of the authentication management table 16 that manages the management registration information. As shown in FIG. 5, the authentication management table 16 includes management registration information for each user, and the management registration information includes a user name, management login information, and contact information.

The user name set in the authentication management device 10 by the user is set as the user name in the management registration information. Further, the management ID of the user is set in the management ID included in the management login information of the management registration information, and the password corresponding to the management ID is set in the management password.

Further, for example, a user's e-mail address is set as the contact information of the management registration information.

The items included in the management registration information are not limited to the items shown in FIG. 5, and other items may be included according to the contents of the cooperative authentication provided by the authentication management device 10. For example, the registration time when the user registers the management ID and the management password in the authentication management device 10, the number of times the service is used for each service providing device 20 used by the user (the number of times the service is connected to the service providing device 20), and the date of birth of the user. Etc. may be included in the management registration information.

The management password is encrypted and set in the management registration information so that even the administrator does not know what value is set.

FIG. 6 is a block diagram showing a functional configuration example of the service providing device 20. As shown in FIG. 6, the service providing device 20 includes each functional unit of the UI unit 21, the control unit 22, the communication unit 23, and the confirmation unit 24, and the service management DB 25.

The UI unit 21 receives instructions from the provider who provides the service using the service providing device 20, and also provides the service provider with various information such as the authentication status, the authentication result, and the service providing status in the service providing device 20. Notice.

The control unit 22 controls the service providing device 20 so that the corresponding processing is performed according to the instruction received from the UI unit 21 and the information received from the communication unit 23. Specifically, when the control unit 22 receives the token from the authentication management device 10, the control unit 22 verifies the token with reference to the service management DB 25, and when the confirmation unit 24 described later confirms the identity of the user. , Perform control to provide the requested service.

The communication unit 23 transmits and receives various information to and from each device connected to the communication line 2 under the control of the control unit 22.

The confirmation unit 24 uses the registration information stored in the service management DB 25 and the management ID included in the token to confirm the identity of the user who requested the service to confirm whether the user who requested the service is the user who is registered in the service providing device 20. To execute.

The service management DB 25 stores registration information used for user authentication in the service providing device 20. Hereinafter, the registration information stored in the service management DB 25 will be referred to as "service registration information".

FIG. 7 is a diagram showing an example of a service management table 26 that manages service registration information. As shown in FIG. 7, the service management table 26 includes service registration information for each user, and the service registration information includes a user name, a service ID, a service password, a management ID, and a login time.

The user name registered by the user in the service providing device 20 is set as the user name of the service registration information. The service ID registered by the user in the service providing device 20 is set as the service ID of the service registration information. The user's e-mail address is set in the service ID. The service password registered by the user in the service providing device 20 is set as the service password of the service registration information. As the management ID of the service registration information, a management ID registered by the user in the authentication management device 10 that provides cooperative authentication in cooperation with the service providing device 20 is set. The login time of the service registration information is set to the time when the user is authenticated by the service providing device 20 by the previous login request made to the service providing device 20 by the user.

The user name, service ID, and service password registered by the user in the service providing device 20 are set in the user name, service ID, and service password of the service registration information, respectively, but the management ID of the service registration information is set. The management ID included in the token received from the authentication management device 10 is set. Further, the login time of the service registration information is updated by the service providing device 20 every time the user is authenticated by the service providing device 20.

The items included in the service registration information are not limited to the items shown in FIG. 7, and other items may be included according to the content of the authentication performed by the service providing device 20. Items used to verify the identity of the user may be included, for example, the date of birth of the user.

The service management table 26 that manages the service registration information is an example of the management table according to the present embodiment.

FIG. 8 is a block diagram showing a functional configuration example of the user device 30. As shown in FIG. 8, the user device 30 includes each functional unit of the UI unit 31, the control unit 32, and the communication unit 33.

The UI unit 31 receives instructions from the user who operates the user device 30, and notifies the user of various information such as, for example, the processing status of a login request to the service providing device 20.

The control unit 32 controls the user device 30 so that the corresponding processing is performed according to the instruction received from the UI unit 31 and the information received from the communication unit 33.

The communication unit 33 transmits and receives various information to and from each device connected to the communication line 2 under the control of the control unit 32.

Next, an example of a main configuration of an electric system in each device included in the service providing system 1 will be described.

FIG. 9 is a diagram showing an example of a main part configuration of an electric system in the authentication management device 10. The authentication management device 10 is configured by using, for example, a computer 40.

The computer 40 is a CPU (Central Processing Unit) 41 that is responsible for each functional unit related to the authentication management device 10, and a ROM (Read Only Memory) that stores an authentication management program for making the computer 40 function as each functional unit of the authentication management device 10. ) 42, a RAM (Random Access Memory) 43 used as a temporary work area of the CPU 41, a non-volatile memory 44, and an input / output interface (I / O) 45. The CPU 41, ROM 42, RAM 43, non-volatile memory 44, and I / O 45 are connected to each other via the bus 46.

The non-volatile memory 44 is an example of a storage device in which the stored information is maintained even if the power supplied to the non-volatile memory 44 is cut off. For example, a semiconductor memory is used, but a hard disk may be used. The non-volatile memory 44 does not necessarily have to be built in the computer 40, and may be a storage device that is attached to and detached from the computer 40, such as a memory card.

For example, a communication unit 47, an input unit 48, and an output unit 49 are connected to the I / O 45.

The communication unit 47 is connected to the communication line 2 and includes a communication protocol for performing data communication with each device connected to the communication line 2.

The input unit 48 is a device that receives an instruction from the administrator and notifies the CPU 41, and for example, a button, a touch panel, a keyboard, a mouse, and the like are used. The authentication management device 10 executes a function instructed by the administrator via the input unit 48.

The output unit 49 is a device that displays information processed by the CPU 41, and for example, a liquid crystal display, an organic EL (Electro Luminescence) display, or the like is used.

The type of unit connected to the I / O 45 of the authentication management device 10 is an example, and the I / O 45 of the authentication management device 10 includes a printer unit that forms an image on a recording medium such as paper, if necessary, and a printer unit. A unit (not shown) may be connected to the memory card, such as an interface unit including a card slot for reading / writing data and a USB (Universal Serial Bus) port.

The example of the main part configuration of the electric system in the service providing device 20 and the user device 30 is the same as the main part configuration example of the electric system in the authentication management device 10 shown in FIG. 9, and the service providing device 20 uses the computer 50. The user device 30 is configured using the computer 60.

Therefore, in the service providing device 20, the CPU 41, ROM 42, RAM 43, non-volatile memory 44, I / O 45, bus 46, communication unit 47, input unit 48, and output unit 49 of the authentication management device 10 are used in the CPU 51, ROM 52, and ROM 52, respectively. The RAM 53, the non-volatile memory 54, the I / O 55, the bus 56, the communication unit 57, the input unit 58, and the output unit 59 are read as, and the person who operates the input unit 48 is changed from the administrator of the authentication management device 10 to the service providing device 20. Read as the service provider.

Further, in the user device 30, the CPU 41, ROM 42, RAM 43, non-volatile memory 44, I / O 45, bus 46, communication unit 47, input unit 48, and output unit 49 of the authentication management device 10 are used in the CPU 61, ROM 62, and RAM 63, respectively. , Non-volatile memory 64, I / O 65, bus 66, communication unit 67, input unit 68, and output unit 69, and the person who operates the input unit 68 is read from the administrator of the authentication management device 10 to the user.

Next, in order for the user to make a login request from the user device 30 to the service providing device 20 using cooperative authentication, the user device 30 is pressed by pressing the link character string 39 included in the reception screen 35 shown in FIG. The operation of the service providing device 20 after inputting the management login information on the login screen displayed on the output unit 69 will be described.

FIG. 10 is a flowchart showing an example of a flow of service provision processing executed by the CPU 51 of the service providing device 20 after the management login information is input to the user device 30. The service providing program that defines the service providing process is stored in advance in, for example, the ROM 52 of the service providing device 20. The CPU 51 of the service providing device 20 reads the service providing program stored in the ROM 52 and executes the service providing process.

It is assumed that the management registration information of the user who made the login request is registered in the authentication management table 16 managed by the authentication management DB 14 of the authentication management device 10. Hereinafter, unless otherwise specified, the service providing device 20 for which the login request using the cooperative authentication is made is simply referred to as the "service providing device 20".

As described with reference to FIG. 2, when the authentication management device 10 receives the management login information from the user device 30, the authentication management device 10 acquires the management registration information including the same management login information as the received management login information from the authentication management table 16. .. Then, the authentication management device 10 generates a token including the management ID and the contact information set in the acquired management registration information, and transmits the generated token to the service providing device 20 (FIG. 2: F5). The authentication management device 10 transmits a token to the service providing device 20 that has redirected (FIG. 2: F2) to a login request using the user's cooperative authentication.

Therefore, in step S10, the CPU 51 determines whether or not the token has been accepted from the authentication management device 10. If the token is not accepted, the determination process of step S10 is repeatedly executed to monitor the token. On the other hand, when the token is accepted, the process proceeds to step S20.

In step S20, the CPU 51 determines whether or not the service registration information in which the same service ID as the contact included in the token is set is registered in the service management table 26 stored in the service management DB 25. The service management DB 25 is built in, for example, the non-volatile memory 54 of the service providing device 20, but may be built in an external storage device connected to the service providing device 20 by the communication line 2.

If the service registration information in which the same service ID as the contact included in the token is set is not included in the service management table 26, the process proceeds to step S25.

In step S25, the CPU 51 determines whether or not the service registration information in which the management ID included in the token is set is registered in the service management table 26. If the service registration information in which the management ID included in the token is set is not registered in the service management table 26, the user who made the login request registers the service login information of the service providing device 20 in the authentication management device 10. However, it means a user whose service login information is not registered in the service providing device 20, that is, an unregistered user who is registered in the authentication management device 10 but not registered in the service providing device 20.

Therefore, the process proceeds to step S30, and the CPU 31 executes an account creation process for registering the user in the service providing device 20.

The contact information included in the token is an item of management registration information managed by the authentication management device 10, but some measures are taken to prevent unauthorized changes to the management registration information by the authentication management device 10. If not, it cannot be said that the contact included in the token is the correct contact of the user who requested the service from the service providing device 20. Therefore, in the account creation process of step S30, the user is registered in the service providing device 20 after confirming that the contact included in the token is the correct contact of the user who requested the service from the service providing device 20.

FIG. 11 is a flowchart showing an example of the flow of the account creation process executed in step S30 of FIG.

Since the contact included in the token is the user's email address, in step S100, the CPU 51 generates a confirmation email addressed to the contact included in the token. In the confirmation email, for example, "If you are the person who made the login request to the service provider, please access the service provider and enter the service login information. If you have not made the login request to the service provider. Please do not access the service provider. " Further, in the confirmation email, for example, a URL for connecting to the service providing device 20 is described together with the above message.

In step S110, after transmitting the confirmation email generated in step S100, the CPU 51 activates a timer for measuring the elapsed time from the transmission of the confirmation email, for example, by using the timer function built in the CPU 51.

As a result, a confirmation email is sent to the user device 30 that receives the email addressed to the contact included in the token.

If the user who received the confirmation email is the user who requested the service from the service providing device 20, he / she connects to the service providing device 20 by pressing the URL for connecting to the service providing device 20 described in the confirmation email. When the URL described in the confirmation email is pressed to connect to the service providing device 20, a confirmation screen (not shown) is displayed.

On the confirmation screen, for example, a consent button for notifying that the user who requested the service to the service providing device 20 is the user himself / herself and consenting to use the service, and a notification for not being the user who requested the service to the service providing device 20. A caution button is placed.

Therefore, in step S120, the CPU 51 determines whether or not the consent notification notified when the consent button is pressed has been accepted, and if the consent notification is received, the timer is stopped and the process proceeds to step S130.

When the consent button is pressed, the CPU 51 displays an account registration screen (not shown) and prompts the user to input the user name and service login information.

Therefore, in step S130, the CPU 51 determines whether or not the service login information has been accepted through the account registration screen. If the service login information is not accepted, the determination process of step S130 is repeatedly executed to monitor the input status of the service login information. On the other hand, when the service login information is received, the process proceeds to step S140.

From the above, it was confirmed that the user who received the confirmation email was the user who requested the service from the service providing device 20, and that the contact information included in the token was the correct email address of the user who requested the service. It will be. Therefore, in step S140, the CPU 51 sets the contact information included in the token as the service ID, associates the management ID included in the token with the service password and user name of the service login information received through the account registration screen, and said that. Generate user service registration information.

In step S150, the CPU 51 sets the value of the login flag. The login flag is a flag indicating whether or not to allow the user who has made the login request to provide the service. For example, when the login flag is set to "0", it means that the service is not permitted, and when "1" is set, it means that the service is allowed to be provided. In this case, since it was confirmed that the user who received the confirmation email was the user who requested the service from the service providing device 20, the CPU 51 sets the login flag to "1" and ends the account creation process shown in FIG. To do.

On the other hand, if it is determined in the determination process of step S120 that the consent notification is not accepted, the process proceeds to step S160.

Since the confirmation email states that if the user who received the confirmation email is not the user who requested the service from the service providing device 20, the CPU 51 does not connect to the service providing device 20 even if the confirmation email is sent. A situation occurs in which no notification is received from the user device 30. Therefore, in step S160, the CPU 51 determines whether or not the elapsed time of the timer started in step S110 has elapsed a predetermined standby time.

If the elapsed time of the timer has elapsed the standby time, the timer is stopped and the process proceeds to step S180.

In this case, since it is determined that the user who received the confirmation email is not the user who requested the service from the service providing device 20, the CPU 51 sets the login flag to "0" and ends the account creation process in step S180. ..

On the other hand, if it is determined in the determination process of step S160 that the elapsed time of the timer has not reached the standby time, the process proceeds to step S170.

If the confirmation e-mail states that the user who received the confirmation e-mail is not the user who requested the service from the service providing device 20, even if it is stated not to connect to the service providing device 20, it is erroneously stated that the service is not requested. There is a user who connects to the service providing device 20. Even in such a case, since the confirmation screen displayed when the service providing device 20 is connected has a caution button for notifying that the user is not the user who requested the service to the service providing device 20, the user. May press the caution button.

Therefore, in step S170, the CPU 51 determines whether or not the caution notification notified when the caution button is pressed has been accepted, and if the caution notification is received, the timer is stopped and the process proceeds to step S180.

In this case, since it is determined that the user who received the confirmation email is not the user who requested the service from the service providing device 20, the CPU 51 sets the login flag to "0" and ends the account creation process in step S180. ..

If it is determined in the determination process of step S170 that the caution notification is not accepted, the process proceeds to step S120 to accept the consent notification, the caution notification, or the elapsed time of the timer has elapsed. The determination process of steps S120, S160, and S170 is repeatedly executed until this is done. As a result, the account creation process shown in FIG. 11 is completed, and the service provision process of FIG. 10 is continued.

On the other hand, in the determination process of step S25 of FIG. 10, when the service registration information in which the management ID included in the token is set is registered in the service management table 26, the process proceeds to step S60. The fact that the same service ID as the contact information of the user who made the login request in the service registration information is not registered but the management ID is registered means that the management registration registered in the authentication management table 16 of the authentication management device 10 The contact information may have changed. Therefore, in step S60, the CPU 51 executes the ID change process.

FIG. 13 is a flowchart showing an example of the flow of the ID change process executed in step S60 of FIG.

In step S300, the CPU 51 displays a screen requesting input of the service login information set for using the service on the output unit 69 of the user device 30 that has made the login request, and requests the input of the service login information.

The CPU 51 activates a timer that measures the elapsed time from requesting the input of the service login information in step S300.

In step S310, the CPU 51 determines whether or not the service login information has been accepted. When the service login information is received, the timer is stopped and the process proceeds to step S320.

In step S320, the CPU 51 receives the service login information service password that matches the service password of the service registration information for which the management ID included in the token is set, and the received service login information service ID is the token. Determine if it matches the contacts contained in. If the entered service password and service ID match, the process proceeds to step S330.

In this case, the user who is requested to enter the service login information knows the service password set for the service ID, and also uses the changed contact information registered in the authentication management table 16 of the authentication management device 10. You will know. That is, it is confirmed that the contact information included in the token is the correct contact information of the user who requested the service from the service providing device 20, and the user who entered the service login information is the user who requested the service from the service providing device 20. Will be done.

Therefore, in step S330, the CPU 51 changes the service ID of the service registration information in which the management ID included in the token is set to the contact included in the token, and updates the association between the service ID and the management ID.

Further, in step S340, the CPU 51 sets the login flag to “1” and ends the ID change process shown in FIG.

On the other hand, if it is determined in the determination process of step S320 that at least one of the service password and the service ID is different, the process proceeds to step S360.

In this case, since the service password or the service ID does not match, it is considered that the user who entered the service login information is not the user himself / herself represented by the service registration information in which the management ID included in the token is set. Therefore, in step S360, the CPU 51 sets the login flag to "0" and ends the ID change process shown in FIG.

On the other hand, if it is determined in the determination process of step S310 that the service login information is not accepted, the process proceeds to step S350.

As described above, if the user requested to enter the service login information is different from the user represented by the service registration information in which the management ID included in the token is set, the user can use the service. Since the set service ID and service password are not known, a situation occurs in which the service login information is not entered. Therefore, in step S350, the CPU 51 determines whether or not the elapsed time of the timer started in step S300 has elapsed the predetermined standby time.

If the elapsed time of the timer has not reached the waiting time, the process proceeds to step S350, and the determination process of steps S310 and S350 is repeatedly executed until the service login information is accepted or the elapsed time of the timer elapses. ..

On the other hand, when the elapsed time of the timer has passed the waiting time, the user who is requested to input the service login information is not the user himself / herself represented by the service registration information in which the management ID included in the token is set. Conceivable. Therefore, the process proceeds to step S360, and in step S360, the CPU 51 sets the login flag to “0” and ends the ID change process shown in FIG. In the above, in the determination process of step S20 of the service provision process of FIG. 10, it is determined that the service registration information in which the same service ID as the registration destination included in the token is set is not registered in the service management table 26. Although the process has been described, if it is determined that the service is registered in the service management table 26, the process proceeds to step S40.

In step S40, does the CPU 51 set the management ID included in the token in the service registration information (hereinafter referred to as "target service registration information") in which the same service ID as the contact included in the token is set? Judge whether or not.

If the management ID included in the token is not set in the target service registration information, the process proceeds to step S50.

In this case, since the management ID is not associated with the target service registration information, the CPU 51 executes the ID association process in step S50.

FIG. 12 is a flowchart showing an example of the flow of the ID association process executed in step S50 of FIG.

In step S200, the CPU 51 displays a screen requesting the input of the service password included in the target service registration information on the output unit 69 of the user device 30 that has made the login request, and requests the input of the service password. The CPU 51 may describe a URL for displaying an authentication mail to the contact information included in the token and requesting the input of the service password in the authentication mail.

The CPU 51 activates a timer that measures the elapsed time from requesting the input of the service password in step S200.

In step S210, the CPU 51 determines whether or not the service password has been accepted. When the service password is accepted, the timer is stopped and the process proceeds to step S220.

In step S220, the CPU 51 compares the received service password with the service password included in the target service registration information, and determines whether or not the respective service passwords match. If the service passwords match, the process proceeds to step S230.

In this case, since the service password set for the service ID is confidential information that only the user who set the service ID can know, the management ID included in the token is the user himself / herself represented by the target service registration information. It is confirmed that the user who has entered the service password, which is the management ID of the above, is the user who requested the service from the service providing device 20.

Therefore, in step S230, the CPU 51 associates the service ID and the management ID in the target service registration information, sets the login flag to "1", and ends the ID association process shown in FIG.

On the other hand, if it is determined in the determination process of step S220 that the received service password and the service password included in the target service registration information do not match, the process proceeds to step S250.

Since the service passwords do not match, it is considered that the user who entered the service password is not the user himself / herself represented by the target service registration information. Therefore, in step S250, the CPU 51 sets the login flag to “0” and ends the ID association process shown in FIG.

On the other hand, if it is determined in the determination process of step S210 that the service password is not accepted, the process proceeds to step S240.

If the user requested to enter the service password is the user himself / herself represented by the target service registration information, he / she should know the service password set in the service providing device 20. However, if the user requested to enter the service password is different from the user represented by the target service registration information, he / she should not know the service password set for the service providing device 20.

That is, if the user requested to enter the service password is different from the user represented by the target service registration information, a situation occurs in which the service password is not entered. Therefore, in step S240, the CPU 51 determines whether or not the elapsed time of the timer started in step S200 has elapsed a predetermined standby time.

If the elapsed time of the timer has not reached the waiting time, the process proceeds to step S210, and the determination process of steps S210 and S240 is repeatedly executed until the service password is accepted or the elapsed time of the timer elapses.

On the other hand, when the elapsed time of the timer has elapsed the waiting time, it is considered that the user who is requested to input the service password is not the user himself / herself represented by the target service registration information. Therefore, the process proceeds to step S250, and in step S250, the CPU 51 sets the login flag to “0” and ends the ID association process shown in FIG.

In the above, in the determination process of step S40 of the service provision process of FIG. 10, the case where the management ID included in the token is not set in the target service registration information has been described, but the management ID included in the token is used as the target service registration information. If it is set, the process proceeds to step S65.

In this case, since the service registration information associated with the management ID and the same information as the contact information included in the token is registered in the service management table 26, the user who requested the service from the service providing device 20 can register the service. It means that the user is represented by information. Therefore, in step S65, the CPU 51 sets the login flag to “1”.

The account creation process in step S30, the ID association process in step S50, the ID change process in step S60, and the login in step S65, depending on the registration status of the contact information and the management ID included in the token in the service providing device 20. Step S70 is executed after any of the flag settings has been executed.

In step S70, the CPU 51 determines whether the login flag is set to "1", that is, whether to allow the user who requested the service to provide the service.

When the login flag is set to "1", the process proceeds to step S80, and in step S80, the CPU 51 provides the requested service and ends the service provision process shown in FIG.

On the other hand, when the login flag is set to "0", the service providing process shown in FIG. 10 is terminated without executing the process of step S80. That is, the service is not provided to the user who fails in the authentication by the service providing device 20.

As described above, according to the service providing system 1 according to the present embodiment, even if the user is authenticated by the authentication management device 10, whether the user is the user himself / herself represented by the service registration information or the service providing device. 20 also authenticates, and the service is provided after confirming that the user represented by the service registration information associated with the token notified from the authentication management device 10 is the user who requested the service.

Therefore, even if the administrator of the authentication management device 10 illegally rewrites the management ID and contact information, the user who requested the service from the service providing device 20 is the same as the user represented by the service registration information associated with the token. Since the identity of the user is confirmed, spoofing of the user is suppressed even if the authenticity of the management registration information registered in the authentication management device is not guaranteed.

Depending on the user, the usage contract for the cooperative authentication provided by the authentication management device 10 may be canceled, and the service login information may be directly input to the reception screen 35 of the service providing device 20 shown in FIG. 3 to directly authenticate to the service providing device 20. There is a user who requests.

As shown in FIG. 7, the service management table 26 stores a management ID for performing authentication in cooperation with the authentication management device 10, but when the user cancels the usage contract for the cooperation authentication in the authentication management device 10. As it is, the management ID will continue to remain in the service registration information of the user.

Therefore, when the service providing device 20 receives the authentication request directly from the user and the management ID is associated with the service ID of the input service login information, the service providing device 20 of the user in the authentication management device 10 In order to confirm the registration status, the authentication management device 10 may be requested to have a token including the management ID associated with the service ID of the input service login information.

When the user cancels the usage contract for authentication using the authentication management device 10, the user's management registration information is deleted from the authentication management table 16 of the authentication management device 10. Therefore, since the management registration information including the management ID associated with the service ID received from the service providing device 20 does not exist in the authentication management table 16, the authentication management device 10 receives the service instead of the token. An error notification notifying that the management ID associated with the ID does not exist is transmitted to the service providing device 20.

When the service providing device 20 receives the error notification from the authentication management device 10, the service providing device 20 executes the update process of the service management table 26.

FIG. 14 is an example of a flowchart showing a flow of update processing of the service management table 26 executed by the CPU 51 when the service providing device 20 receives an error notification. The update process of the service management table 26 is performed by the CPU 51 executing the service providing program.

When the error notification is received from the authentication management device 10, in step S400, the CPU 51 deletes the management ID of the service registration information including the service ID of the input service login information, and cancels the usage contract of the linked authentication. The association between the user's service ID and the management ID is released.

In step S410, the CPU 51 determines whether or not the service registration information including the service login information input from the reception screen 35 is registered in the service management table 26. When the service registration information including the input service login information is registered in the service management table 26, the user who requested the service is a user registered in the service providing device 20. Therefore, the process proceeds to step S420, and in step S420, the CPU 51 provides the service requested by the user and ends the update process of the service management table 26 shown in FIG.

On the other hand, when it is determined that the service registration information including the service login information input in the determination process of step S410 is not registered in the service management table 26, the user who requested the service is not registered in the service providing device 20. It will be a user. Therefore, the CPU 51 ends the update process of the service management table 26 shown in FIG. 14 without executing the process of step S420, so as not to provide the service to the unregistered user.

In this way, when the user directly requests the service providing device 20 for authentication without using the cooperative authentication, the service providing device 20 inquires the authentication management device 10 about the user's registration status, and the user authenticates. When it is not registered in the management device 10, the information related to the cooperation authentication is deleted from the service management table 26 so that unnecessary information does not remain in the service management table 26.

As described above, the update process of the service management table 26 is executed when the user directly requests the service providing device 20 for authentication, but some users may not frequently use the service of the service providing device 20. is there. In the case of such a user, after canceling the usage contract for authentication using the authentication management device 10, the service of the service providing device 20 may not be used for a long period of time, so that the service management table 26 is updated. Unnecessary information will continue to remain in the service management table 26.

Therefore, the service providing device 20 executes the periodic update process of the service management table 26 so that unnecessary information does not remain in the service management table 26 even if the user does not directly request the authentication.

FIG. 15 is an example of a flowchart showing the flow of periodic update processing of the service management table 26 executed by the CPU 51 at predetermined intervals such as every month. The periodic update process of the service management table 26 is performed by the CPU 51 executing the service providing program.

In step S500, the CPU 51 selects one of the service registration information from the service management table 26.

In step S510, the CPU 51 refers to the login time of the selected service registration information, and determines whether or not the specified time has elapsed from the previous login time. The specified time is a time that defines a period for maintaining the association between the service ID and the management ID after receiving the login request, and is stored in advance in, for example, the non-volatile memory 54. The user may change the specified time.

If the current time is the time when the specified time has elapsed from the login time of the selected service registration information, the process proceeds to step S520.

In step S520, the CPU 51 deletes the selected service registration information, cancels the association between the service ID and the management ID, and proceeds to step S530.

On the other hand, if the current time is less than the specified time from the login time of the selected service registration information, the process proceeds to step S530 without executing the process of step S520. That is, if the elapsed time from the previous login request has not reached the specified time, the selected service registration information should not be deleted in order to maintain the association between the service ID and the management ID in the selected service registration information. To do.

In step S530, the CPU 51 determines whether or not there is unselected service registration information not selected in step S500 in the service management table 26. If there is no unselected service registration information, the periodic update process of the service management table 26 shown in FIG. 15 is terminated.

On the other hand, if there is unselected service registration information, the process proceeds to step S500. That is, by repeatedly executing the processes of steps S500 to S530 until there is no unselected service registration information from the service management table 26, the service usage interval is defined among the users registered in the service management table 26. The service registration information of the user who has been free for more than an hour will be deleted.

Therefore, unnecessary information in the service management table 26 is deleted even if the user does not use the service provided by the service providing device 20.

When the service management table 26 is periodically updated, the usage interval of the service provided by the service providing device 20 is specified even for a user who has not canceled the usage contract of the linked authentication provided by the authentication management device 10. If the time is left or longer, the association between the service ID and the management ID in the service registration information corresponding to the user is released. On the other hand, when the user tries to use the service provided by the service providing device 20 by using the cooperative authentication after the specified time has elapsed from the previous use of the service, the management ID and contact information included in the token are set. Since the service registration information is not present in the service management table 26, the account creation process in step S30 in the service provision process shown in FIG. 10 is executed. Therefore, in the service management table 26, the association between the service ID and the management ID for the user is restored.

When the service providing device 20 in the above-described embodiment receives the token from the authentication management device 10, the service providing device 20 confirms the identity of the user by a method according to the registration status of the management ID and the service ID in the service providing device 20 of the management ID. However, when the authenticity of the authentication management table 16 in the authentication management device 10 is guaranteed, the service providing device 20 treats the information contained in the token as correct information of the user who requested the service from the service providing device 20. You may. In this case, the service providing device 20 provides the requested service to the user without confirming the identity of the user.

Specifically, in the account creation process of step S30 in FIG. 10, the service providing device 20 may display a confirmation screen (not shown) after receiving the consent notification for the confirmation email and ask the user to input the service login information. It displays a confirmation screen and accepts service login information without sending a confirmation email. Further, in the ID association process of step S50 in FIG. 10, the requested service is provided to the user without requiring the user to input the service password. Further, in the ID change process of step S60 in FIG. 10, the service ID of the service registration information in which the management ID included in the token is set is changed to the contact included in the token without requesting the input of the service login information. Then, the association between the service ID and the management ID is updated.

The authenticity of the authentication management table 16 in the authentication management device 10 is guaranteed, for example, when the domain including the authentication management device 10 has received domain authentication, or when the user is registered in the authentication management device 10. At this time, the case where the user is registered after confirming the identity of the user is included.

Although the present invention has been described above using the embodiments, the present invention is not limited to the scope described in the embodiments. Various changes or improvements can be made to the embodiments without departing from the gist of the present invention, and the modified or improved forms are also included in the technical scope of the present invention. For example, the order of processing may be changed without departing from the gist of the present invention.

In this embodiment, a mode in which each process is realized by software has been described as an example, but a process equivalent to each flowchart shown in FIGS. 10 to 15 is implemented in, for example, an ASIC (Application Specific Integrated Circuit) and hardware. It may be processed by hardware. In this case, the processing speed can be increased as compared with the case where each processing is realized by software.

Further, in the above-described embodiment, the mode in which each program is installed in the ROM has been described, but the present invention is not limited to this. Each program according to the present invention can also be provided in a form recorded on a computer-readable storage medium. For example, each program according to the present invention may be provided in the form of being recorded on an optical disk such as a CD (Compact Disc) -ROM or a DVD (Digital Versatile Disc) -ROM. Further, each program according to the present invention may be provided in a form recorded in a semiconductor memory such as a USB memory and a flash memory. Further, the authentication management device 10, the service providing device 20, and the user device 30 may each acquire a program from an external device connected to the communication line 2 through the communication line 2.

Further, each functional unit of the authentication management device 10 and the authentication management DB 14 shown in FIG. 4 are not realized by a single computer 40, but are distributed and arranged in a plurality of computers by using, for example, cloud computing, and a plurality of computers are used. By linking the computers, the same processing as that of the authentication management device 10 may be executed. Similarly, with respect to the service providing device 20 shown in FIG. 6, each functional unit and the service management DB 25 are distributed and arranged on a plurality of computers, and the plurality of computers are linked to perform the same processing as the service providing device 20. May be executed.

1 ... Service provision system, 2 ... Communication line, 10 ... Authentication management device, 11 (21, 31) ... User interface (UI) unit, 12 (22, 32) ... Control unit , 13 (23, 33) ... Communication unit, 14 ... Authentication management DB, 16 ... Authentication management table, 20 ... Service providing device, 24 ... Confirmation unit, 25 ... Service management DB 25, 26 ... Service management table, 30 ... User device, 35 ... Reception screen, 36 ... Service ID input area, 37 ... Service password input area, 38 ... Login button, 39 ... link character string, 40 (50, 60) ... computer, 41 (51, 61) ... CPU, 42 (52, 62) ... ROM, 43 (53, 63) ... RAM , 44 (54, 64) ... Non-volatile memory, 45 (55, 65) ... I / O, 47 (57, 67) ... Communication unit, 48 (58, 68) ... Input unit , 49 (59, 69) ・ ・ ・ Output unit

Claims (11)

Using the management information received from the authentication management device that supports the authentication of multiple affiliated services, it is confirmed whether the registration information of the user corresponding to the management information has been registered, and the service request is based on the registration information. A confirmation unit that confirms whether the request is from the user represented, and
When the confirmation unit confirms that the registration information has been registered and the request for the service is a request from the user represented by the registration information, the service requested by the user is provided. And the control unit that controls
Service providing device equipped with. When the management information received from the authentication management device is not registered in the management table that manages the registration information for each user, the confirmation unit includes the contact information included in the management information received from the authentication management device. The service providing device according to claim 1, wherein the service providing device is used to confirm whether the service request is a request from a user represented by the registration information. When the contact information included in the management information is an e-mail address, the confirmation unit uses the service in response to the confirmation e-mail sent to the e-mail address to confirm whether the user has requested the service. The service providing device according to claim 2, which confirms that the request for the service is a request from the user represented by the registration information by accepting the consent notification. The confirmation unit requests the user to input the password of the registration information when the registration information has already been registered, and when the entered password is the same as the password of the registration information, the service request is made. Confirm that the request is from the user represented by the registration information,
The service providing device according to any one of claims 1 to 3, wherein the control unit controls associating the management information received from the authentication management device with the registration information. When the identifier of the registration information including the management ID of the management information is set to have a content different from the contact information included in the management information, the confirmation unit requests a password, and the obtained password is the said. If it is the same as the password of the registration information, confirm that the service request is a request from the user represented by the registration information, and confirm that the request is from the user.
The service providing device according to any one of claims 1 to 4, wherein the control unit controls to change the identifier of the registered information to the contact information of the management information received from the authentication management device. The confirmation unit requests the input of the contact information included in the management information in addition to the password of the registration information, and the obtained password is the same as the password of the registration information and the obtained contact information. The service providing device according to claim 5, wherein the service providing device confirms that the service request is a request from the user represented by the registration information when is the same as the contact information included in the management information. When a service request is received from a user without going through the authentication management device, the control unit requests the management information of the user who requested the service from the authentication management device, but the management information The service providing device according to any one of claims 1 to 6, which controls to release the association between the management information and the registration information when the above is not obtained. When a predetermined period has elapsed from the authentication associated with the use of the provided service for each user, the control unit cancels the association between the management information of the user whose predetermined period has passed and the registration information. The service providing device according to any one of claims 1 to 7, which is controlled. The confirmation unit according to any one of claims 1 to 8, which treats the management information received from the authentication management device whose authenticity of the information is guaranteed as correct information of the user who requested the service. Service provider. A service providing program for causing a computer to function as each part of the service providing device according to any one of claims 1 to 9. The service providing device according to any one of claims 1 to 9.
Management information including an identifier that identifies the user and the contact information of the user is registered for each user, and when the registered user requests the service provided by the service providing device, the user requesting the service An authentication management device that transmits the management information to the service providing device and cooperates with the service providing device to support authentication of a user requesting the service on the service providing device.
Service provision system including.