Information processing apparatus, information processing method, computer readable medium, and computer program product

Abstract

This invention provides an information processing apparatus, an information processing method, and a computer-readable medium. The information processing apparatus has a memory and one or more processors. The memory stores a history of consent items notified to a user each time they log in and consent items in various services. The processors are controlled in the following manner: when notifying a user of consent items while they are using a service, the processor uses the authentication information of a first service to log in to that service; if the user logs in to a second service (different from the first service) without logging in, upon switching to the second service, the processor uses the history to: if the consent items notified in the first service are the same as those in the second service, the consent item is not notified; if the consent items notified in the first service are different from those in the second service, the different consent item is notified.

Description

Technical Field

[0001] This disclosure relates to information processing apparatus, information processing methods, and computer-readable media. Background Technology

[0002] Japanese Patent No. 4780744 discloses the following technology: On a host side connected to a terminal device via a network, there are: a screen generation control unit that generates a database retrieval control screen according to a request from the browser of the terminal device; and a session checking unit that stores session data, checks the legality of the display screen requested by the browser with reference to the session data, and notifies the screen generation control unit. The session data records: a history of the screens displayed and sequentially transferred by the browser from login to logout; and information related to transfer data for accurately transferring data input to the preceding display screen to the next screen. The session checking unit has the right... The permission checking unit, for requests that contradict the processing flow or screen transfer flow, executes error handling to reject them by issuing an error message. When a request to display a screen comes from the browser, it refers to the registrant database with registered legitimate users to determine whether permissions are available and notifies the screen generation control unit. The session data includes login time, user affiliation, user permission level, and search conditions. The session checking unit has a log recording unit, which generates and saves history management data. The history management data includes information extracted from the session data to identify the user, information indicating the connection time, information indicating the IP address, and processing content.

[0003] Japanese Patent No. 6173112 discloses a system for determining whether to notify a user of consent for using a specified function. The system includes: an acquisition unit that acquires language information and consent information, wherein the language information is used to determine the language corresponding to the user, and the consent information is related to the date and time when the user consents to the consent item; and a determination unit that, upon receiving a user's request to use the specified function, determines whether to notify the user of the consent item based on the date and time of the consent item corresponding to the language information acquired by the acquisition unit and the consent information acquired by the acquisition unit from among multiple consent items corresponding to multiple languages. Summary of the Invention

[0004] When a user is notified of consent when using a service, if the user logs in to the first service and then logs in to the second service (different from the first service) using the authentication information from the first service, the consent cannot be notified because no login screen is displayed when logging in to the second service. Furthermore, if consent is notified every time the user logs in to the second service, the user needs to confirm consent again for consent that is duplicated from the consent given when logging in to the first service. Therefore, the object of this disclosure is to provide an information processing apparatus, information processing method, and computer-readable medium, in which, when a user is notified of consent when using a service, the user logs in to the first service, and even when logging in to the second service (different from the first service) using the authentication information from the first service, consent that is not duplicated from the consent given in the first service can be notified.

[0005] According to a first aspect of this disclosure, an information processing apparatus is provided, comprising a memory and one or more processors. The memory stores a history of consent items notified to a user each time they log in, and consent items in various services. The processors are controlled in the following manner: when a user is notified of consent items while using a service, the user logs in to a first service; when a user logs in to a second service different from the first service without logging in, the user logs in using the authentication information of the first service; when switching to the second service, the user logs in using the history; when the consent items notified in the first service are the same as those in the second service, the user is not notified of the consent item; when the consent items notified in the first service are different from those in the second service, the user is notified of the different consent items.

[0006] According to the second aspect of this disclosure, when a session for utilizing the first or second service ends, the processor deletes the history from the memory.

[0007] According to the third embodiment of this disclosure, if a predetermined time elapses after the transfer from the notification of consent in the first service to the second service, the processor will also notify the consent even if the consent notified in the first service is the same as the consent in the second service.

[0008] According to the fourth embodiment of this disclosure, when a consent matter is notified in the first service, the processor notifies the user in a notification form different from the notification form of the different consent matter.

[0009] According to a fifth aspect of this disclosure, an information processing apparatus is provided, comprising a memory and one or more processors. The memory stores a history of consent items notified to a user each time they log in, and consent items in various services. The processors are controlled in the following manner: when a user is notified of consent items while using a service, the user logs in to a first service; when a user can log in to a second service (different from the first service) using the authentication information of the first service without logging in, the user logs out of the first service when switching from the first service to the second service; when logging in to the second service, the user logs in using the history; when the consent items notified in the first service are the same as those in the second service, the user is not notified of the consent item; when the consent items notified in the first service are different from those in the second service, the user is notified of the different consent items.

[0010] According to a sixth aspect of this disclosure, a computer-readable medium is provided that stores a program for causing a computer to perform processing. The computer includes a memory storing a history of consent items notified to a user each time they log in and consent items in various services. The processing is controlled in the following manner: when a user is notified of consent items while using a service, the user logs in to a first service; when logging in to a second service (different from the first service) using the authentication information of the first service without performing a user login operation, the user logs in to the second service using the history; when transferring to the second service, if the consent items notified in the first service are the same as those in the second service, the user is not notified of the consent item; if the consent items notified in the first service are different from those in the second service, the user is notified of the different consent items.

[0011] According to a seventh aspect of this disclosure, a computer-readable medium is provided that stores a program for causing a computer to perform processing. The computer includes a memory storing a history of consent items notified to a user each time they log in and consent items in various services. The processing is controlled in the following manner: when a user is notified of consent items while using a service, the user logs in to a first service; when a user can log in to a second service (different from the first service) using the authentication information of the first service without requiring a user login, the user logs out of the first service when switching from the first service to the second service; when performing a login operation relative to the second service, the user logs in using the history; when the consent items notified in the first service are the same as those in the second service, the user is not notified of the consent item; when the consent items notified in the first service are different from those in the second service, the user is notified of the different consent items.

[0012] According to the eighth aspect of this disclosure, an information processing method is provided, which stores a history of consent items notified to a user each time they log in and consent items in various services, and controls them in the following manner: when a user is notified of consent items when using a service, the user logs in to the first service; when a user logs in to the second service (different from the first service) without logging in but using the authentication information of the first service, the user logs in to the second service using the history; if the consent items notified in the first service are the same as those in the second service, the user is not notified of the consent item; if the consent items notified in the first service are different from those in the second service, the user is notified of the different consent items.

[0013] (Effect)

[0014] According to the first scheme, when a user is notified of consent matters while using the service, the user logs in to the first service. Even if the user logs in to the second service, which is different from the first service, using the authentication information of the first service, the user can be notified of consent matters that do not overlap with the consent matters in the first service.

