Login skip system and program

Abstract

To provide a log-in skip system and a program for smoothly shifting processing by skipping log-in between different domains and sessions, and for easily shifting document data.SOLUTION: A first service providing server stores a first login ID and a first password for logging in to a first service, a second login ID for logging in to a second service, and a third login ID for logging in to a third service in association with each other, logs in to the first service with the first login ID and the first password, and gives permission to log in to the second service with the first login ID when an instruction to shift from the first service to the second service is given. The log-in skip system accesses a second service providing server 2 with a first log-in ID to shift to a second service, and shifts document data in a first service to the second service.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a system that skips login between different domains or sessions, and more particularly to a login skip system and program that eliminates the need for login and enables smooth transition to different processing to share document data. [Background technology]

[0002] [Prior Art] Conventionally, when switching from a first session in a first domain to a second session in a different second domain, it was necessary to newly log in to the second domain.

[0003] [Related Technology] Related prior art includes Japanese Patent Application Publication No. 2002-245011, "Information display control device" (Patent Document 1), Japanese Patent Application Publication No. 2014-032560, "Method and information processing system for transferring member data in a web system" (Patent Document 2), and Japanese Patent Application Publication No. 2016-091166, "Information processing device, user terminal device, and program" (Patent Document 3).

[0004] Patent document 1 describes that a user ID, password, and server address are stored as cookie information on an IC card, and when the address of the server being accessed matches the server address in the cookie information, the user ID and password on the IC card are sent to the server to log in.

[0005] Patent Document 2 describes that when a user requests access to an old system, the old system authenticates the user and returns authentication confirmation information to the user terminal, and when the user terminal provides the authentication confirmation information to the new system, the services of the new system are provided without the user having to log in to the new system.

[0006] Patent Document 3 describes that when the number of successful login authentication attempts exceeds a threshold value and the user accesses from the same wireless access point from the next time onwards, a notification is sent to the effect that omission of a password is permitted in the login request. [Prior art documents] [Patent documents]

[0007] [Patent Document 1] Japanese Patent Application Laid-Open No. 2002-245011 [Patent Document 2] Japanese Patent Application Laid-Open No. 2014-032560 [Patent Document 3] Japanese Patent Application Laid-Open No. 2016-091166 Summary of the Invention [Problem to be solved by the invention]

[0008] As such, in conventional login systems, users had to log in again between different domains or sessions, which was inconvenient for users, prevented smooth transitions in processing, and made it difficult to transfer created document data.

[0009] Patent Documents 1 to 3 do not describe a configuration for skipping login between different domains or sessions to smoothly transition between processes and easily transfer document data.

[0010] The present invention has been made in consideration of the above-mentioned situation, and aims to provide a login skip system and program that can skip logins between different domains or sessions to smooth the transition of processing and easily transfer document data. [Means for solving the problem]

[0011] The present invention, which solves the problems of the above-mentioned conventional examples, is a login skip system that transitions from a first service of a first domain to a second service of a second domain without displaying a login screen on the user terminal, wherein a first service providing server that provides the first service stores a first login ID and first password used to log in to the first service in association with a second login ID used to log in to the second service, and when a request is made from the user terminal to transition from the first service to the second service, if the first login ID and second login ID are associated, the first service providing server grants permission to the second service providing server that provides the second service to allow the user terminal to use the second service with the first login ID, causes the user terminal to access the second service providing server, and provides the document data used in the first service to the second service providing server so that it can be used in the second service, thereby transitioning the user terminal to the second service.

[0012] The present invention is characterized in that in the login skip system, when the status of the document data is changed in the second service, the first service providing server receives information on the status.

[0013] The present invention is characterized in that, in the above-mentioned login skip system, when a second service providing server receives a request from a user terminal to transition from the second service to the first service, the second service providing server allows the user terminal to access the first service providing server, and provides the document data used in the second service to the first service providing server so that it can be used in the first service, and transitions the user to the first service without displaying a login screen on the user terminal, if the permission to use the second service is still valid.

[0014] The present invention is characterized in that in the login skip system, when the status of the document data is changed in the first service, the second service providing server receives information on the status.

