Authentication System
The authentication system simplifies the integration of multiple authentication servers by using a platform to relay information, reducing complexity and costs, and enhances user experience with visual authentication options.
Patent Information
- Application Number
- JP2024029684
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-02-29
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2041-04-20
AI Technical Summary
As the number of ID-linked services increases, the complexity of authentication systems grows, leading to higher development and maintenance costs due to the need for multiple authentication servers to communicate directly, complicating the system architecture.
An authentication system featuring a terminal device, a first server storing user information, a second server without user information, and a platform that relays authentication requests and results between them, allowing for simplified configuration and user-friendly authentication options through visual buttons for direct and relayed authentication methods.
This configuration enables easier setup and improved user convenience by reducing system complexity and costs while facilitating seamless interaction between authentication servers via a centralized platform.
Smart Images

Figure 0007594141000001 
Figure 0007594141000002 
Figure 0007594141000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to authentication systems. [Background technology]
[0002] Japanese Patent Laid-Open Publication No. 2020-36234 (Patent Document 1) discloses an authorization system including an authentication and authorization server, a resource server that provides a Web service, and a client device. In this authorization system, the client receives a Web service from the resource server using an access token acquired from the authentication and authorization server. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2020-36234 A Summary of the Invention [Problem to be solved by the invention]
[0004] In recent years, ID federation, which allows users to log in to multiple services on a network using a single ID, has been attracting attention. ID federation is realized, for example, by using a protocol such as OIDC (OpenID Connect).
[0005] When there are many services that are ID-linked, there will also be a large number of authentication servers corresponding to each service server. Therefore, if authentication servers are to be linked using the OIDC protocol, the system may become complicated. The increased complexity of the system leads to increased time and costs required for system development and maintenance.
[0006] The present disclosure has been made to solve the above problems, and an object of the present disclosure is to realize cooperation between authentication servers with a relatively simple configuration. [Means for solving the problem]
[0007] (1) An authentication system according to an aspect of the present disclosure includes a terminal device operated by a user, a first server that stores information for identifying the user, a second server that does not store the information, and a platform that relays information between the first server and the second server. When a user authentication request is made from the terminal device to the second server, the platform relays the authentication request from the second server to the first server, and relays the authentication result of the first server in response to the authentication request from the first server to the second server.
[0008] According to the above configuration, the platform relays the exchange of information between the first server and the second server. Therefore, it is only necessary to construct a system in which each of the first server and the second server can exchange information with the platform. Therefore, the authentication system can be configured more easily than when a system in which servers exchange information with each other is constructed.
[0009] (2) In one embodiment, the terminal device includes a display unit. The terminal device causes the display unit to display a screen for receiving authentication. A first button and a second button are displayed on the screen. When the first button is pressed, the second server authenticates the user. When the second button is pressed, the platform relays an authentication request from the second server to the first server, and the first server authenticates the user.
[0010] According to the above configuration, the display unit of the terminal device displays a first button for receiving authentication directly from the second server and a second button for receiving authentication from the first server by relaying information from the platform. The user can visually recognize that there are two authentication methods, which improves user convenience.
[0011] (3) In one embodiment, the first server stores user information about the user. The second server does not store the user information. If the authentication result indicates successful authentication, the platform sends a consent request to the terminal device requesting consent to sharing the user information with the second server, and if consent to the consent request is obtained from the terminal device, relays the user information from the first server to the second server.
[0012] According to the above configuration, the platform also relays the transmission of user information. By configuring the platform to relay information exchanged between the first server and the second server, the authentication system can be configured more simply than when a system is constructed in which servers exchange information with each other.
[0013] (4) In one embodiment, if consent to the consent request is obtained from the terminal device, the second server sends an authorization code to the terminal device.
[0014] (5) In one embodiment, the terminal device transmits the authorization code to the second server and obtains a token from the second server, the token including at least an access token and an ID token. Effect of the Invention
[0015] According to the present disclosure, cooperation between authentication servers can be achieved with a relatively simple configuration. [Brief description of the drawings]
[0016] [Figure 1] 1 is a diagram showing a schematic configuration of an authentication system according to an embodiment; [Diagram 2] FIG. 2 is a diagram for explaining the configuration of an authentication server 11. [Diagram 3] FIG. 2 is a diagram for explaining the configuration of an authentication server 21. [Figure 4] 13 is a flowchart (part 1) showing a procedure for a login process to a first service (back-end server). [Diagram 5] 13 is a second flowchart showing the procedure of a login process to a first service (back-end server). [Figure 6] FIG. 11 is a diagram showing an example of a login screen for a first service displayed on a terminal device. [Figure 7] 13 is a flowchart (part 1) showing a procedure for a global login process. [Figure 8] 13 is a flowchart (part 2) showing the procedure of a global login process. [Figure 9] 13 is a flowchart (part 3) illustrating the procedure of a global login process. [Figure 10] FIG. 13 is a diagram showing an example of a login screen for a third service displayed on the terminal device. [Figure 11] FIG. 11 is a diagram illustrating an example of a selection screen displayed on a terminal device. [Figure 12] FIG. 1 is a diagram illustrating a schematic configuration of a service providing system according to a first modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0017] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference characters, and the description thereof will not be repeated.
[0018] 1 is a diagram showing a schematic configuration of an authentication system 1 according to the present embodiment. The authentication system 1 according to the present embodiment is a system for linking IDs (user IDs) between services operated in different countries. The authentication system 1 enables ID linking with a relatively simple configuration by allowing authentication servers in different countries to exchange information via a common platform.
[0019] 1, authentication system 1 includes service providing systems 10-40, a global ID platform 50, and a terminal device 70 owned by a user 71. Service providing systems 10-40, global ID platform 50, and terminal device 70 are connected to each other so as to be able to communicate with each other via a network 60 such as the Internet.
[0020] The service providing systems 10 to 40 are systems that provide automobile-related services in countries A to D, respectively.
[0021] The service providing system 10 provides a service related to automobiles in country A. In this embodiment, the service providing system 10 provides two types of services, a first service and a second service. The first service is a subscription service in which a user can use a vehicle during a contract period by paying a fixed amount every month. The fixed fee for the first service includes, for example, vehicle maintenance costs and automobile insurance fees. The second service is a car sharing service in which members share a specific vehicle. Note that the services provided by the service providing system 10 are not limited to the above-mentioned first service and second service. The service providing system 10 may provide another service in addition to the first service and the second service, instead of the first service and the second service, or instead of either the first service or the second service.
[0022] The service providing system 10 includes an authentication server 11 and back-end servers 12 and 13. The authentication server 11 is a server that authenticates users who are registered as members of the first service and / or the second service. The authentication server 11 has a function as an open ID provider. A detailed configuration of the authentication server 11 will be described later with reference to FIG. 2. The authentication server 11 corresponds to an example of a "first server" according to the present disclosure.
[0023] The back-end server 12 is a server that provides a first service. A service provider (not shown) of the back-end server 12 provides an application 73 for receiving the first service in a marketplace or the like. The back-end server 12 accepts a user operation via the application 73 from a terminal device (e.g., a smartphone, a personal computer, etc.) on which the application 73 is installed, and executes a process for providing a service according to the operation.
[0024] The back-end server 13 is a server that provides a second service. A service provider (not shown) of the back-end server 13 provides an application (not shown) for receiving the second service in a marketplace or the like. The back-end server 13 accepts a user operation via an application from a terminal device in which the application for receiving the second service is installed, and executes a process for providing a service according to the operation.
[0025] The terminal device 70 is a smartphone owned by a user 71. The terminal device 70 is not limited to a smartphone, and may be, for example, a desktop PC (Personal Computer), a notebook PC, a tablet terminal, or other information processing terminals having a communication function. An application 73 for using the first service is installed in the terminal device 70 according to the present embodiment.
[0026] The user 71 is a user who has registered as a member of the first service provided by the back-end server 12. The user 71 has an ID (user ID) and a password for logging in to the first service. The password is, for example, one that the user 71 set when registering as a member of the first service. The user 71 starts up an application 73 on the terminal device 70, displays a login screen for the first service (back-end server 12), and inputs the user ID and password on the displayed login screen. This input information is sent to the authentication server 11. The authentication server 11 performs a process of authenticating the user ID, and if the authentication is successful, the user 71 is able to receive the first service from the back-end server 12.
[0027] The service providing system 20 provides a service related to automobiles in country B. In this embodiment, the service providing system 20 provides three types of services: a third service, a fourth service, and a fifth service. The third service is a subscription service similar to the first service. The fourth service is a car sharing service similar to the second service. The fifth service is a car pool service in which multiple people ride together in one vehicle during commuting, etc. Note that the services provided by the service providing system 20 are not limited to the third service, the fourth service, and the fifth service. The service providing system 10 may provide other services in addition to the third service, the fourth service, and the fifth service, or in place of any of the third service, the fourth service, and the fifth service.
[0028] The service providing system 20 includes an authentication server 21 and back-end servers 22, 23, and 24. The authentication server 21 is a server that authenticates users who are registered as members of the third service, the fourth service, and / or the fifth service. The authentication server 21 functions as an open ID provider. A detailed configuration of the authentication server 21 will be described later with reference to FIG. 3. The authentication server 21 corresponds to an example of a "second server" according to the present disclosure.
[0029] The back-end server 22 is a server that provides a third service. A service provider (not shown) of the back-end server 22 provides an application 74 for receiving the third service in a marketplace or the like. The back-end server 22 accepts a user operation via the application 74 from a terminal device on which the application 74 is installed, and executes a process for providing a service according to the operation.
[0030] The back-end server 23 is a server that provides a fourth service. A service provider (not shown) of the back-end server 23 provides an application (not shown) for receiving the provision of the fourth service in a marketplace or the like. The back-end server 23 accepts a user operation via the application from a terminal device in which the application for receiving the provision of the fourth service is installed, and executes a process for providing a service according to the operation.
[0031] The back-end server 24 is a server that provides a fifth service. A service provider (not shown) of the back-end server 24 provides an application (not shown) for receiving the provision of the fifth service in a marketplace or the like. The back-end server 24 accepts a user operation via the application from a terminal device in which the application for receiving the provision of the fifth service is installed, and executes a process for providing a service according to the operation.
[0032] The service providing system 30 provides services related to automobiles in country C. The service providing system includes an authentication server and at least one back-end server, neither of which are shown in the figure.
[0033] The service providing system 40 provides services related to automobiles in country D. The service providing system includes an authentication server and at least one back-end server, neither of which are shown in the figure.
[0034] Fig. 2 is a diagram for explaining the configuration of authentication server 11. Referring to Fig. 2, authentication server 11 includes a control device 111, a read only memory (ROM) 112, a random access memory (RAM) 113, a communication device 114, and a storage device 115. Control device 111, ROM 112, RAM 113, communication device 114, and storage device 115 are connected to a bus 117.
[0035] The control device 111 is configured, for example, by an integrated circuit including a CPU (Central Processing Unit). The control device 111 loads various programs stored in the ROM 112 into the RAM 113 and executes them. The various programs include an operating system and the like. The RAM 113 functions as a working memory and temporarily stores various data required for executing the various programs. The control device 111 manages, for example, information about users who have registered as members in the first service or the second service (hereinafter also referred to as "user information"), performs authentication processing, and performs authorization processing.
[0036] Communication device 114 includes an interface for connecting to network 60, and is configured to be able to communicate with external devices via network 60. External devices include, for example, global ID platform 50 and terminal device 70.
[0037] The storage device 115 includes a storage medium such as a hard disk or a flash memory. The storage device 115 stores user information 1151 and 1152. The user information 1151 is information about a user who has registered as a member in the first service. The user information 1152 is information about a user who has registered as a member in the second service. The user information 1151 includes a user ID assigned when the user registered as a member in the first service and personal information input by the user when the user registered as a member. The personal information includes, for example, information such as a name, an email address, a telephone number, an address, and a password. The password is set by the user when the user registered as a member or by the control device 111 when the user registered as a member. The user information 1152 includes a user ID assigned when the user registered as a member in the second service and personal information input by the user when the user registered as a member. Note that a storage device that stores the user information 1151 and a storage device that stores the user information 1152 may be provided separately.
[0038] The control device 111 includes a user information management unit 1111, an authentication and authorization unit 1112, and a global authentication unit 1113. The control device 111 functions as the user information management unit 1111, the authentication and authorization unit 1112, and the global authentication unit 1113, for example, by executing a program stored in the ROM 112. Note that the user information management unit 1111, the authentication and authorization unit 1112, and the global authentication unit 1113 may be realized by, for example, dedicated hardware (electronic circuitry).
[0039] The user information management unit 1111 assigns a user ID corresponding to the service (first service or second service) for which the user has registered as a member to the first service or the second service. In detail, the user information management unit 1111 assigns a user ID of the first service to a user who has registered as a member to the first service. The user information management unit 1111 stores the assigned user ID of the first service and the input personal information in the storage device 115 as user information 1151. The user information management unit 1111 assigns a user ID of the second service to a user who has registered as a member to the second service. The user information management unit 1111 stores the assigned user ID of the second service and the input personal information in the storage device 115 as user information 1152.
[0040] The user information management unit 1111 judges whether the user has registered for the first service or the second service based on whether the registration has been made through the application 73 corresponding to the first service or the application corresponding to the second service. For example, when the registration has been made through the application 73 corresponding to the first service, the user information management unit 1111 judges that the registration has been made for the first service and stores the input information as the user information 1151. In order to judge the correspondence between the application and the service, a service ID for identifying the first service and the second service may be introduced and the service ID may be assigned to the application, the service, and the user information. In this case, the user information management unit 1111 may specify the service to be registered for by the service ID assigned to the application used for the registration.
[0041] When a login operation to the first service or the second service is performed via a corresponding application, the authentication and authorization unit 1112 verifies the validity of the input user ID. For example, when the authentication and authorization unit 1112 receives a login request to the first service from the terminal device 70 (browser) of the user 71 via the application 73, the authentication and authorization unit 1112 displays a login screen to the first service on the terminal device 70. When a user ID and a password are input on the login screen, the authentication and authorization unit 1112 queries the user ID and password against the user information 1151 stored in the storage device 115, and authenticates the user 71 (user ID). The authentication and authorization unit 1112 may identify a service ID based on the application 73 operated by the user 71, thereby recognizing that the user information to be referenced is the user information 1151.
[0042] When the authentication and authorization unit 1112 confirms the validity of the user ID, it returns an authorization code to the terminal device 70. When the authentication and authorization unit 1112 receives a token request with the authorization code from the terminal device 70, it returns a token to the application. This token includes, for example, an access token, an ID token, and a refresh token. For example, the application 73 that has received the token can access the backend server 12 using the access token and the ID token. This allows the user 71 to receive the first service.
[0043] The global authentication unit 1113 functions to perform ID federation between a service (first service or second service) provided by the service providing system 10 and a service provided by another service providing system 20 to 40. Although details will be described later, when there is a login request to a service provided by another service providing system 20 to 40 using a user ID of a service (first service or second service) provided by the service providing system 10, the global authentication unit 1113 verifies the validity of the user ID. Note that hereinafter, login to a service provided by another service providing system using a user ID of a service provided by a certain service providing system is also referred to as "global login".
[0044] Fig. 3 is a diagram for explaining the configuration of authentication server 21. Referring to Fig. 3, authentication server 21 includes control device 211, ROM 212, RAM 213, communication device 214, and storage device 215. Control device 211, ROM 212, RAM 213, communication device 214, and storage device 215 are connected to bus 217. Except for information stored in storage device 215, control device 211, ROM 212, RAM 213, communication device 214, and storage device 215 are basically similar to control device 111, ROM 112, RAM 113, communication device 114, and storage device 115 of authentication server 11, respectively, and therefore description thereof will not be repeated.
[0045] The storage device 215 stores user information 2151, 2152, and 2153. The user information 2151 is information about a user who has registered as a member of the third service. The user information 2152 is information about a user who has registered as a member of the fourth service. The user information 2153 is information about a user who has registered as a member of the fifth service.
[0046] The authentication servers of the service providing systems 30 and 40 basically have the same configuration as the authentication servers 11 and 21 of the service providing systems 10 and 20. Therefore, detailed description of the authentication servers of the service providing systems 30 and 40 will not be repeated.
[0047] Next, a procedure for logging in to the first service by user 71 who has registered as a member of the first service will be described. User 71 starts up application 73 on terminal device 70 in which application 73 is installed, and logs in to the first service.
[0048] 4 and 5 are flowcharts showing the procedure of the login process to the first service (back-end server 12). The process of the flowcharts of FIG. 4 and FIG. 5 is started when the user 71 launches the application 73 on the terminal device 70. Each step (hereinafter, steps are abbreviated as "S") of the flowcharts shown in FIG. 4 and FIG. 5 will be described as being realized by software processing by the terminal device 70, the authentication server 11 (user information management unit 1111 and authentication authorization unit 1112), and the back-end server 12, but a part or all of it may be realized by hardware (electronic circuits) created in the terminal device 70, the authentication server 11, and the back-end server 12.
[0049] In S1, the user 71 operates the terminal device 70 to launch the application 73 and performs an operation to display a login screen (a screen for transmitting an authentication request) on the display screen of the terminal device 70. The application 73 accepts the operation.
[0050] In S2 and S3, when an operation for displaying a login screen is accepted, the application 73 requests the authentication server 11 to display the login screen via the browser of the terminal device 70. Specifically, in S2, the application 73 starts the browser of the terminal device 70 and redirects the browser to the authorization endpoint of the authentication server 11. In S3, the browser requests the authorization endpoint of the authentication server 11 to display the login screen.
[0051] In S4, the authentication server 11 verifies the contents of the request and returns a login screen to the browser, whereby a login screen for the first service (backend server 12) is displayed on the browser.
[0052] In S5, the user 71 inputs a user ID and a password on the login screen and presses the login button, whereby an authentication request is sent from the browser to the authentication server 11 together with the user ID and password.
[0053] 6 is a diagram showing an example of a login screen for the first service displayed on the terminal device 70. A user ID input field 81, a password input field 82, a login button 83, and a global login button 84 are displayed on the display unit 80 of the terminal device 70. The user 71 inputs a user ID and a password in the user ID input field 81 and the password input field 82, respectively, and presses the login button 83. As a result, an authentication request is sent from the browser to the authentication server 11 together with the input user ID and password. In other words, the login button 83 is a button for receiving authentication directly from the authentication server 11.
[0054] The global login button 84 is used when requesting login to the first service using a user ID of a service other than the first service. Details of the global login button 84 will be described later. That is, the global login button 84 is a button for receiving authentication at an authentication server other than the authentication server 11. The login button 83 corresponds to an example of a "first button" according to the present disclosure. Moreover, the global login button 84 corresponds to an example of a "second button" according to the present disclosure.
[0055] 4 and 5 again, in S6, authentication server 11 verifies the input user ID and password. If the verification result indicates that at least one of the user ID and password is incorrect, processing in S7 is executed. If the verification result indicates that the user ID and password are not incorrect, processing in S8 is executed.
[0056] In S7, the authentication server 11 returns a screen indicating that at least one of the user ID and password is incorrect to the browser. By displaying this screen in the browser, the user 71 can recognize the input error.
[0057] In S8, the authentication server 11 redirects the browser to the callback URL with the authorization code. The callback URL redirects the browser to the application 73.
[0058] In S9, the browser accesses the application 73, which is the transition destination of the callback URL, with the authorization code attached. As a result, the authorization code is passed to the application 73.
[0059] In S10, the application 73 sends a token request to the token endpoint of the authentication server 11 together with the authorization code received in S9.
[0060] In S11, the authentication server 11 verifies the contents of the token request and transmits the token to the application 73. The tokens transmitted from the authentication server 11 to the application 73 include, for example, an access token, an ID token, and a refresh token.
[0061] In S12, the application 73 sends a request to the backend server 12 to provide the first service, together with the access token and the ID token.
[0062] In S13, upon receiving the access token and the ID token, the backend server 12 transmits the access token and the ID token to the user information end point of the authentication server 11.
[0063] In S14, the authentication server 11 verifies the access token and the ID token and returns the user information to the backend server 12.
[0064] In S 15 , the backend server 12 starts providing the service to the user 71 .
[0065] By receiving authentication from the authentication server 11 as described above, the user 71 can log in to the first service for which he / she is registered as a member, and can receive the first service from the back-end server 12.
[0066] Referring again to FIG. 1, the global ID platform 50 is a platform for linking IDs between a plurality of services across countries. The global ID platform 50 has a function of relaying information. The global ID platform 50 stores correspondence information that associates a service (back-end server) with an authentication server. The correspondence information is information that associates a service with an authentication server that authenticates a user who has made a login request to the service. Specifically, the correspondence information associates a first service with the authentication server 11. The correspondence information also associates a second service with the authentication server 11. The correspondence information also associates a third service with the authentication server 21. The correspondence information also associates a fourth service with the authentication server 21. The correspondence information also associates a fifth service with the authentication server 21. The global ID platform 50 identifies a relay destination of information based on the correspondence information.
[0067] The global ID platform 50 enables a user to log in to a service provided by a service providing system using a user ID of the service provided by the other service providing system (global login) by relaying information exchange between each of the service providing systems 10 to 40 and the terminal device 70. In other words, once a user 71 has registered as a member for one service provided by a service providing system, the user 71 can use the user ID to access and use the service provided by the other service providing system without registering as a member for the service provided by the other service providing system.
[0068] For example, when the user 71 visits country B, in order to use the third service provided by the service providing system 20 in country B, the user 71 needs to install an application 74 corresponding to the third service on the terminal device 70, input personal information of the user 71 on a member registration page, and register as a member of the third service. It is troublesome for the user 71 to register as a member for each service to be used, and this impairs the convenience of the user 71.
[0069] For example, it is possible to use a protocol such as OIDC to build a system for ID federation between the authentication servers of each service providing system, thereby enabling ID federation between the authentication servers of each service providing system. However, if there are many authentication servers to be federated, the system may become complicated. The increased complexity of the system leads to increased time and costs required for system development and maintenance.
[0070] Therefore, in the authentication system 1 according to the present embodiment, a global ID platform 50 that relays information is provided, thereby enabling global login that omits direct information exchange between authentication servers. As a result, from the authentication server of a certain service providing system, ID federation with a plurality of other authentication servers is possible by information processing with the global ID platform 50. In other words, since it is only necessary to construct a system in which information can be exchanged between the authentication server and the global ID platform 50, the system configuration can be simplified compared to the case in which a system in which ID federation is performed by directly exchanging information between the authentication servers of each service providing system is constructed. Global login will be specifically described below. As an example, the following assumes an example in which a user 71 logs in to a third service provided by the service providing system 20 using a user ID of the first service. The user 71 is not registered as a member of the third service. Therefore, a user ID of the third service has not been issued to the user 71.
[0071] First, the user 71 installs the application 74 for using the third service in the terminal device 70. Then, when the user 71 launches the application 74 on the terminal device 70, the processing shown in Figs. 7 to 9 starts.
[0072] 7 to 9 are flowcharts showing the procedure of global login processing. The processing of the flowcharts of FIGS. 7 to 9 is started when a user 71 launches an application 74 on a terminal device 70. Each step of the flowcharts shown in FIGS. 7 to 9 will be described as being realized by software processing by the terminal device 70, authentication server 11 (user information management unit 1111 and authentication authorization unit 1112), authentication server 21 (global authentication unit 2113), back-end server 22, and global ID platform 50, but a part or all of the steps may be realized by hardware (electronic circuits) created in the terminal device 70, authentication server 11, authentication server 21, back-end server 22, and global ID platform 50.
[0073] In S20, the user 71 operates the terminal device 70 to launch the application 74 and performs an operation to display a login screen on the display screen of the terminal device 70. The application 74 accepts the operation.
[0074] In S21 and S22, when an operation for displaying a login screen is accepted, the application 74 requests the authentication server 21 of the service providing system 20 to display a login screen via the browser of the terminal device 70. Specifically, in S21, the application 74 starts the browser of the terminal device 70 and redirects the browser to an authorization end point of the authentication server 21. In S22, the browser requests the authorization end point of the authentication server 21 to display a login screen.
[0075] In S23, the authentication server 21 verifies the contents of the request and returns a login screen to the browser.
[0076] In S24, the user 71 selects the global login button 88 on the login screen. This causes a global login request to be sent from the browser to the authentication server 21.
[0077] FIG. 10 is a diagram showing an example of a login screen for the third service displayed on the terminal device 70. In this embodiment, the display configuration of the login screen for the third service is basically the same as that of the login screen for the first service. A user ID input field 85, a password input field 86, a login button 87, and a global login button 88 are displayed on the display unit 80 of the terminal device 70. The user ID input field 85, the password input field 86, and the login button 87 are the same as those described in FIG. 6, and are used when logging in to the third service using a user ID and a password issued to use the third service. If the user is registered as a member of the third service, the user enters the user ID and password for the third service in the user ID input field 85 and the password input field 86, respectively, and presses the login button 87. That is, the login button 87 is a button for receiving direct authentication from the authentication server 21.
[0078] The global login button 88 is a button for logging in to the third service through ID federation. That is, the global login button 88 is a button for logging in to the third service using a user ID of a service other than the third service. In other words, the global login button 88 is a button for receiving authentication from an authentication server other than the authentication server 21. The global login button 88 is used when a user 71 who is not registered as a member of the third service attempts to log in to the third service, as in this example. The login button 87 corresponds to an example of a "first button" according to the present disclosure. The global login button 88 corresponds to an example of a "second button" according to the present disclosure.
[0079] 7 to 9 again, in S25, upon receiving the global login request, authentication server 21 redirects the browser to the global login end point of global ID platform 50.
[0080] In S26, the browser requests a global login to the global login endpoint of the global ID platform 50.
[0081] In S27, the global ID platform 50 verifies the contents of the request and returns a selection screen to the browser. The selection screen is a screen for selecting a user ID to be used for global login. In this embodiment, since the user 71 uses the user ID of the first service, the user 71 selects "Country A" and "First Service" on the selection screen.
[0082] 11 is a diagram showing an example of a selection screen displayed on the terminal device 70. A country selection field 91, a service selection field 92, and a selection (decision) button 93 are displayed on the display unit 80 of the terminal device 70. The user 71 selects which service's user ID to use for global login. In this example, the user 71 will use the user ID of the first service in country A to globally log in to the third service, so the user 71 selects country A in the country selection field 91 and the first service in the service selection field 92, and presses the selection button 93.
[0083] 7 to 9, in S28, the information (country A and first service) entered by the user 71 is sent to the global ID platform 50 as a request.
[0084] In S29, upon receiving the request, the global ID platform 50 identifies an authentication server that authenticates the user ID used for global login based on the contents of the request, and redirects the browser to the authentication server. Specifically, the global ID platform 50 identifies the authentication server 11 of the service providing system 10 including the backend server 12 that provides the first service from the information "Country A" and "First Service". The global ID platform 50 redirects the browser to the authentication server 11. For example, the global ID platform 50 may identify the authentication server using correspondence information.
[0085] In S30, the browser requests the authentication server 11 to display a login screen for the first service.
[0086] In S31, the authentication server 11 verifies the contents of the request and returns a login screen for the first service to the browser.
[0087] In S32, the user 71 inputs the user ID and password for the first service on the login screen. As the login screen, for example, the screen in Fig. 6 may be displayed, or another screen for global login may be displayed.
[0088] In S33, authentication server 11 verifies the input user ID and password. If the verification result confirms that the user ID and password are correct, authentication server 11 returns the verification result to global ID platform 50. Specifically, authentication server 11 redirects the browser to global ID platform 50.
[0089] At S34, the browser accesses the global ID platform 50 with the result of the validation.
[0090] If at least one of the user ID and the password is incorrect in S33, the authentication server 11 returns to the global ID platform 50 a verification result indicating that at least one of the user ID and the password is incorrect.
[0091] In S35, the global ID platform 50 transmits a request to the user 71 (browser) for consent to the transfer of the user information 1151 from the authentication server 11 to the authentication server 21. As a result, for example, a screen for requesting the authority to transfer the user information 1151 is displayed on the display unit 80 of the terminal device 70. The user 71 can consent to the transfer of the user information 1151 by pressing an consent button (not shown) displayed on the display unit 80.
[0092] In S36, the user 71 consents to the transfer of the user information and presses the consent button (not shown) displayed on the display unit 80 of the terminal device 70. As a result, the consent information of the user 71 is sent from the browser to the global ID platform 50.
[0093] In S37 and S38, the global ID platform 50 transmits the consent information to the authentication server 21. Specifically, in S37, the global ID platform 50 redirects the browser to the authentication server 21. In S38, the browser accesses the authentication server 21 with the consent information attached.
[0094] In S39, the authentication server 21 redirects the browser to the callback URL with the authorization code. The callback URL redirects the browser to the application 74.
[0095] In S40, the browser accesses the application 74, which is the transition destination of the callback URL, with the authorization code attached. As a result, the authorization code is passed to the application 74.
[0096] In S41, the application 74 sends a token request to the token endpoint of the authentication server 21 together with the authorization code received in S40.
[0097] In S42, the authentication server 21 verifies the contents of the token request and transmits the token to the application 74. The tokens transmitted from the authentication server 21 to the application 74 include, for example, an access token, an ID token, and a refresh token.
[0098] In S43, the application 74 sends a request to the backend server 22 to provide the third service, together with the access token and the ID token.
[0099] In S44, upon receiving the access token and the ID token, the backend server 22 transmits the access token and the ID token to the user information endpoint of the authentication server 21.
[0100] In S45, the authentication server 21 verifies the access token and the ID token, and returns the user information 1151 of the user 71 to the backend server 22.
[0101] In S46, the backend server 22 starts providing the service to the user 71. In this way, the user 71 who is not registered as a member of the third service can log in to the third service by using the user ID of the first service for which the user 71 is registered as a member.
[0102] The user information 1151 of the user 71 is shared with the authentication server 21 via the global ID platform 50 by the processes of S50 to S52 after the process of S36 is executed and before the process of S44 is executed. After the process of S36 is executed and before the process of S44 is executed, the global ID platform 50 acquires the user information 1151 of the user 71 from the authentication server 11, and transmits the acquired user information 1151 of the user 71 to the authentication server 21.
[0103] In S50, when consent information of the user 71 is obtained, the global ID platform 50 requests the authentication server 11 to transmit the user information 1151 of the user 71.
[0104] In S 51 , the authentication server 11 reads out the user information 1151 of the user 71 from the storage device 115 , and transmits the read out user information 1151 of the user 71 to the global ID platform 50 .
[0105] In S 52 , the global ID platform 50 transmits the user information 1151 of the user 71 to the authentication server 21 .
[0106] The processes of S50 to S52 may be executed after the process of S36 is executed and before the process of S44 is executed. The execution timing of the processes of S50 to S52 is not limited to the timing shown in FIGS.
[0107] As described above, the authentication system 1 according to the present embodiment includes the global ID platform 50 that relays information, thereby enabling global login without direct information exchange between authentication servers. This allows a system to be constructed that can exchange information between the authentication server and the global ID platform 50, and therefore the system configuration can be simplified compared to a system in which ID federation is performed by directly exchanging information between the authentication servers of each service providing system.
[0108] Furthermore, a login button (e.g., login buttons 83, 87) and a global login button (e.g., global login buttons 84, 88) are displayed on the login screen for each service (e.g., the first service and the third service) displayed on the display unit 80 of the terminal device 70. By displaying two buttons, the user 71 can visually recognize that he or she must press the login button when logging in to a service for which he or she is registered as a member, and that he or she must press the global login button when globally logging in to a service for which he or she is not registered as a member. By displaying the login button and the global login button on the login screen, convenience for the user 71 can be improved.
[0109] [Variation 1] In the embodiment, an example has been described in which the authentication server stores and manages user information, but the function of managing user information may be provided in a server separate from the authentication server.
[0110] 12 is a diagram showing a schematic configuration of a service providing system 10A according to Modification 1. The service providing system 10A is an alternative to the service providing system 10 of the embodiment. Note that, although the configuration of the service providing system 10A will be representatively described below, a similar configuration can also be adopted for the service providing systems in countries B to D.
[0111] The service providing system 10A includes an information management server 11A, an authentication server 11B, and back-end servers 12 and 13.
[0112] The information management server 11A includes a control device 111A, a ROM, a RAM, a communication device, and a storage device 115A. Note that the ROM, the RAM, and the communication device are not shown in FIG.
[0113] The control device 111A includes a user information management unit 1111A. The control device 111A functions as the user information management unit 1111A by, for example, executing a program stored in a ROM. Note that the user information management unit 1111A may be realized by, for example, dedicated hardware (electronic circuitry).
[0114] The user information management unit 1111A has the same functions as the user information management unit 1111 of the embodiment.
[0115] The storage device 115A is similar to the storage device 115 in the embodiment. The storage device 115A stores user information 1151 and 1152.
[0116] The authentication server 11B includes a control device 111B, a ROM, a RAM, a communication device, and a storage device. Note that the ROM, the RAM, the communication device, and the storage device are not shown in Fig. 12. The authentication server 11B storage device does not store user information 1151 and 1152.
[0117] The control device 111B has an authentication / authorization unit 1112B and a global authentication unit 1113B. The control device 111B functions as the authentication / authorization unit 1112B and the global authentication unit 1113B, for example, by executing a program stored in a ROM. Note that the authentication / authorization unit 1112B and the global authentication unit 1113B may be realized by dedicated hardware (electronic circuitry), for example.
[0118] The authentication / authorization unit 1112B and the global authentication unit 1113B have the same functions as the authentication / authorization unit 1112 and the global authentication unit 1113 of the embodiment.
[0119] Even if the configuration of the service providing system 10A is adopted in the authentication system 1, the same effects as those of the embodiment can be achieved.
[0120] [Variation 2] In the embodiment, an example has been described in which one authentication server (e.g., authentication server 11) is provided for multiple backend servers (e.g., backend servers 12 and 13), but an authentication server may be provided for each backend server. Even in this case, each authentication server exchanges information with other authentication servers via the global ID platform, thereby achieving the same effects as those of the embodiment.
[0121] The embodiments disclosed herein should be considered to be illustrative and not restrictive in all respects. The scope of the present disclosure is defined by the claims, not by the description of the embodiments described above, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]
[0122] 1 Authentication system, 10, 10A, 20, 30, 40 Service providing system, 11, 11B, 21 Authentication server, 11A Information management server, 12, 13, 22, 23, 24 Back-end server, 50 Platform, 60 Network, 70 Terminal device, 71 User, 73, 74 Application, 80 Display unit, 81, 85 ID input field, 82, 86 Password input field, 83, 87 Login button, 84, 88 Global login button, 91 Country selection field, 92 Service selection field, 93 Selection button, 111, 111A, 111B, 211 Control device, 112, 212 ROM, 113, 213 RAM, 114, 214 Communication device, 115, 115A, 215 Storage device, 117, 217 Bus, 1111, 1111A, 2111 User information management section, 1112, 1112B, 2112 authentication and authorization section, 1113, 1113B, 2113 global authentication section, 1151, 1152, 2151, 2152, 2153 user information.
Claims
1. A first server; A second server; and a platform configured to relay information between the first server and the second server; An authentication system comprising: the first server and the second server do not communicate directly with each other; the first server provides a first service to a user; the second server provides a second service to the user; the platform stores first correspondence information regarding the first server and second correspondence information regarding the second server; The first correspondence information is information that associates the first service with the first server, The second correspondence information is information that associates the second service with the second server, When a user authentication request is made from a terminal device operated by a user to the second server, if user information relating to the user is not stored in the second server, The platform comprises: relaying the authentication request from the second server to the first server based on the first correspondence information; The authentication system further comprises: the platform configured to relay an authentication result of the first server in response to the authentication request from the first server to the second server.
2. The authentication system comprises: displaying on the terminal device a screen for receiving authentication, the screen including a first button and a second button; When the first button is pressed as a user authentication request from the terminal device to the second server, if user information about the user is stored in the second server, the user is authenticated in the second server; 2. The authentication system of claim 1, wherein when the second button is pressed as a user authentication request from the terminal device to the second server, if the user information is stored in the first server, the platform relays the authentication request from the second server to the first server, and the first server authenticates the user.
3. The first server stores user information about the user, and the second server If the user information is not stored, when the authentication result indicates successful authentication, the platform sends a consent request to the terminal device to request consent to sharing the user information to the second server; 3. The authentication system according to claim 1, wherein if consent to the consent request is obtained from the terminal device, the platform relays the user information from the first server to the second server.
Citation Information
Patent Citations
Authentication method, terminal device, repeater, and authentication server
JP2006011989A
Method and system for authentication processing
JP2008242684A
Authentication system and authentication method
JP2012164191A
Information processing apparatus, authorization system, and verification method
JP2020036234A
Mediation device, mediation method, program, and mediation system
WO2010110182A1