[0015] According to the second scheme, the records in the memory can be deleted when the session for using the first service or the second service ends.

[0016] According to the third scheme, if a predetermined time has elapsed since the transfer to the second service was initiated after the consent matters in the first service were communicated, the consent matters communicated in the first service can be communicated.

[0017] According to the fourth scheme, when the consent was notified in the first service, the notification can be delivered in a form that makes it clear to the user that the notification has been given.

[0018] According to the fifth scheme, when a user is notified of consent matters while using the service, the user logs in to the first service. Even if the user logs in to the second service, which is different from the first service, using the authentication information of the first service, the user can be notified of consent matters that do not overlap with the consent matters in the first service.

[0019] According to the sixth scheme, when a user is notified of consent matters while using the service, they log in to the first service. Even if they log in to the second service, which is different from the first service, using the authentication information of the first service, they can still be notified of consent matters that do not overlap with the consent matters in the first service.

[0020] According to the seventh scheme, when a user is notified of consent matters while using the service, the user logs in to the first service. Even if the user logs in to the second service, which is different from the first service, using the authentication information of the first service, the user can be notified of consent matters that do not overlap with the consent matters in the first service.

[0021] According to the eighth scheme, when a user is notified of consent matters while using the service, the user logs in to the first service. Even if the user logs in to the second service, which is different from the first service, using the authentication information of the first service, the user can be notified of consent matters that do not overlap with the consent matters in the first service. Attached Figure Description

[0022] Figure 1 This is a conceptual module structure diagram of a structural example of this embodiment.

[0023] Figure 2 This is an explanatory diagram showing an example of a system structure using this embodiment.

[0024] Figure 3 This is a detailed module structure diagram of a structural example of this embodiment.

[0025] Figure 4 This is an explanatory diagram showing an example of the data structure of the service / agreement item mapping table.

[0026] Figure 5 This is an explanatory diagram showing an example of the data structure of a log table.

[0027] Figure 6 This is a flowchart illustrating a processing example of this embodiment.

[0028] Figure 7 This is a flowchart illustrating a processing example of this embodiment.

[0029] Figure 8 This is a flowchart illustrating a processing example of this embodiment.

[0030] Figure 9 This is a flowchart illustrating a processing example of this embodiment. Detailed Implementation

[0031] Hereinafter, an example of a preferred embodiment for implementing the present disclosure will be described with reference to the accompanying drawings.

[0032] Figure 1 A conceptual modular structure diagram of a structural example of this embodiment is shown.

[0033] Furthermore, a module typically refers to logically separable components such as software (including computer programs and hardware as interpreted "software"). Therefore, in this embodiment, a module refers not only to modules in a computer program but also to modules in a hardware structure. Thus, this embodiment also includes descriptions of computer programs (e.g., programs for causing a computer to perform various steps, programs for causing a computer to function as various units, programs for causing a computer to perform various functions), systems, and methods used to perform these functions. However, for ease of explanation, the terms "store," "make ~ store," and equivalents are used, but in the case of a computer program embodiment, these statements mean stored in a storage device or controlled in a manner that allows storage in a storage device. Furthermore, a module can correspond one-to-one with a function, but in actual installation, a module can be composed of one program, or multiple modules can be composed of one program, and vice versa. Moreover, multiple modules can be executed by a single computer or by multiple computers in a distributed or parallel environment. Additionally, a module can include other modules. Furthermore, the term "connection" hereafter applies not only to physical connections but also to logical connections (e.g., data transmission and reception, instructions, reference relationships between data, login, etc.). "Pre-defined" refers to a situation where a definition is made before the processing of the object being processed. This includes definitions made before the start of processing according to this embodiment, as well as definitions made after the start of processing according to this embodiment but before the processing of the object being processed, based on the current state or previous state. When there are multiple "pre-defined values," they can be different values ​​or two or more values ​​("two or more values" includes all values). The statement "When it is A, proceed to B" means "determine whether it is A; if it is A, then proceed to B." However, cases where determining whether it is A is not required are excluded. Furthermore, when items are listed as "A, B, C," unless otherwise specified, they are all examples, including cases where only one is selected (e.g., only A is selected).

[0034] Furthermore, a system or device includes not only cases where multiple computers, hardware, devices, etc., are connected through communication units such as networks ("networks" include one-to-one corresponding communication connections), but also cases where it is implemented through a single computer, hardware, device, etc. "Device" and "system" are used as synonymous terms. Of course, "system" does not include merely artificially agreed-upon social "structures" (i.e., social systems).

[0035] Furthermore, during each process performed by each module, or in the case of multiple processes performed within a module, information as an object is read from the storage device, and after the process is performed, the processing result is written to the storage device. Therefore, the description of reading from the storage device before processing and writing to the storage device after processing is sometimes omitted.

[0036] The information processing apparatus 100 in this embodiment has the function of notifying a user of their consent when the user utilizes a service. For example... Figure 1 As shown in the example, the information processing device 100 includes at least a processor 105 and a memory 110, configured to exchange data via a bus 198 for connecting them. In addition, the information processing device 100 may also include an output device 185, a receiving device 190, and a communication device 195. Furthermore, the processor 105, memory 110, output device 185, receiving device 190, and communication device 195 exchange data via the bus 198.

[0037] in addition, Figure 1 The block diagram shown also illustrates an example of the hardware structure of a computer implementing this embodiment. The hardware structure of the computer that executes this embodiment is as follows: Figure 1 The computer illustrated herein is specifically a personal computer, a computer capable of functioning as a server, etc. As a specific example, a processor 105 is used as the processing unit, and a memory 110 is used as the storage device.

[0038] There can be one or more processors 105. Processors 105 may include, for example, a CPU (Central Processing Unit), a microprocessor, etc. When using multiple processors 105, they can be either tightly coupled or loosely coupled multiprocessors. For example, multiple processors / cores can be integrated within a single processor 105. Furthermore, it can be configured as a system where multiple computers are connected via a communication channel, but the system is imagined to function as a single computer. Specifically, it can be configured as a loosely coupled multiprocessor cluster system or a computer cluster. The processor 105 executes programs stored in the program memory 140.

[0039] The memory 110 may include, for example, semiconductor memory inside the processor 105 such as registers or cache memory, main memory consisting of RAM (Random Access Memory) or ROM (Read Only Memory) as the main storage device, internal storage devices such as HDD (Hard Disk Drive) or SSD (Solid State Drive) which have the function of persistent storage devices, as well as external storage devices or auxiliary storage devices such as CD, DVD, Blu-ray Disc, USB storage, and memory card. In addition, it may also include storage devices such as servers connected via communication lines.