[0015] The present invention is a login skip system that transitions from a first service of a first domain to a second service of a second domain or a third service of a third domain without displaying a login screen on a user terminal, wherein a first service providing server that provides the first service stores a first login ID and a first password for logging in to the first service, a second login ID for logging in to the second service, and a third login ID for logging in to the third service in association with each other, and when a request to transition from the first service to the second service or the third service is received from the user terminal, the first service providing server When the first login ID is associated with the second login ID or the third login ID, permission for the user terminal to use the second service or the third service with the first login ID is given to the second service providing server that provides the second service or the third service providing server that provides the third service, the user terminal is made to access the second service providing server or the third service providing server, and the document data used in the first service is provided to the second service providing server or the third service providing server so that it can be used in the second service or the third service, thereby transitioning the user terminal to the second service or the third service.

[0016] The present invention is characterized in that in the login skip system, when the status of the document data is changed in the second service or the third service, the first service providing server receives information on the status.

[0017] The present invention is characterized in that in the above-mentioned login skip system, when the second service providing server transitions from the second service to the third service, if the permission to use the second service and the third service is within a period in which the permission to use the second service and the third service is valid, the second service providing server allows the user terminal to access the third service providing server, provides the document data used in the second service to the third service providing server so that it can be used in the third service, and transitions to the third service without displaying a login screen on the user terminal.

[0018] The present invention is characterized in that in the login skip system, when the status of the document data is changed in the third service, the second service providing server receives information on the status.

[0019] The present invention is characterized in that in the above-mentioned login skip system, when the third service providing server transitions from the third service to the second service, if the permission to use the third service and the second service is within the period in which permission is valid, the third service providing server allows the user terminal to access the second service providing server, provides the document data used in the third service to the second service providing server so that it can be used in the second service, and transitions to the second service without displaying a login screen on the user terminal.

[0020] The present invention is characterized in that in the login skip system, when the status of the document data is changed in the second service, the third service providing server receives information on the status.

[0021] The present invention is a processing program that operates on a first service providing server that provides a first service of a first domain, and that stores a first login ID and first password for logging in to the first service in association with a second login ID for logging in to a second service of a second domain, and that, when transitioning from the first service to a second service, if the first login ID and the second login ID are associated, grants permission to a second service providing server that provides the second service to allow a user terminal to use the second service with the first login ID, causes the user terminal to access the second service providing server, and provides document data used in the first service to the second service providing server so that it can be used in the second service, thereby transitioning the user terminal to the second service.

[0022] The present invention is characterized in that, in the program, the first service providing server is caused to function so as to receive information on the status when the status of the document data is changed in the second service.

[0023] The present invention is a processing program that operates in a second service providing server that provides a second service of a second domain, and is characterized in that, when the second service providing server is transitioned from the second service to the first service, the second service providing server functions to cause a user terminal to access the first service providing server, provide document data used in the second service to the first service providing server so that it can be used in the first service, and transition to the first service without displaying a login screen on the user terminal, as long as the permission to use the second service granted by the first service providing server that provides the first service is valid.

[0024] The present invention is characterized in that, in the program, the second service providing server is caused to function so as to receive information on the status when the status of the document data is changed in the first service.

[0025] The present invention is a processing program that operates on a first service providing server that provides a first service of a first domain, and that stores a first login ID and first password for logging in to the first service, a second login ID for logging in to the second service, and a third login ID for logging in to the third service, in association with each other; and when transitioning from the first service to the second service or the third service, if the first login ID and the second login ID or the third login ID are associated, the program functions to grant permission for the user terminal to use the second service or the third service with the first login ID to the second service providing server that provides the second service or the third service providing server that provides the third service, have the user terminal access the second service providing server or the third service providing server, and provide document data used in the first service to the second service providing server or the third service providing server so that it can be used in the second service or the third service, thereby transitioning to the second service or the third service without displaying a login screen on the user terminal.

[0026] The present invention is characterized in that, in the program, the first service providing server is caused to function so as to receive information on the status when the status of the document data is changed in the second service or the third service.

[0027] The present invention is characterized in that, in the above program, when transitioning from the second service to the third service, the second service providing server is caused to access the user terminal to the third service providing server that provides the third service, and provides the document data used in the second service to the third service providing server so that it can be used in the third service, if the permission to use the second service and the third service given by the first service providing server that provides the first service is valid during that period, thereby transitioning to the third service without displaying a login screen on the user terminal.

[0028] The present invention is characterized in that, in the program, the second service providing server is caused to function so as to receive information on the status when the status of the document data is changed in the third service.