[0040] The memory 110 includes a data memory 120 primarily used for storing data and a program memory 140 primarily used for storing programs. In addition to storing illustrated information and module programs, the data memory 120 and program memory 140 may also store programs such as the OS used to start the computer and data such as parameters that change appropriately when executing modules.

[0041] Output device 185 may include, for example, a display device 187 and a printing device 189. The display device 187, such as a liquid crystal display, an organic EL display, a 3D display, or a projector, displays the processing results of the processor 105 and the data stored in the data memory 120 as text or image information. The printing device 189, such as a printer or a multifunction printer, prints the processing results of the processor 105 and the data stored in the data memory 120. Furthermore, output device 185 may include a speaker and an actuator for vibrating the device.

[0042] The receiving device 190 may include, for example, an instruction receiving device 192, a document reading device 194, etc. The instruction receiving device 192, such as a keyboard, mouse, microphone, camera (including a gaze detection camera, etc.), receives data generated based on the user's operations on these devices (including actions, voice, gaze, etc.).

[0043] Furthermore, it could be a device like a touchscreen that combines the functions of both a display device 187 and an instruction receiving device 192. In this case, regarding the implementation of keyboard functions, even if there are no physical keys, keyboard functions can be implemented by drawing a keyboard on the touchscreen using software (a so-called software keyboard, also known as an on-screen keyboard, etc.).

[0044] In addition, the user interface mainly uses a display device 187 and an instruction receiving device 192.

[0045] Document reading devices such as scanners and cameras 194 read or capture documents and receive the resulting image data.

[0046] Communication device 195 is a communication line interface such as a network card used to connect to other devices via a communication line.

[0047] In this embodiment, the program memory 140 of the hardware structure reads a computer program as software, and the software and hardware resources work together to implement this embodiment. That is, in the information processing performed by software, hardware resources (including at least processor 105, memory 110, and sometimes output device 185, receiving device 190, and communication device 195) are used to specifically implement this embodiment, making overall use of natural laws.

[0048] in addition, Figure 1 The hardware structure shown is an example, and this implementation is not limited to this one. Figure 1 The structure shown can be any structure capable of executing the modules described in this embodiment. For example, the processor 105 can use a GPU (Graphics Processing Unit, including GPGPU (General-Purpose computing on Graphics Processing Units)), or it can use dedicated hardware (such as application-specific integrated circuits (ASICs) or reconfigurable integrated circuits (FPGAs)) to execute a portion of the modules. Alternatively, some modules can be located in an external system and connected via communication lines. Figure 1 The multiple systems shown are interconnected and work together via communication lines. Furthermore, in addition to personal computers, they can be particularly integrated into portable information communication devices (including mobile phones, smartphones, mobile devices, wearable computers, etc.), information appliances, robots, copiers, fax machines, scanners, printers, multifunction printers (image processing devices with any two or more functions such as scanners, printers, copiers, fax machines, etc.).

[0049] Processor 105 is connected to memory 110, output device 185, receiving device 190, and communication device 195 via bus 198. Processor 105 performs processing according to the program in program memory 140, that is, a computer program that describes the execution sequence of each module. For example, triggered by indicating that the receiving device 192 has received a user operation, processor 105 executes processing based on the module corresponding to the operation in program memory 140, and stores the processing result in data memory 120, outputs it to display device 187, or controls communication device 195 to send it to other devices.

[0050] The memory 110 includes a data memory 120 and a program memory 140, and is connected to the processor 105, the output device 185, the receiving device 190 and the communication device 195 via a bus 198.

[0051] The data storage device 120 has a login log storage module 122 and a service / consent item storage module 124.

[0052] The login log storage module 122 stores a history of consent requests notified to a user each time they log in. The history stored in the login log storage module 122 only needs to contain information that can identify past consent requests notified to the user. Here, "past consent requests" refers to consent requests notified in services used before the service the user intends to use. For example, it could also be consent requests notified during the last login. That is, when services A and B collaborate, transferring from service A to service B is equivalent to consent requests notified in service A. In this case, service A is equivalent to "service 1," and service B is equivalent to "service 2." Furthermore, when services A, B, and C collaborate, transferring to service C in this order is equivalent to consent requests notified in service A, consent requests notified in service B, or consent requests notified in both services A and B. This is because, when transferring to service C, login is performed in service A through explicit user action, while login is performed without user login action during the transfer to service B; login processing occurs in both services A and B. In this case, service A or service B is equivalent to "service 1", and service C is equivalent to "service 2".

[0053] Login log storage module 122, for example Figure 5 The log is stored in the form of table 500 as shown.

[0054] Figure 5 This is an explanatory diagram showing an example of the data structure of log table 500.

[0055] Log table 500 has a log ID field 502, a date and time field 504, a logged-in user ID field 506, a service ID field 508, and a notification message field 510. It stores the history of notified consent items. The log ID field 502 stores information used to uniquely identify the log in this embodiment (specifically, log ID: abbreviation for IDentification). The date and time field 504 stores the date and time when consent items were notified. The logged-in user ID field 506 stores information used to uniquely identify the logged-in user in this embodiment (specifically, the logged-in user ID). The service ID field 508 stores information used to uniquely identify the service used by the user in this embodiment (specifically, the service ID). The notification message field 510 stores the message that was a consent item notified when using the service. It may store the message itself or information used to uniquely identify the message in this embodiment.

[0056] The service / consent terms storage module 124 stores the consent terms for each service. The information stored in the service / consent terms storage module 124 only needs to contain the consent terms specified for each service. The consent terms notification module 144 notifies the user of the consent terms for the service they wish to log in to, based on the information stored in the service / consent terms storage module 124.

[0057] Service / Consensus Item Storage Module 124, for example, Figure 4 The services / agreements shown are stored in the form of Table 400.

[0058] Figure 4 This is an explanatory diagram showing an example of the data structure of the service / agreement item correspondence table 400.

[0059] The service / consent item mapping table 400 has a service ID field 402, a corresponding law ID field 404, a consent item ID field 406, and a message field 408. In this embodiment, the service ID field 402 stores information used to uniquely identify the service in this embodiment (specifically, the service ID). The corresponding law ID field 404 stores information used to uniquely identify the law corresponding to the service in this embodiment (specifically, the corresponding law ID). The consent item ID field 406 stores information used to uniquely identify the consent item in the corresponding law in this embodiment (specifically, the consent item ID). The message field 408 stores a message that is the literal content of the consent item.

[0060] The program memory 140 stores the login processing module 142, the consent notification module 144, and the service module 146.

[0061] The login processing module 142 performs login processing for the service when a user uses the service.

[0062] At this time, the login processing module 142 performs login in the first service. In the second service, which is different from the first service, the user does not perform login operation but uses the authentication information of the first service to log in.

[0063] Service 1 and Service 2 are different services.

[0064] Therefore, users need to log in in order to use the first service, and they also need to log in in order to use the second service.

[0065] In this system, Service 1 and Service 2 collaborate; once a user logs into Service 1, Service 2 can also be used. Specifically, in Service 1, the user needs to log in, but in Service 2, the user can switch to Service 2 (i.e., utilize Service 2) without logging in. This is referred to as collaborative login processing. For example, this can be achieved using a technology called Single Sign-On (SSO).

[0066] The consent notification module 144 notifies the user of consent matters when the user uses the service.

[0067] Here, "notification" refers to the process of informing users of information, which can be displayed on a screen, communicated via voice, or a combination of both.

[0068] Furthermore, the consent notification module 144 controls the process as follows: when notifying a user of consent matters while the user is using the service, the user logs in to the first service and uses the authentication information of the first service. If the user logs in to the second service, which is different from the first service, without logging in, the user logs in the login log storage module 122 when the user switches to the second service. If the consent matters notified in the first service are the same as those notified in the second service, the user is not notified of the consent matters. If the consent matters notified in the first service are different from those notified in the second service, the user is notified of the different consent matters.

[0069] Here, "the consent items notified in the first service are different from the consent items in the second service" means that there are consent items in the original consent items in the second service that are not included in the consent items notified in the first service. In addition, it can also be said to be insufficient in the sense that the number of consent items notified in the first service in the original consent items in the second service is insufficient. As "different", "there are consent items not included in the consent items notified" and "insufficient", for example, it is equivalent to the following situations: (1) the consent items that must be notified in the second service are not present in the consent items notified in the first service; (2) in the consent items that must be notified in the second service, although the item itself is also present in the consent items notified in the first service, its detail is insufficient (for example, it is equivalent to the following situation: the essence of consent item A notified in the first service and consent item B that must be notified in the second service is the same, but consent item A is a subset of consent item B). (a higher-level concept, consent item B is more detailed than consent item A); (3) In the consent items that must be notified in the second service, although the items also exist in the consent items notified in the first service, there are differences in the content to be notified (for example, equivalent to the following situation: although consent item A notified in the first service and consent item B that must be notified in the second service are both the same item, such as consent to the period of saving user information in the service, the values ​​and other items in the consent items are different, such as the period is 30 days in consent item A and 180 days in consent item B); etc.

[0070] Furthermore, by controlling in the following way: using a resume, if the consent terms notified in the first service are the same as those notified in the second service, then the consent terms are not notified; if the consent terms notified in the first service are different from those notified in the second service, then the different consent terms are notified, then the consent terms notified in the second service are also notified appropriately.

[0071] Furthermore, the consent notification module 144 can also delete the log record in the login log storage module 122 when the session for using the first service or the second service ends.

[0072] It can manage notifications of agreed-upon matters on a per-session basis.

[0073] Specifically, when using only a resume, it is possible to prevent the unnotified consents that have already been communicated within the resume from being missed, even if the use occurs after the session has ended.

[0074] Furthermore, the consent notification module 144 can also be configured to notify the user of consent even if the consent notified in the first service is the same as the consent notified in the second service, if a predetermined time has elapsed since the consent notification in the first service was made. If the predetermined time has elapsed, the user is also notified of the consent notified in the first service to draw attention to the situation. Additionally, the processing for determining "the case where a predetermined time has elapsed since the consent notification in the first service was made" can be set to measure time from the moment the consent notification in the first service was made and detect if a transfer to the second service has occurred after the predetermined time has elapsed.

[0075] Furthermore, the consent notification module 144 can also be configured to notify in a different form than the notification form for different consent items when the consent item has been notified in the first service.

[0076] Here, "different notification formats" refers to any notification format that indicates a notification has already been given (conversely, the notification format for different consent items is the same as the notification format for the first time). Examples include: displaying the different consent items in a smaller size; displaying them in a lighter density than the different consent items; and placing the notifications later in the order of the different consent items; etc.

[0077] Furthermore, the consent notification module 144 can also be configured such that when a user is notified of consent when using the service, the user logs in to the first service using the authentication information of the first service. If the user can log in to the second service (which is different from the first service) without needing to log in, then when switching from the first service to the second service, the user logs out of the first service. In other words, although collaborative login processing is possible, the user needs to log out of the first service and perform the login operation for the second service.

[0078] Here, "Exit Service 1" can be an automatic exit or a confirmation from the user regarding exiting Service 1. Furthermore, in the latter case, in addition to confirming the exit from Service 1, the user can also confirm that a login is required to transfer to Service 2.

[0079] In addition, in this case, the session is ended by exiting the first service, but in this case, the history in the login log storage module 122 is not deleted as described above.

[0080] Furthermore, the consent notification module 144 can also be controlled in the following way: when performing a login operation for the second service, the log storage module 122 uses the history. If the consent notification in the first service is the same as the consent notification in the second service, the consent notification is notified. If the consent notification in the first service is different from the consent notification in the second service, the different consent notification is notified.

[0081] Service module 146 also stores service module A 148 and service module B 150, etc.

[0082] Services provided in modules A (148) and B (150), etc., require notification of consent to the user before implementation. This notification is mandated by law. Specific examples will be provided later.

[0083] Figure 2 This is an explanatory diagram showing an example of a system structure utilizing this embodiment.

[0084] For example, to comply with certain legal regulations, specific messages must be displayed to users on login screens, etc. These legal regulations include laws, regulations, and decrees of various countries, and may also include rules and norms.

[0085] Examples of legal provisions requiring users to provide consent include the following: "NIST SP800-53 (Security and Privacy Controls for Federal Information Systems)" and "NIST SP800-171 (Protection of Controlled Unclassified Information in Non-Federal Systems and Agencies)" issued by the National Institute of Standards and Technology (NIST).

[0086] For example, the “SP800-53 AC-8 System Use Notification” requires the following.

[0087] a. Before granting access to the system, the user will be notified via an "Organizational System Use Notification Message or Title" regarding privacy and security in accordance with appropriate laws, standards, guidelines, etc., using the following content. This is one example of consent. Additionally, the information system is an example of a service.

[0088] 1. Users should access the government's information systems.

[0089] 2. The use of information systems is monitored and recorded, which may make them the subject of investigation.

[0090] 3. Unauthorized use of information systems is prohibited and will be subject to criminal and civil penalties.

[0091] 4. During the period of using the information system, it is considered as consent to monitoring and recording.