[0029] The present invention is characterized in that, in the above program, when transitioning from the third service to the second service, the third service providing server is caused to access the user terminal to the second service providing server providing the second service, if the permission to use the third service and the second service given by the first service providing server providing the first service is within the period in which it is valid, and provides the document data used in the third service to the second service providing server so that it can be used in the second service, thereby transitioning to the second service without displaying a login screen on the user terminal.

[0030] The present invention is characterized in that, in the program, the third service providing server is caused to function so as to receive information on the status when the status of the document data is changed in the second service. [Effects of the Invention]

[0031] According to the present invention, a first service providing server that provides a first service stores a first login ID and first password used to log in to the first service, in association with a second login ID used to log in to the second service; when a request is made from a user terminal to transition from the first service to the second service, if the first login ID and second login ID are associated, the first service providing server grants permission to the second service providing server that provides the second service to allow the user terminal to use the second service with the first login ID, causes the user terminal to access the second service providing server, and provides the document data used in the first service to the second service providing server so that it can be used in the second service, thereby transitioning the user terminal to the second service, thereby providing a login skip system that has the effect of enabling a smooth transition from the first service to the second service and transferring the document data without displaying a login screen on the user terminal.

[0032] According to the present invention, a first service providing server that provides a first service stores a first login ID and first password used to log in to the first service, a second login ID used to log in to the second service, and a third login ID used to log in to the third service, in association with each other. When a request is made from a user terminal to transition from the first service to the second or third service, if the first login ID is associated with the second login ID or the third login ID, the first service providing server grants permission for the user terminal to use the second or third service with the first login ID to the second service providing server that provides the second service or the third service providing server that provides the third service, allowing the user terminal to access the second or third service providing server, and providing the second or third service providing server with document data used in the first service so that it can be used in the second or third service, thereby transitioning the user terminal to the second or third service. This is a login skip system, which has the effect of enabling a smooth transition from the first service to the second or third service and transferring document data without displaying a login screen on the user terminal.

[0033] According to the present invention, when the second service providing server transitions from the second service to the third service, as long as the permission to use the second service and the third service is still valid, the login skip system allows the user terminal to access the third service providing server, provides the document data used in the second service to the third service providing server so that it can be used in the third service, and transitions to the third service without displaying a login screen on the user terminal.This has the effect of enabling a smooth transition from the second service to the third service and the transfer of document data without displaying a login screen on the user terminal. [Brief explanation of the drawings]

[0034] [Figure 1] FIG. 1 is a schematic diagram of the system. [Figure 2] FIG. 10 is a schematic diagram showing the relationship between a common login ID and first and third login IDs. [Figure 3] FIG. 10 is a flow diagram of a transition process from a first service to a second service. [Figure 4] FIG. 10 is a flow diagram of a transition process from the second service to the third service. [Figure 5] FIG. 1 is a schematic diagram of quote and purchase order processing. [Figure 6] This is a schematic diagram of the screen for creating a quote and purchase order and requesting a signature. [Figure 7] FIG. 10 is a schematic diagram of a status display screen after the estimate and purchase order has been sent. [Figure 8] FIG. 10 is a schematic diagram of a status display screen in accounting process (1). [Figure 9] FIG. 10 is a schematic diagram of a status display screen after the estimate and purchase order has been concluded. [Figure 10] FIG. 10 is a schematic diagram of a status display screen in accounting process (2). DETAILED DESCRIPTION OF THE INVENTION

[0035] An embodiment of the present invention will be described with reference to the drawings. [Outline of the embodiment] In a login skip system (this system) according to an embodiment of the present invention, a first service providing server stores a first login ID and a first password used to log in to a first service, in association with a second login ID used to log in to a second service; a user logs in to the first service using the first login ID and the first password; and when an instruction is given to transition from the first service to the second service, if the first login ID and the second login ID are associated, the system grants permission to the second service providing server that provides the second service to allow the user terminal to use the second service using the first login ID, and causes the user terminal to access the second service providing server, which migrates the document data in the first service to the second service and shares the status of the document data. This allows a smooth transition from the first service to the second service, and the document data is also migrated, without displaying a login screen on the user terminal.

[0036] [This system: Figure 1] This system will be described with reference to Figure 1. Figure 1 is a schematic diagram of the system. As shown in Figure 1, this system includes a first service providing server 1 that provides a first service in a first domain, a second service providing server 2 that provides a second service in a second domain, a third service providing server 3 that provides a third service in a third domain, a user terminal 4, and a network 5.

[0037] The first to third service providing servers 1 to 3 and the user terminal 4 are connected via a network 5, and the user terminal 4 is able to use the first to third services provided by the first to third service providing servers 1 to 3. Here, the domain of the first service, the domain of the second service, and the domain of the third service are all different from each other. However, this system can also be applied to cases where the same domain is used for different services.

[0038] [First to third service providing servers 1 to 3: Figure 2] Next, the first to third service providing servers 1 to 3 are connected with reference to Fig. 2. Fig. 2 is a schematic diagram showing the relationship between the first login ID and the second and third login IDs. First, this system is provided with login IDs (first to third login IDs) for logging in to each service, and permission to log in to the second service or third service using the first login ID for the first service is granted from the first service providing server 1 to the second service providing server 2 or the third service providing server 3, and the user is transferred to the second service or third service without displaying a login screen on the user terminal 4.

[0039] As shown in Figure 2, in this system, the first service providing server 1 stores in a memory unit a first login ID and first password for logging in to the first service, a second login ID for logging in to the second service, and a third login ID for logging in to the third service, in association with each other.On the premise that this association has been made, permission is granted to log in to the second service or the third service using the first login ID.

[0040] The user terminal 4 normally logs in to the first service with a first login ID and a first password, logs in to the second service with a second login ID and a second password, and logs in to the third service with a third login ID and a third password to use each service.

[0041] Furthermore, when the user terminal 4 logs in to the first service using the first login ID and first password, if the first login ID and the second login ID are associated with each other, the first service providing server 1 grants permission to the second service providing server 2 to access the second service using the first login ID. The permission is transmitted in the form of a token (access token). When permission is granted from the first service providing server 1, the second service providing server 2 provides the second service with the first login ID without displaying a login screen on the user terminal 4. Furthermore, an ID token may be issued in addition to the access token to grant access permission. In the above, it has been explained that the second service providing server 2 stores the first login ID and grants access permission to the second service using that first login ID, but it is also possible to grant access permission to the second service using a unique identifier similar to (equivalent to) the first login ID instead of the first login ID.

[0042] Furthermore, a validity period is set for the permission token, and so long as the permission is within the validity period, the second service providing server 2 can access the first service providing server 1 and transition from the second service to the first service without displaying a login screen on the user terminal 4. When the validity period of the permission has expired, the user terminal 4 will need to enter the first login ID and first password on the login screen to log in to the first service again.

[0043] Similarly, when the user terminal 4 logs in to the first service using the first login ID and first password, and the first login ID is associated with the third login ID, the first service providing server 1 grants the third service providing server 3 permission to access the third service using the first login ID. The permission is transmitted in the form of a token (access token). Alternatively, an ID token may be issued in addition to the access token to grant access permission. When permission is granted from the first service providing server 1, the third service providing server 3 causes the user terminal 4 to transition from the third service to the first service without displaying a login screen. In the above, it has been explained that the third service providing server 3 stores the first login ID and grants access permission to the third service using that first login ID, but access permission to the third service may also be granted using a unique identifier similar to (equivalent to) the first login ID instead of the first login ID.

[0044] Furthermore, within the validity period of the permission, the third service providing server 3 can access the first service providing server 1 and transition from the third service to the first service without displaying a login screen on the user terminal 4. When the validity period of the permission has expired, the user terminal 4 will have to log in to the first service again using the first login ID and first password.

[0045] Next, the transition from the second service to the third service will be described. As described above, if a user switches to the second service using the first login ID and then switches to the third service, and the permission for the second service is still valid, and the permission for the third service is still valid, the user can switch from the second service to the third service without displaying a login screen on the user terminal 4.

[0046] The third service providing server 3 has already been granted access permission using the first login ID, so when the second service providing server 2 accesses the third service providing server 3 using the first login ID, the user terminal 4 is transitioned to be able to use the third service using the first login ID. The first to third service providing servers 1 to 3 will be specifically described below.

[0047] [First service provider server 1] As shown in FIG. 2, the first service providing server 1 is a processing device that provides a first service to a user, and a first login ID and a first password are registered in order for the user to use the first service. As shown in FIG. 2, the first service providing server 1 also stores a second login ID for a second service and a third login ID for a third service in association with the first login ID.