[0092] b. The notification message or title will continue to be displayed on the screen until the user understands the conditions for using the information system and performs a clear login action or performs a re-login to the information system.

[0093] c. Implement the following in normally public systems.

[0094] 1. Display the “System Usage Conditions Stipulated by the Organization” before allowing further access.

[0095] 2. For systems that fundamentally prohibit behaviors such as surveillance, recording, or monitoring, display the content provided that indicates these behaviors are privacy-conscious.

[0096] 3. Includes a description relating to the use of the authorized system.

[0097] In this implementation, when providing collaborative login processing using multiple services, the user needs to be notified of their consent even when performing these individual services.

[0098] It can also handle situations where all legally required consents are displayed on the login screen of the initially used service. However, in such cases, consents for services not being used are also notified later, adding unnecessary burden to the user. In collaborative login processing, when initially switching from service 1 to service 2, no explicit login action is required from the user, therefore there is no login screen itself. Thus, the timing of notifying the user of consents for service 2 is uncertain.

[0099] Therefore, in this embodiment, when switching from the first service to the second service, the consent items in the second service are notified. Then, the content of the consent items to be notified is made to be different from the consent items notified in the first service, and consent items that are insufficient in the consent items notified in the first service are notified.

[0100] Figure 2 (a) This embodiment is configured as a standalone system architecture. The user device 200 is used by the user, such as a computer (including a laptop computer), a portable terminal, etc.

[0101] User device 200 includes information processing device 100. The user operates user device 200 to utilize services within information processing device 100. When utilizing a service, the user device 200 receives notifications of consent related to the service via its display, speakers, etc.

[0102] Figure 2 (b) This implementation is configured as a network-type system architecture.

[0103] Information processing device 100, user terminal 250A, user terminal 250B, and user terminal 250C are interconnected via communication line 290. Communication line 290 can be wireless, wired, or a combination thereof, such as the Internet or local area network as communication infrastructure. Furthermore, the functionality of information processing device 100 can be implemented as a cloud service.

[0104] Users operate the browser and other devices on user terminal 250 and utilize services within information processing device 100 via communication line 290. When utilizing these services, users are notified of their consent via the display, speaker, and other means on the user terminal 250.

[0105] Specific examples are shown in the notification regarding matters of consent.

[0106] Save the notification history of agreed-upon matters for each session. Refer to the history when transferring from other services. If additional notification of agreed-upon matters is required, then additional notification will be sent; otherwise, no notification will be sent.

[0107] For example, the legal requirements for each service are as follows.

[0108] Service A: Law 1

[0109] Service B: Law 1, Law 2

[0110] Service C: Law 2

[0111] Service D: (Unable to issue a warrant)

[0112] In this case, the following services are transferred.

[0113] (1) In the case of switching from service A to service B, the consent to the additional notification of Decree 2 shall be provided.

[0114] (2) In the case of a transfer from service A to service C, the consent to the additional notification of Decree 2 shall be provided.

[0115] (3) No additional notification is given in the case of a transfer from service B to service A.

[0116] (4) No additional notification is given in the case of a transfer from service B to service C.

[0117] (5) In the event of a transfer from Service D to Service B, notify the parties of consent under Decree 1 and Decree 2.

[0118] Furthermore, the same notification applies to transfers between three or more services. That is, notifications are given only for consent matters that have already been communicated, not for consent matters that have not been communicated up to this point. For example, if a transfer occurs from service A to service C, and then from service C to service B, no additional notification is given. However, if a transfer occurs from service A to service D, and then from service D to service C, notifications are given regarding consent matters stipulated in Regulation 2.

[0119] Figure 3 This is a detailed module structure diagram of a structural example of this embodiment. Here, as an example of notification, a display is used.

[0120] The information processing device 300 includes an authentication / authorization module 305, a message display history saving module 310 for each user connection, a necessary message judgment module 315, a necessary message display module 320, a message display management module 325 for each service, and a message display setting module 330 for each service.

[0121] The authentication / authorization module 305 is connected to the message display history storage module 310 for each user connection, the necessary message judgment module 315, the login screen 355 for each service on the user terminal 350, and the collaboration service (after login) screen 360. The authentication / authorization module 305 processes authentication or authorization requests. For example, it performs authentication (OAuth) processing. Furthermore, it can transfer to other services by calling the message display history storage module 310 for each user connection and storing the display history of legally required response messages. In addition, to handle transfers from other services, it calls the necessary message judgment module 315 and, when necessary, displays legally required response messages.

[0122] The message display history saving module 310 for each user connection is connected to the authentication / authorization module 305, the necessary message judgment module 315, and the necessary message display module 320. The message display history saving module 310 saves the display history of legally mandated messages for each service. For example, it saves the display history for each session.

[0123] The necessary message judgment module 315 is connected to the authentication / authorization module 305, the message display history saving module 310 for each user connection, the necessary message display module 320, and the message display management module 325 for each service. The necessary message judgment module 315 determines whether the message required by the service (the message display management module 325 for each service) is displayed in the session (the message display history saving module 310 for each user connection). Then, if there is no display history for the necessary message, the message is displayed (by the necessary message display module 320).

[0124] The necessary message display module 320 is connected to the message display history saving module 310 for each user connection, the necessary message judgment module 315, and the message display management module 325 for each service. The necessary message display module 320 obtains necessary messages from the message display management module 325 of each service and displays them on the screen. Then, the displayed history is saved in the message display history saving module 310 for each user connection.

[0125] The message display management module 325 for each service is connected to the necessary message judgment module 315, the necessary message display module 320, the message display setting module 330 for each service, and the login screen 355 for each service on the user terminal 350. The message display management module 325 for each service stores the legal compliance messages required for each service.

[0126] Each service's message display setting module 330 is connected to each service's message display management module 325. Each service's message display setting module 330 has the function of allowing the service administrator to register or edit legally required response messages for each service. This can be achieved, for example, through a settings screen based on a web application or local application, or through a command-line based SDK (Software Development Kit). It is primarily used by the service provider. Furthermore, it avoids the need for customers or end users to use it. Services that do not require setting are those that do not need to display legally required response messages. These are considered ordinary services.

[0127] User terminal 350 has a login screen 355 for various services and a collaboration service (after login) screen 360. User terminal 350 is equivalent to Figure 2 The example shown is user terminal 250.

[0128] Each service's login screen 355 is connected to the authentication / authorization module 305 of the information processing device 300 and the message display management module 325 of each service. The login screen 355 for each service is a login screen prepared separately for each service, used to provide collaborative login processing across multiple services. Each service's login screen 355 sends an authentication request or authorization request to the authentication / authorization module 305 of the information processing device 300. Then, it retrieves the legally required response messages for the service from the message display management module 325 of each service in the information processing device 300 and displays them on the screen.

[0129] The collaboration service (after login) uses screen 360 to connect to the authentication / authorization module 305 of the information processing device 300. Screen 360 is the interface for the collaboration service after login. During various operations, authentication or authorization requests are sent to the authentication / authorization module 305 of the information processing device 300 through screen 360 to confirm user permissions, etc.

[0130] Figure 6 This is a flowchart illustrating a processing example of this embodiment. The initial login process in the service is handled through the login screen 355 for each service, the message display management module 325 for each service, the authentication / authorization module 305, and the message display history saving module 310 for each user connection. This is an example of the process of logging into the first service through a user's login operation.

[0131] In step S602, based on the user's operation on the login screen 355 for each service, the service ID of the service the user wants to log in to and the instruction for obtaining the notification message are sent from the user terminal 350 to the message display management module 325 of each service.

[0132] In step S604, the message corresponding to the service the user wants to log in to is sent back to the user terminal 350 from the message display management module 325 for each service. Specifically, the message of the consent item corresponding to the service ID is extracted from the service / consent item mapping table 400 and sent back to the user terminal 350.

[0133] In step S606, the user terminal 350 displays the message received in step S604 on the login screen 355 of each service.

[0134] In step S608, based on the user's operation, the authentication / authorization module 305 performs login processing using the information input to the login screens 355 of each service. The information input to the login screens 355 of each service includes, for example, a login ID and password. Alternatively, the user's biometric information, such as fingerprints or facial images, can also be read.

[0135] In step S610, the authentication / authorization module 305 saves the display history of the message display history for each user connection to the message display history storage module 310. Specifically, the message that is the consent item sent back in step S604 is stored in the log table 500.

[0136] In step S612, the authentication / authorization module 305 conveys the message that the service can be started to the login screen 355 of each service.

[0137] Figure 7This is a flowchart illustrating a processing example of this embodiment. It describes the process of displaying legally required messages when transferring from a logged-in service to another service. This process is handled by screen 360A for collaborative service (after login), screen 360B for collaborative service B, authentication / authorization module 305, necessary message judgment module 315, message display management module 325 for each service, message display history saving module 310 for each user connection, and necessary message display module 320. This is an example of the process of displaying a message indicating consent required to be displayed in the second service when transferring from the first service to the second service under collaborative login processing.

[0138] In step S702, a token is used to transfer the screen from screen 360A of collaboration service (after login) A to screen 360B of collaboration service B. That is, the user is transferred from service A to service B based on their actions.

[0139] In step S704, the information processing device 300 uses the collaboration service B to request a check token from the authentication / authorization module 305 via screen 360B.

[0140] In step S706, the authentication / authorization module 305 requests the necessary message judgment module 315 to make a judgment related to message display.

[0141] In step S708, the necessary message judgment module 315 sends an instruction to the message display management module 325 of each service to obtain the necessary messages in service B.

[0142] In step S710, the message display management module 325 of each service sends the messages to be displayed back to the necessary message judgment module 315. Specifically, the service / agreement item correspondence table 400 is used to extract the messages that should be notified in service B.

[0143] In step S712, the necessary message judgment module 315 sends an instruction to the message display history saving module 310 for each user connection to obtain the message display history.

[0144] In step S714, the message display history saving module 310, which saves the history each time the user connects, sends it back to the necessary message judgment module 315. Specifically, the log table 500UI is used to send back messages that were displayed in the same session in the past.

[0145] In step S716, the necessary message determination module 315 determines whether there exists a history of displaying necessary messages. Specifically, it determines whether the message received in step S710 exists in the message received in step S714. Furthermore, even if a message has already been notified, if a period X, which is a threshold, has elapsed since the date and time of notification, it can be determined that the message received in step S710 does not exist in the message received in step S714. Thus, even if a message is displayed in service A, it becomes a notification recipient if a period X has elapsed since the date and time of display. Moreover, the message displayed in service A is set to a different display format than the message initially displayed in service B. For example, the message initially displayed in service B can be set to a large size, while the message displayed in service A can be set to a small size.

[0146] In step S718, the necessary message determination module 315 sends an instruction to the necessary message display module 320 to display the necessary message in the absence of a display history. That is, "absence of a display history" means that the message received in step S710 is not present in the message received in step S714. Furthermore, if the message received in step S710 is present in the message received in step S714, no further processing after step S718 is required. This is because the message that should be displayed in service B has already been displayed in service A.

[0147] In step S720, the necessary message display module 320 sends an instruction to the message display management module 325 of each service to obtain the necessary message.

[0148] In step S722, the message display management module 325 of each service sends the necessary messages back to the necessary message display module 320.

[0149] In step S724, the necessary message display module 320 displays the history and saves it in the message display history saving module 310 each time the user connects. Specifically, the messages displayed in step S726 are appended to the log table 500.

[0150] In step S726, the necessary message display module 320 instructs the necessary message judgment module 315 to display a message. Of course, in step S726, if there is no necessary message, then there is no need to display the message itself.

[0151] Additionally, if an exit process is performed in service A or service B, the session is terminated, and the data in the login log storage module 122 for that session is deleted.

[0152] Figure 8This is a flowchart illustrating a processing example of this embodiment. When switching from service A to service B, exiting service A requires explicit login processing to service B. Figure 7 The difference in the flowchart shown in the example is that the processing of step S808 and the processing of steps S830 to S834 are added.

[0153] In step S802, a screen transfer is performed from screen 360A of collaborative service (after login) A to screen 355B of login service B using a token. That is, the user is transferred from service A to service B based on their actions. As described later in step S808, in order to transfer to service B, the user needs to log out of service A.

[0154] In step S804, the information processing device 300 uses the login screen 355B of service B to request the authentication / authorization module 305 to check the token.

[0155] In step S806, the authentication / authorization module 305 requests the necessary message judgment module 315 to make a judgment related to message display.

[0156] In step S808, the authentication / authorization module 305 processes the exit from service A. That is, it terminates the session, requiring the user to log in to service B as well. Consequently, the login screen for service B is displayed. Figure 8 In the flowchart shown in the example, the data in the login log storage module 122 is not deleted even if the session ends.

[0157] Additionally, in step S808, the user can either a) exit automatically or b) display a message indicating that they need to exit service A and log in to service B, thus instructing them to exit.

[0158] In step S810, the necessary message judgment module 315 sends an instruction to the message display management module 325 of each service to obtain the necessary messages in service B.