[0048] The first service providing server 1 allows the user terminal 4 to log in to the first service using the first login ID and the first password, thereby enabling the first service to be used. Furthermore, when a user terminal 4 that is logged in to the first service of the first service providing server 1 transitions to the second service, the first service providing server 1 sends permission to the second service providing server 2 to log in to the second service using the first login ID, and based on that permission, transitions the user terminal 4 from the first service to the second service using the first login ID, allowing the user terminal 4 to use the second service.

[0049] Furthermore, when a user terminal 4 that is logged in to the first service of the first service providing server 1 transitions to the third service, the first service providing server 1 sends permission to the third service providing server 3 to log in to the third service using the first login ID, and based on that permission, transitions the user terminal 4 from the first service to the third service using the first login ID, allowing the user terminal 4 to use the third service. In this way, when switching services, the first service providing server 1 smoothly switches services on the user terminal 4 without displaying a login screen on the user terminal 4 and forcing the user to log in.

[0050] [Second service provider server 2] The second service providing server 2 is a processing device that provides a second service to the user. Furthermore, the second service providing server 2 stores the second login ID and the second password, and the user terminal 4 logs in to the second service using the second login ID and the second password.

[0051] Furthermore, when a user terminal 4 logged in to the first service transitions to the second service, if permission to log in using the first login ID is given by the first service providing server 1, the second service providing server 2 allows the user terminal 4 to use the second service using the first login ID without displaying a login screen on the user terminal 4. In this way, when switching services, the second service providing server 2 smoothly switches services on the user terminal 4 without displaying a login screen and forcing the user to log in.

[0052] [Third service provider server 3] The third service providing server 3 is a processing device that provides a third service to a user, and a third login ID and a third password are registered in order for the user to use the third service. The third service providing server 3 allows the user terminal 4 to log in to the third service using the third login ID and third password, thereby enabling the user to use the third service.

[0053] Furthermore, when a user terminal 4 logged in to the first service transitions to the third service, if permission to log in using the first login ID is given by the first service providing server 1, the third service providing server 3 allows the user terminal 4 to use the third service using the first login ID without displaying a login screen on the user terminal 4. In this way, when switching services, the third service providing server 3 smoothly switches services on the user terminal 4 without displaying a login screen and forcing the user to log in.

[0054] [User device 4] The user terminal 4 is a user's computer (personal computer) that accesses the first service providing server 1, the second service providing server 2, and the third service providing server 3 and uses the respective services. A user has a login ID and password for each service, and logs in to each service using the login ID.

[0055] [Network 5] The network 5 is assumed to be the Internet, and data sent and received is encrypted.

[0056] [Processing by this system] In this system, the first service providing server 1 registers the first login ID and first password, the second login ID, and the third login ID in association with each other, and stores them in the storage unit. Furthermore, the second service providing server 2 registers a second login ID and a second password and stores them in the storage unit. Furthermore, the third service providing server 3 registers a third login ID and a third password and stores them in a storage unit.

[0057] When the user terminal 4 shifts from a specific service to another service, the login screen of the other service is not displayed, but the first login ID is used to log in to the other service in the background, and a processing screen of the other service is displayed. The process of shifting to another service without displaying the login screen is sometimes called a login skip process. Furthermore, in this system, it is possible to envision cooperation between services, for example, with the first service being accounting processing, the second service being legal processing, and the third service being outsourced processing.

[0058] Furthermore, this system not only allows you to skip logging in, but also transfers (transfers) document data created in the pre-migration service to the post-migration service using an API (Application Programming Interface), allowing you to continue editing and other processing of the document data in the post-migration service.

[0059] If the status (state) of the document data changes due to approval (signing) or editing of the document data in the migrated service, the changed status information is provided to the service before the migration via API, and the status information is shared between services.

[0060] [Transition from Service 1 to Service 2: Figure 3] The transition from the first service to the second service will be described with reference to Fig. 3. Fig. 3 is a flow diagram of the process of transitioning from the first service to the second service. As shown in Figure 3, the transition from the first service to the second service is performed by the first service providing server 1, where the user terminal 4 logs in to the first service using the first login ID and first password (S1), and then performs processing in a specific session of the domain of the first service (S2).

[0061] In response to a request from the user terminal 4, the first service providing server 1 determines whether a transition from a specific session in the domain of the first service to another session in the domain of the second service has occurred (S3), and if a transition has occurred (Yes), the first service providing server 1 grants permission to the second service providing server 2 to log in to the second service with the first login ID and transitions the user terminal 4 to the second service based on the granted permission (S4), and if a transition has not occurred (No), returns to processing S2.

[0062] Then, the first service providing server 1 determines whether there is document data to be transferred from the first service to the second service (S5), and if there is document data to be transferred (if Yes), it passes the document data to the second service providing server 2 via API (S6), and the second service providing server 2 makes the second service available in another session in the domain of the second service using the first login ID (S7).If there is no document data to be transferred (if No), process S6 is skipped and the process proceeds to process S7.

[0063] [Transition from Service 2 to Service 3: Figure 4] Next, the transition from the second service to the third service will be described with reference to Fig. 4. Fig. 4 is a flow diagram of the transition process from the second service to the third service. Furthermore, the premise for transitioning from the second service to the third service is that the user transitions to the second service using the first login ID, and then transitions to the third service using the first login ID, both within the validity period of the permission for the second service and within the validity period of the permission for the third service.

[0064] As shown in FIG. 4, the transition from the second service to the third service is performed by the second service providing server 2 logging in to the second service with the first login ID (S11) and performing processing in a specific session of the domain of the second service (S12).

[0065] In response to a request from the user terminal 4, the second service providing server 2 determines whether a transition from a specific session in the domain of the second service to another session in the domain of the third service has occurred (S13), and if it determines that a transition has occurred (if Yes), it accesses the third service providing server 3 with the first login ID (S14). If a transition has not occurred (if No), the process returns to step S12.

[0066] Next, the second service providing server 2 determines whether there is document data to be transferred from the second service to the third service (S15), and if there is document data to be transferred (if Yes), it passes the document data to the third service providing server 3 via API (S16), and since login with the first login ID has already been permitted, the third service providing server 3 transfers to another session in the domain of the third service using the first login ID, making the third service available (S17).If there is no document data to be transferred (if No), process S16 is skipped and process S17 is proceeded to.

[0067] Here, this system not only has the advantage of being able to seamlessly migrate domains or sessions between the first service, the second service, and the third service, but also makes it easy to automatically transfer document data processed by each service using an API as the service is migrated.

[0068] The document data may be, for example, bill data, document data related to personnel and labor, or document data related to outsourcing, and other data other than document data, such as email addresses related to personnel.

[0069] In addition, when the status of document data changes in the destination service, the destination service provider server notifies the source service provider server of the changed status information (status information) via API, so that the status information can be provided and shared.

[0070] Furthermore, instead of the destination service providing server notifying the source service providing server of the status information, the source service providing server may make an inquiry to the destination service providing server, receive the status information from the destination service providing server, and acquire the status information.

[0071] This system can be used, for example, for outsourcing management, a cloud service that centrally manages contracts, orders, requests, billing, and payments between companies and their business partners. This system is particularly effective for cloud services that enable centralized management of administrative tasks (contracts, billing, ordering, payments, messaging functions, talent management, etc.) that occur between companies and freelancers.

[0072] [Quotation and Purchase Order Processing: Figures 5-10] The processing of the quotation and purchase order will be specifically explained below. The processing of a quotation and purchase order will be explained with reference to Figure 5. Figure 5 is a schematic diagram of the processing of a quotation and purchase order. Figure 6 is a schematic diagram of the screen for creating a quotation and purchase order and requesting a signature, Figure 7 is a schematic diagram of the status display screen after the quotation and purchase order has been sent, Figure 8 is a schematic diagram of the status display screen in accounting process (1), Figure 9 is a schematic diagram of the status display screen after the quotation and purchase order has been concluded, and Figure 10 is a schematic diagram of the status display screen in accounting process (2).

[0073] Here, the screens in Figures 6 to 10 are displayed on the user terminal 4, and show the user terminal 4 first accessing the first service providing server 1, then moving to the second service providing server 2, and then returning to the first service providing server 1 again.

[0074] Then, assuming that the first service provided by the first service providing server 1 is, for example, accounting processing, and the second service provided by the second service providing server 2 is, for example, legal processing, the processing of the estimate and purchase order will be described with reference to FIG.

[0075] As shown in Fig. 5, a quotation and purchase order is created in the first service (accounting processing) (1-1), and as shown in Fig. 6, when the "signature request" (signback) button is selected on the user terminal 4, the system skips login and transitions to the second service (legal processing), where preparation for an electronic signature is made (2-1). Then, in the legal processing, the quotation and purchase order prepared for the electronic signature is sent to the destination (third party), and the destination receives a request for an electronic signature (3-1).