[0159] In step S812, the message display management module 325 of each service sends the message to be displayed back to the necessary message judgment module 315. Specifically, the service / agreement item correspondence table 400 is used to extract the message that should be notified in service B.

[0160] In step S814, the necessary message judgment module 315 sends an instruction to the message display history saving module 310 for each user connection to obtain the message display history.

[0161] In step S816, the message display history saving module 310, which saves the history each time the user connects, sends it back to the necessary message judgment module 315. Specifically, the log table 500 is used to send back the messages that were previously displayed.

[0162] In step S818, the necessary message determination module 315 determines whether there exists a history of displaying necessary messages. Specifically, it determines whether the message received in step S812 exists in the message received in step S816. Furthermore, even if a message has already been notified, if a period X, which is a threshold, has elapsed since the date and time of notification, it can be determined that the message received in step S812 does not exist in the message received in step S816. Thus, even if a message is displayed in service A, it becomes a notification recipient if a period X has elapsed since the date and time of display. Moreover, the message displayed in service A is set to a different display format than the message first displayed in service B. For example, the message first displayed in service B can be set to a large size, while the message displayed in service A can be set to a small size.

[0163] In step S820, the necessary message determination module 315 sends an instruction to the necessary message display module 320 to display the necessary message in the absence of a display history. That is, "absence of a display history" means that the message received in step S812 is not present in the message received in step S816. Furthermore, if the message received in step S812 is present in the message received in step S816, steps S820 to S828 are unnecessary. This is because the message that should be displayed in service B has already been displayed in service A.

[0164] In step S822, the necessary message display module 320 sends an instruction to the message display management module 325 of each service to obtain the necessary message.

[0165] In step S824, the message display management module 325 of each service sends the necessary messages back to the necessary message display module 320.

[0166] In step S826, the necessary message display module 320 displays the history in the message display history storage module 310 for each user connection. Specifically, the messages displayed in step S828 are appended to the log table 500.

[0167] In step S828, the necessary message display module 320 instructs the necessary message judgment module 315, the authentication / authorization module 305, and the login screen 355B of service B to display a message. Of course, in step S828, if there is no necessary message, then the message display instruction itself is not required.

[0168] In step S830, the user uses the login screen 355B of service B to perform login processing for the authentication / authorization module 305.

[0169] In step S832, the authentication / authorization module 305 saves the display history of the user's message display history to the message display history saving module 310 each time the user connects.

[0170] In step S834, the authentication / authorization module 305 conveys the message that service B can be started to the login screen 355B of service B.

[0171] Additionally, after step S808, the processing after step S810 can be skipped, and instead, the normal login process for service B can be performed (specifically, Figure 6 (The flowchart shown in the example illustrates steps S602 to S608 of the process). Therefore, in this case, the consent message from service B is displayed. Where a message identical to the consent message displayed in service A also exists in the consent message of service B, that same message is displayed again when logging into service B.

[0172] Figure 9 This is a flowchart illustrating a processing example of this embodiment. Figure 9 The flowchart shown in the example has been deleted. Figure 8 The flowchart shown in the example illustrates step S808 of the process. That is, while it's possible to log in to service B using service A's authentication information without performing a user login operation (i.e., collaborative login processing is possible), when switching from service A to service B, a login operation for service B is required. Therefore, a message indicating agreement can be displayed when logging into service B. Furthermore, in this... Figure 9 In the flowchart shown in the example, if the session ends, the data in the login log storage module 122 is deleted. This is because, when transferring from service A to service B, service A is not exited.

[0173] In step S902, a screen transfer is performed from screen 360A of collaboration service (after login) A to screen 355B of login service B using a token. That is, the user is transferred from service A to service B based on their actions.

[0174] In step S904, the information processing device 300 uses the login screen 355B of service B to request the authentication / authorization module 305 to check the token.

[0175] In step S906, the authentication / authorization module 305 requests the necessary message judgment module 315 to perform a judgment related to message display.

[0176] In step S908, the necessary message judgment module 315 sends an instruction to the message display management module 325 of each service to obtain the necessary messages in service B.

[0177] In step S910, the message display management module 325 for each service sends the messages to be displayed back to the necessary message judgment module 315. Specifically, the service / agreement item mapping table 400 is used to extract the messages that should be notified in service B.

[0178] In step S912, the necessary message judgment module 315 sends an instruction to the message display history saving module 310 for each user connection to obtain the message display history.

[0179] In step S914, the message display history saving module 310, which saves the history each time the user connects, sends it back to the necessary message judgment module 315. Specifically, the log table 500 is used to send back the messages that were previously displayed.

[0180] In step S916, the necessary message determination module 315 determines whether there exists a history of displaying necessary messages. Specifically, it determines whether the message received in step S910 exists in the message received in step S914. Furthermore, even if a message has already been notified, if a period X, which serves as a threshold, has elapsed since the date and time of notification, it can be determined that the message received in step S910 does not exist in the message received in step S914. Thus, even a message displayed in service A becomes a notification recipient if a period X has elapsed since the date and time of display. Moreover, the message displayed in service A is set to a different display format than the message initially displayed in service B. For example, the message initially displayed in service B can be set to a large size, while the message displayed in service A can be set to a small size.

[0181] In step S918, the necessary message determination module 315 sends an instruction to the necessary message display module 320 to display the necessary message in the absence of a display history. That is, "absence of a display history" means that the message received in step S910 is not present in the message received in step S914. Furthermore, if the message received in step S910 is present in the message received in step S914, steps S918 to S926 are unnecessary. This is because the message that should be displayed in service B has already been displayed in service A.

[0182] In step S920, the necessary message display module 320 sends an instruction to the message display management module 325 of each service to obtain the necessary message.

[0183] In step S922, the message display management module 325 of each service sends the necessary messages back to the necessary message display module 320.

[0184] In step S924, the necessary message display module 320 displays the history in the message display history storage module 310 for each user connection. Specifically, the messages displayed in step S926 are appended to the log table 500.

[0185] In step S926, the necessary message display module 320 instructs the necessary message judgment module 315, the authentication / authorization module 305, and the login screen 355B of service B to display a message. Of course, in step S926, if there is no necessary message, then the message display instruction itself is not required.

[0186] In step S928, the user uses the login screen 355B of service B to perform login processing with the authentication / authorization module 305.

[0187] In step S930, the authentication / authorization module 305 saves the display history relative to the message display history saving module 310 for each user connection.

[0188] In step S932, the authentication / authorization module 305 conveys the message that service B can be started to the login screen 355B of service B.

[0189] Alternatively, after step S906, the processing after step S908 can be skipped, and the normal login process for service B can be performed instead (specifically, Figure 6 (The flowchart shown in the example illustrates steps S602 to S608 of the process). Therefore, in this case, the consent message from service B is displayed. Where a message identical to the consent message displayed in service A also exists in the consent message of service B, that same message is displayed again when logging into service B.

[0190] Furthermore, the described program can be provided by storing it on a recording medium, or it can be provided via a communication device. In this case, for example, the program described above can be understood as a disclosure of a "computer-readable recording medium on which a program is recorded".

[0191] "Computer-readable recording media containing programs" refers to computer-readable recording media containing programs used for the installation, execution, and distribution of programs.

[0192] In addition, recording media include, for example, digital universal optical discs (DVDs) (such as DVD-R, DVD-RW, and DVD-RAM, which are standards defined by the DVD Forum, and DVD+R, DVD+RW, etc., which are standards defined by DVD+RW), optical discs (CDs) (such as CD-ROM, CD-R, and CD-RW), Blu-ray discs (Blu-ray Disc), optical disks (MO), floppy disks (FD), magnetic tapes, hard disks, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, random access memory (RAM), and SD (Secure Digital) memory cards.

[0193] Furthermore, the entire program or a portion thereof can be recorded on the recording medium for storage or distribution. It can also be transmitted via communication media, such as wired or wireless communication networks used in local area networks (LANs), metropolitan area networks (MANs), wide area networks (WANs), the Internet, intranets, and extranets, or combinations thereof, and can also be transmitted via carrier waves.

[0194] Furthermore, the program can be part of or all of other programs, or it can be recorded together with a separate program on a recording medium. It can also be recorded in segments on multiple recording media. Moreover, it can be recorded using methods such as compression or encryption; any method is acceptable as long as it can be recovered.

Claims

1. An information processing apparatus having a memory and one or more processors, the memory stores a history of consent matters notified each time a user logs in and consent matters in each service, the history of consent matters being information capable of determining consent matters notified in the past to the user, the processor controls in such a manner that: when a user is notified of a consent matter at the time of using a service, in a case where login is performed in a first service using authentication information of the first service and login is performed without a login operation of the user in a second service different from the first service, at the time of transition to the second service, using the history, in a case where the consent matter notified in the first service is the same as the consent matter in the second service, the consent matter is not notified, in a case where the consent matter notified in the first service is different from the consent matter in the second service, the different consent matter is notified.

2. The information processing apparatus according to claim 1, wherein the processor deletes the history in the memory in a case where a session for using the first service or the second service ends.

3. The information processing apparatus according to claim 1, wherein in a case where transition to the second service after the consent matter in the first service is notified has elapsed a predetermined time, even in a case where the consent matter notified in the first service is the same as the consent matter in the second service, the processor notifies the consent matter.

4. The information processing apparatus according to claim 3, wherein in a case where the consent matter notified in the first service is notified, the processor notifies in a notification form different from a notification form of the different consent matter.

5. An information processing apparatus having a memory and one or more processors, the memory stores a history of consent matters notified each time a user logs in and consent matters in each service, the history of consent matters being information capable of determining consent matters notified in the past to the user, the processor controls in such a manner that: when a user is notified of a consent matter at the time of using a service, in a case where login is performed in a first service using authentication information of the first service and login is capable of being performed without a login operation of the user in a second service different from the first service, at the time of transition from the first service to the second service, the first service is exited, at the time of performing a login operation for the second service, using the history, in a case where the consent matter notified in the first service is the same as the consent matter in the second service, the consent matter is not notified, in a case where the consent matter notified in the first service is different from the consent matter in the second service, the different consent matter is notified.

6. A computer-readable medium storing a program for causing a computer to execute a process, wherein, the memory stores a history of consent matters notified each time a user logs in and consent matters in each service, the history of consent matters being information capable of determining consent matters notified in the past to the user, in the processing, in such a manner that: When the user is notified of the consent matter at the time of using the service, the login is performed in the first service, the authentication information of the first service is used, and the login is performed without the login operation of the user in the second service different from the first service. In the case where the login is performed without the login operation of the user in the second service different from the first service, the history is used at the time of shifting to the second service, the consent matter notified in the first service is the same as the consent matter in the second service, the consent matter is not notified, and the consent matter notified in the first service is different from the consent matter in the second service, the different consent matter is notified.

7. A computer-readable medium storing a program for causing a computer to execute a process, wherein, The history of the consent matter notified at the time of the login of the user each time and the consent matter in each service are stored in the memory possessed by the computer, the history of the consent matter is information capable of determining the consent matter notified to the user in the past, In the processing, the control is performed in the following manner: When the user is notified of the consent matter at the time of using the service, the login is performed in the first service, the authentication information of the first service is used, and the login is performed without the login operation of the user in the second service different from the first service. In the case where the login is performed without the login operation of the user in the second service different from the first service, the history is used at the time of shifting to the second service, the consent matter notified in the first service is the same as the consent matter in the second service, the consent matter is not notified, and the consent matter notified in the first service is different from the consent matter in the second service, the different consent matter is notified. The following processing is performed:

8. An information processing method, wherein, The history of the consent matter notified at the time of the login of the user each time and the consent matter in each service are stored, the history of the consent matter is information capable of determining the consent matter notified to the user in the past, In the processing, the control is performed in the following manner: When the user is notified of the consent matter at the time of using the service, the login is performed in the first service, the authentication information of the first service is used, and the login is performed without the login operation of the user in the second service different from the first service. In the case where the login is performed without the login operation of the user in the second service different from the first service, the history is used at the time of shifting to the second service, the consent matter notified in the first service is the same as the consent matter in the second service, the consent matter is not notified, and the consent matter notified in the first service is different from the consent matter in the second service, the different consent matter is notified.

9. A computer program product comprising a program which causes a computer to execute a process, wherein, The history of the consent matter notified at the time of the login of the user each time and the consent matter in each service are stored in the memory possessed by the computer, the history of the consent matter is information capable of determining the consent matter notified to the user in the past, In the processing, the control is performed in the following manner: When the user is notified of the consent matter at the time of using the service, the login is performed in the first service, the authentication information of the first service is used, and the login is performed without the login operation of the user in the second service different from the first service. In the case where the login is performed without the login operation of the user in the second service different from the first service, the history is used at the time of shifting to the second service, the consent matter notified in the first service is the same as the consent matter in the second service, the consent matter is not notified, and the consent matter notified in the first service is different from the consent matter in the second service, the different consent matter is notified. When a login operation for a second service is performed, using the history, in a case where the consent matter notified in the first service is the same as the consent matter in the second service, the consent matter is not notified, and in a case where the consent matter notified in the first service is different from the consent matter in the second service, the different consent matter is notified.

Images