[0076] In the legal processing to which the quotation and purchase order has been sent, the status of the quotation and purchase order is displayed as "Waiting for confirmation," and a link to transition to accounting processing is provided on the screen, as shown in Fig. 7. When the link is selected (returned), the user can transition to accounting processing of the first service providing server 1.

[0077] When the user returns to the accounting process (1-3), the accounting process (1) screen as shown in Fig. 8 is displayed on the user terminal 4. The screen in Fig. 8 also displays the status of the signature request for the quotation and purchase order as "Waiting for confirmation."

[0078] Then, when the destination party executes an electronic signature on the quotation and purchase order (3-2), the legal process receives the sign-back (conclusion) (2-4), the quotation and purchase order is concluded (2-5), and the status "Completed" is displayed on the user terminal 4 as shown in Figure 9.

[0079] If the user terminal 4 remains in the accounting processing state, the accounting processing (2) screen will be displayed as shown in Fig. 10. The screen in Fig. 10 also displays the status of the signback of the quotation and purchase order as "Completed" in conjunction with the legal processing.

[0080] In this system, when transitioning between services, permission is granted to log in using a first login ID from the first service providing server 1, and the user terminal 4 is transitioned to another service using that first login ID. However, it is also possible to store a common login ID and common password in each service providing server in association with the login ID and password of each service, convert them into a common login ID and common password, and log in and transition to another service without displaying a login screen on the user terminal 4, and transfer the document data and share the status of the document data.

[0081] [Effects of the embodiment] According to this system, the first service providing server 1 stores a first login ID and first password for logging in to the first service, a second login ID for logging in to the second service, and a third login ID for logging in to the third service, in association with each other. A user logs in to the first service using the first login ID and first password, and when an instruction is given to switch from the first service to the second service, the first service providing server 1 grants permission to the second service providing server 2 to log in to the second service using the first login ID, and causes the user terminal 4 to switch to the second service using the first login ID, while also transferring the document data in the first service to the second service. This has the effect of enabling a smooth transition from the first service to the second service without displaying a login screen on the user terminal 4, and easily transferring document data.

[0082] According to this system, when the status of document data transferred from the first service to the second service changes, the second service providing server 2 shares status information between the second service providing server 2 and the first service providing server 1, which has the effect of making it easy to recognize status information between services. [Industrial Applicability]

[0083] The present invention is suitable for a login skip system and program that skips login between different domains and sessions to smooth the transition of processes and easily transfer document data. [Explanation of symbols]

[0084] 1...first service providing server, 2...second service providing server, 3...third service providing server, 4...user terminal, 5...network

Claims

1. A login skip system that transitions from a first service of a first domain to a second service of a second domain without displaying a login screen on a user terminal, comprising: a first service providing server that provides the first service stores a first login ID and a first password used to log in to the first service and a second login ID used to log in to the second service in association with each other; A login skip system characterized in that, when a request is made from the user terminal to transition from the first service to the second service, if the first login ID and the second login ID are associated, the first service providing server grants permission to the second service providing server that provides the second service to allow the user terminal to use the second service with the first login ID, allows the user terminal to access the second service providing server, provides document data used in the first service to the second service providing server so that it can be used in the second service, and transitions the user terminal to the second service.

2. 2. The login skip system according to claim 1, wherein when the status of the document data is changed in the second service, the first service providing server receives information about the status.

3. The login skip system described in claim 1 or 2, characterized in that when the second service providing server receives a request from the user terminal to transition from the second service to the first service, if the permission to use the second service is valid, the second service providing server allows the user terminal to access the first service providing server, provides the document data used in the second service to the first service providing server so that it can be used in the first service, and transitions the user terminal to the first service without displaying a login screen on the user terminal.

4. 4. The login skip system according to claim 3, wherein when the status of the document data is changed in the first service, the second service providing server receives information about the status.

5. A login skip system that transitions from a first service of a first domain to a second service of a second domain or a third service of a third domain without displaying a login screen on a user terminal, a first service providing server that provides the first service stores a first login ID and a first password used to log in to the first service, a second login ID used to log in to the second service, and a third login ID used to log in to the third service in association with each other; A login skip system characterized in that, when a request is made from the user terminal to transition from the first service to the second service or the third service, if the first login ID is associated with the second login ID or the third login ID, the first service providing server grants permission for the user terminal to use the second service or the third service with the first login ID to the second service providing server that provides the second service or the third service providing server that provides the third service, allows the user terminal to access the second service providing server or the third service providing server, provides document data used in the first service to the second service providing server or the third service providing server so that it can be used in the second service or the third service, and transitions the user terminal to the second service or the third service.

6. 6. The login skip system according to claim 5, wherein when the status of the document data is changed in the second service or the third service, the first service providing server receives information about the status.

7. The login skip system described in claim 5 or 6, characterized in that when transitioning from the second service to the third service, the second service providing server allows the user terminal to access the third service providing server if the permission to use the second service and the third service is valid, provides the document data used in the second service to the third service providing server so that it can be used in the third service, and transitions to the third service without displaying a login screen on the user terminal.

8. 8. The login skip system according to claim 7, wherein when the status of the document data is changed in the third service, the second service providing server receives information about the status.

9. The login skip system described in claim 5 or 6, characterized in that when transitioning from the third service to the second service, the third service providing server allows the user terminal to access the second service providing server, provides the second service providing server with document data used in the third service so that it can be used in the second service, and transitions to the second service without displaying a login screen on the user terminal, if the permission to use the third service and the second service is valid within the period in which the permission to use the third service and the second service is valid.

10. 10. The login skip system according to claim 9, wherein when the status of the document data is changed in the second service, the third service providing server receives information about the status.

11. A processing program that operates on a first service providing server that provides a first service of a first domain, the first service providing server storing a first login ID and a first password for logging in to the first service and a second login ID for logging in to a second service of a second domain in association with each other; A program characterized by the following: when transitioning from the first service to the second service, if the first login ID and the second login ID are associated, granting permission to a second service providing server that provides the second service to allow the user terminal to use the second service with the first login ID, allowing the user terminal to access the second service providing server, providing document data used in the first service to the second service providing server so that it can be used in the second service, and transitioning the user terminal to the second service.

12. 12. The program according to claim 11, further comprising causing the first service providing server to receive information on the status of the document data when the status of the document data is changed in the second service.

13. a processing program that operates on a second service providing server that provides a second service of a second domain, The second service providing server, A program characterized by causing the user terminal to access the first service providing server when transitioning from the second service to the first service, if the permission to use the second service granted by the first service providing server that provides the first service is valid, and providing document data used in the second service to the first service providing server so that it can be used in the first service, and transitioning to the first service without displaying a login screen on the user terminal.

14. 14. The program according to claim 13, further comprising causing the second service providing server to receive information on the status of the document data when the status of the document data is changed in the first service.

15. A processing program that operates on a first service providing server that provides a first service of a first domain, the first service providing server storing a first login ID and a first password for logging in to the first service, a second login ID for logging in to the second service, and a third login ID for logging in to the third service in association with each other; a program that, when transitioning from the first service to the second service or the third service, if the first login ID is associated with the second login ID or the third login ID, grants permission for the user terminal to use the second service or the third service with the first login ID to a second service providing server that provides the second service or a third service providing server that provides the third service, allows the user terminal to access the second service providing server or the third service providing server, provides document data used in the first service to the second service providing server or the third service providing server so that it can be used in the second service or the third service, and transitions to the second service or the third service without displaying a login screen on the user terminal.

16. 16. The program according to claim 15, further comprising causing the first service providing server to receive status information when the status of the document data is changed in the second service or the third service.

17. The program described in claim 15 or 16, characterized in that when the second service providing server is transitioned from the second service to the third service, if the permission to use the second service and the third service given by the first service providing server that provides the first service is valid within the period in which that permission is valid, the program causes the user terminal to access a third service providing server that provides the third service, provides document data used in the second service to the third service providing server so that it can be used in the third service, and transitions to the third service without displaying a login screen on the user terminal.

18. 18. The program according to claim 17, further comprising causing the second service providing server to receive information on the status of the document data when the status of the document data is changed in the third service.

19. The program described in claim 15 or 16, characterized in that when the third service providing server is transitioned from the third service to the second service, if the permission to use the third service and the second service given by the first service providing server that provides the first service is valid within the period in which that permission is valid, the program causes the user terminal to access the second service providing server that provides the second service, provides document data used in the third service to the second service providing server so that it can be used in the second service, and transitions to the second service without displaying a login screen on the user terminal.

20. 20. The program according to claim 19, further comprising causing the third service providing server to receive information on the status of the document data when the status of the document data is changed in the second service.

Images