Management device of identification information

JP2025028461APending Publication Date: 2025-03-03NTT DOCOMO INC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023133290
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-08-18
Publication Date
2025-03-03

AI Technical Summary

Benefits of technology

【0006】 本開示によれば、ユーザと取引する複数の金融機関のクレデンシャルの仕様が区々であっても、クレデンシャルの一元管理が容易になる。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025028461000001_ABST
    Figure 2025028461000001_ABST
Patent Text Reader

Abstract

To facilitate unified management of credentials, even if specifications of the credentials for each service are divisional.SOLUTION: A management device 10 has an acquisition part 160a, a first generation part 160b, a second generation part 160c, and a control part 160d. The acquisition part 160a acquires a plurality of kinds of identification information constituting credentials. The first generation part 160b generates coupling information in which the plurality of kinds of acquired identification information is coupled to each other while sandwiching delimiter characters therebetween. The second generation part 160c encrypts the coupling information and generates encryption information. When detecting use start of service by a user, the control part 160d transmits each identification information obtained by decoding the encryption information to a server providing the service, and tries to authenticate a user. When the user authentication has continuously failed N times (integer equal to and less than M-1, M is integer of 2 or more, which is determined for each of the service), the control part 160d suspends the trial of the subsequent user authentication.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a management device for multiple types of identification information used for user authentication. [Background technology]

[0002] In recent years, account aggregation has been attracting attention. Account aggregation refers to a service that displays transaction information and the like of accounts held by a user at multiple financial institutions on one screen. Specific examples of transaction information include deposit and withdrawal history and usage history. Prior art related to account aggregation includes the technology disclosed in Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2011-128985 A Summary of the Invention [Problem to be solved by the invention]

[0004] In account aggregation, ensuring security is important, and management of financial institution credentials is particularly important. A financial institution's credentials are multiple types of identification information, such as IDs and passwords, used to authenticate the source of access to transaction information. In normal communication services, the security of identification information for user authentication is often ensured by hashing and storing the identification information. However, it is difficult to restore the identification information before hashing from the hashed identification information, and this is not applicable to account aggregation, which requires accessing the server of each financial institution to collect transaction information. For this reason, in conventional account aggregation, there are many cases where encryption of the memory contents of the storage device that stores the credentials (i.e., storage-level encryption) is relied upon, and security is not necessarily sufficient. In addition, the number of multiple types of identification information that make up the credentials and the specifications of each identification information often vary from financial institution to financial institution, making it difficult to centrally manage the credentials. [Means for solving the problem]

[0005] A management device according to a preferred embodiment of the present disclosure includes an acquisition unit, a first generation unit, a second generation unit, a storage unit, and a control unit. The acquisition unit acquires a plurality of types of identification information used when a server providing a service to a preregistered user authenticates an accessing user. In the first embodiment, the type and number of the plurality of types of identification information used when the server authenticates an accessing user are determined for each service. The first generation unit generates combined information by combining each of the plurality of types of identification information with one or more delimiters in between. In the first embodiment, the delimiter is a character different from any of the characters available for each of the plurality of types of identification information in the plurality of services. The second generation unit generates encrypted information by encrypting the combined information generated by the first generation unit. The storage unit stores the encrypted information in association with the user and the service. When the control unit detects that the user has started using the service, the control unit transmits to the server a plurality of types of identification information obtained by decrypting the encrypted information stored in the storage unit in association with the user and the service. The control unit suspends subsequent attempts at user authentication when user authentication using multiple types of identification information obtained by decrypting the encrypted information stored in the storage unit fails N times in a row. In a first aspect, N is a positive integer equal to or smaller than M-1, and M is an integer equal to or larger than 2 that is determined for each service in order to reject subsequent authentication attempts when authentication fails M times in a row. Effect of the Invention

[0006] According to the present disclosure, it becomes easy to centrally manage credentials even if the credential specifications of multiple financial institutions that conduct transactions with a user vary. [Brief description of the drawings]

[0007] [Figure 1] 1 is a diagram illustrating an example of a configuration of a management device 10 according to an embodiment of the present disclosure. [Diagram 2] FIG. 13 is a diagram showing an example of a management table TBL. [Diagram 3]11 is a flowchart showing a process flow in a storage mode operation executed by the processor 160 of the management device 10 according to a program PR1. [Figure 4] 11 is a flowchart showing a process flow in a usage mode operation executed by a processor 160 of a management device 10 according to a program PR1. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] (A. Embodiment) FIG. 1 is a diagram showing an example of the configuration of a management device 10 according to an embodiment of the present disclosure. The management device 10 is a device that provides account aggregation. As described above, account aggregation is a service that displays transaction information and the like of accounts held by a user who has previously registered to use account aggregation (hereinafter, a registered user) at multiple financial institutions, etc., all at once on one screen. In addition to the management device 10, FIG. 1 also shows a terminal device 20 used by the registered user. The management device 10 and the terminal device 20 are connected to a communication network such as the Internet by wire or wirelessly. The management device 10 communicates with the terminal device 20 via the communication network.

[0009] Each financial institution has a server (hereinafter, financial service server) for realizing a financial service that provides transaction information related to an account via a communication network. The financial service server is not shown in FIG. 1. The management device 10 acquires transaction information related to a registered user by communicating with the financial service server of the financial institution in which the registered user has an account. The management device 10 generates image data representing an image in which the transaction information acquired from the financial service server is arranged, and transmits the image data to the terminal device 20, thereby causing the terminal device 20 to display an image represented by the image data, thereby realizing account aggregation.

[0010] To use financial services, a user must be authenticated using credentials (multiple types of identification information such as a user ID and password) set for that user. The management device 10 is a device that manages the credentials of registered users. As mentioned above, the specifications of credentials vary from financial institution to financial institution, and conventionally, it has been difficult to centrally manage multiple credentials with different specifications. The management device 10 is a device that facilitates centralized management of multiple credentials with different specifications. The following explanation will focus on the management device 10.

[0011] 1, the management device 10 includes a communication device 130, a storage device 150, a processing device 160, and a bus 190. The communication device 130, each of the storage device 150, and the processing device 160 are connected to each other by the bus 190 for communicating information. The bus 190 may be configured using a single bus, or may be configured using different buses between the devices.

[0012] The communication device 130 is hardware (transmitting / receiving device) for communicating with other devices via a communication line in a wired or wireless manner. The communication device 130 is also called, for example, a network device, a network controller, a network card, or a communication module. Examples of other devices that communicate with the communication device 130 via a communication line include a financial service server and a terminal device 20.

[0013] The storage device 150 is a recording medium readable by the processing device 160. The storage device 150 includes, for example, a nonvolatile memory and a volatile memory. The nonvolatile memory includes, for example, a ROM (Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), or an EEPROM (Electrically Erasable Programmable Read Only Memory). The volatile memory is, for example, a RAM (Random Access Memory). The nonvolatile memory of the storage device 150 stores a program PR1 that causes the processing device 160 to execute a management method specific to the present disclosure. The volatile memory of the storage device 150 is used as a work area when executing the program PR1.

[0014] The storage device 150 also stores a management table TBL for managing the credentials of registered users. FIG. 2 is a diagram showing an example of the management table TBL. As shown in FIG. 2, the management table TBL is a collection of multiple records. Each record includes, in association with a user identifier that uniquely identifies a registered user, a financial institution identifier that uniquely identifies a financial institution in which the registered user has an account, and encryption information. The encryption information stored in the management table TBL in association with the user identifier and the financial institution identifier is generated based on multiple types of identification information (i.e., credentials) for user authentication of an access source that accesses a financial service server of the financial institution.

[0015] As described above, the types and number of the multiple types of identification information constituting the credentials are determined for each financial service. For example, the credentials for Bank A are composed of a user ID ("User01" in the example shown in FIG. 2), a password ("pwd01" in the example shown in FIG. 2), and a branch code of the branch where the account is set up ("001" in the example shown in FIG. 2). On the other hand, the credentials for Bank B are composed of a user ID ("User02" in the example shown in FIG. 2) and a password ("pwd02" in the example shown in FIG. 2). A specific method for generating encrypted information from a user's credentials will be made clear later. Storage device 150 is an example of a storage unit in this disclosure.

[0016] The processing device 160 includes one or more central processing units (CPUs). The one or more CPUs are an example of one or more processors. Each of the processors and the CPUs is an example of a computer. When the processing device 160 is instructed to execute the program PR1 by an operation on the input device 110, the processing device 160 reads the program PR1 from the non-volatile memory to the volatile memory. Then, the processing device 160 executes the program PR1 read into the volatile memory. The processing device 160 operating according to the program PR1 functions as the acquisition unit 160a, the first generation unit 160b, the second generation unit 160c, and the control unit 160d shown in FIG. 1. That is, the acquisition unit 160a, the first generation unit 160b, the second generation unit 160c, and the control unit 160d in FIG. 1 are software modules realized by operating the processing device 160 according to software. The functions of the acquisition unit 160a, the first generation unit 160b, the second generation unit 160c, and the control unit 160d are as follows.

[0017] The acquiring unit 160a acquires the credentials of the registered user by receiving a message instructing the registration of the credentials from the terminal device 20. This message includes a user identifier indicating the registered user who sent the message, a financial institution identifier indicating the financial institution that registers the credentials, and the credentials. In other words, the acquiring unit 160a acquires the credentials of the registered user for each financial institution.

[0018] The first generating unit 160b generates combined information by combining each of the multiple types of identification information acquired by the acquiring unit 160a for each financial institution, with one or more delimiters in between. The delimiter is a character that is different from any of the characters that can be used for each of the identification information in each financial institution. For example, when the characters that can be used for the identification information are alphabets and numbers, specific examples of the delimiter include a tab, a backslash, a comma, or a space. In this embodiment, a tab (\t) is used as the delimiter.

[0019] In this embodiment, the first generating unit 160b uses the credentials acquired by the acquiring unit 160a to attempt to access the financial service server of the financial institution corresponding to the credentials, and generates combined information if the access is successful. The first generating unit 160b determines whether the access is successful by referring to a message returned from the financial service server. From the viewpoint of ensuring security, it is preferable that the credentials are updated at regular intervals, in order to avoid generating combined information based on old credentials.

[0020] In this embodiment, the order of the identification information when combining the identification information constituting the credential with a delimiter between them is predetermined for each financial institution. This is to avoid confusion of identification information when restoring the identification information from encrypted information, such as mistakenly taking a user ID as a password and mistakenly taking a password as a user ID.

[0021] The second generating unit 160c generates encrypted information by encrypting the combined information generated by the first generating unit 160b and converting the encrypted combined information into a character string using an existing technology such as base64. The second generating unit 160c writes the generated encrypted information in the management table TBL in association with a user identifier and a financial institution identifier.

[0022] When the control unit 160d detects that a user has started using account aggregation, it reads out encrypted information stored in the management table TBL in association with the user from the management table TBL for each financial institution. Next, the control unit 160d converts the read encrypted information into binary data and then decrypts it to restore the combined information, and extracts each piece of identification information separated by a delimiter from the restored combined information. The control unit 160d then attempts to authenticate the user by sending the extracted multiple types of identification information to the corresponding financial service server. The control unit 160d determines whether the access is successful by referring to a message returned from the financial service server.

[0023] If the user authentication is successful, the control unit 160d acquires transaction information from the financial service server and provides the acquired transaction information to the user for whom the start of use of account aggregation has been detected. If the user authentication fails, the control unit 160d notifies the user for whom the start of use of account aggregation has been detected that the user authentication has failed. In user authentication, if authentication fails M (an integer of 2 or more) times in a row, subsequent authentication attempts are often rejected, and the value of M is determined for each service. For this reason, if access using credentials restored from encrypted information fails N times in a row, the control unit 160d refrains from attempting user authentication thereafter. N is a positive integer equal to or less than M-1. The number of times user authentication has failed is managed by a trial counter stored in the storage device 150 for each user and each financial institution.

[0024] In this embodiment, the control unit 160d notifies the user of the access failure in a PUSH format such as sending an e-mail at the time of the first failure, but notifies the user of the access failure from the second failure onwards by displaying a message indicating the access failure on the screen for providing information by account aggregation. The reason for notifying the user in a PUSH format only at the time of the first failure is as follows.

[0025] As described above, in this embodiment, since the encrypted information is generated based on the correct credentials that have succeeded in the user authentication, basically, the attempt of user authentication by the control unit 160d does not fail. The only reason that the attempt of user authentication by the control unit 160d fails is when, after the credential is registered in the management device 10, the credential registered on the financial institution side is updated, while the credential registered in the management device 10 is not updated. The causes of such a situation include, first, forgetting to update the credential registered in the management device 10, and, second, the registered user feels uncomfortable with the access by the management device 10 and intentionally not updating the credential registered in the management device 10. If the registered user intentionally does not update the credential registered in the management device 10, if the user is notified of the access failure many times per day, some users may have a sense of distrust, thinking, "Isn't this system trying to access the financial service server many times?" For this reason, in this embodiment, the notification to the user in the PUSH format is limited to the first failure.

[0026] Furthermore, the processing device 160 operating according to the program PR1 performs a storage mode operation and a usage mode operation. The storage mode operation is an operation of generating encrypted information based on the user's credentials and writing it to the management table TBL. The usage mode operation is an operation of reading encrypted information from the management table TBL and accessing the financial institution's server using the read encrypted information.

[0027] Fig. 3 is a flowchart showing the flow of processing in the operation of the storage mode. As shown in Fig. 3, the operation of the storage mode includes an acquisition process SA100, a first trial process SA110, a first determination process SA120, a first generation process SA130, a second generation process SA140, and a first notification process SA150.

[0028] In the acquisition process SA100, the processing device 160 functions as an acquisition unit 160a. In the acquisition process SA100, the processing device 160 communicates with the terminal device 20 using the communication device 130 to acquire a user identifier of a registered user, a financial institution identifier of a financial institution where the user has an account, and credentials for accessing the account.

[0029] In the first trial process SA110, the first determination process SA120, the first generation process SA130, and the first notification process SA150, the processing device 160 functions as a first generation unit 160b. In the first trial process SA110, the processing device 160 attempts user authentication using the credentials acquired in the acquisition process SA100. In the first determination process SA120, the processing device 160 determines whether or not the user authentication in the first trial process SA110 has been successful.

[0030] If the user authentication in the first trial process SA110 is unsuccessful, the judgment result of the first determination process SA120 is "No." If the judgment result of the first determination process SA120 is "No," the processing device 160 ends the operation in the storage mode after executing the first notification process SA150. In the first notification process SA150, the processing device 160 notifies the registered user who is the sender of the uploaded credentials that the user authentication using the uploaded credentials was unsuccessful.

[0031] If the user authentication in the first trial process SA110 is successful, the judgment result of the first judgment process SA120 is "Yes". If the judgment result of the first judgment process SA120 is "Yes", the processing device 160 executes the first generation process SA130, and further executes the second generation process SA140 to end the operation of the storage mode. In the first generation process SA130, the processing device 160 generates combined information based on the credentials acquired in the acquisition process SA100. In the second generation process SA140 subsequent to the first generation process SA130, the processing device 160 functions as the second generation unit 160c. In the second generation process SA140, the processing device 160 generates encrypted information based on the combined information generated in the first generation process SA130. Then, in the second generation process SA140, the processing device 160 writes the encrypted information generated based on the combined information generated in the first generation process SA130 in association with the user identifier and financial institution identifier acquired in the acquisition process SA100 into the management table TBL.

[0032] 4 is a flowchart showing the flow of processing in the operation of the usage mode. The operation of the usage mode includes a read process SB100, a second determination process SB110, a second trial process SB120, a third determination process SB130, a second notification process SB140, and an information provision process SB150. In the read process SB100, the second determination process SB110, the second trial process SB120, the third determination process SB130, the second notification process SB140, and the information provision process SB150, the processing device 160 functions as the control unit 160d.

[0033] In the read process SB100, the processing device 160 reads, from the management table TBL, the encrypted information stored in the management table TBL in association with the registered user for whom the start of use of account aggregation has been detected, for each financial institution. The processes following the second determination process SB110 are executed for each credential read in the read process SB100, i.e., for each financial institution.

[0034] In the second determination process SB110, the processing device 160 determines whether the value indicated by the attempt count counter corresponding to the financial institution attempting to access the financial services server (hereinafter, the target financial institution) is less than the attempt count upper limit M for the target financial institution. If the determination result of the second determination process SB110 is "No", the processing device 160 ends the operation of the usage mode without attempting user authentication using the credentials read in the read process SB100.

[0035] If the determination result of the second determination process SB110 is "Yes", the processing device 160 executes a second attempt process SB120. In the second attempt process SB120, the processing device 160 attempts user authentication using the credentials read from the management table TBL in the read process SB100.

[0036] In the third determination process SB130, the processing device 160 determines whether or not the user authentication in the second trial process SB120 was successful. If the user authentication in the second trial process SB120 was successful, the determination result of the third determination process SB130 is "Yes". If the determination result of the third determination process SB130 is "Yes", the processing device 160 resets the trial number counter for the target financial institution to 0 and executes the information provision process SB150. In the information provision process SB150, the processing device 160 obtains transaction information from the server of the financial institution that has succeeded in the user authentication, generates image data representing an image in which the transaction information is arranged, and transmits the image data to the terminal device 20.

[0037] If the user authentication in the second trial process SB120 is unsuccessful, the judgment result of the third determination process SB130 is "No." If the judgment result of the third determination process SB130 is "No," the processing device 160 increments the attempt counter for the target financial institution and executes the second notification process SB140. In the second notification process SB140, the processing device 160 notifies the user for whom the start of account aggregation usage has been detected that user authentication using pre-registered credentials was unsuccessful.

[0038] As described above, according to this embodiment, multiple types of identification information that make up a credential are converted into a single combined information by combining each piece of identification information with a delimiter between them, and the combined information is then encrypting and managed as a single encrypted information, making it easy to centrally manage credentials even if the specifications of the credentials vary from financial institution to financial institution.

[0039] (B: Transformation) The present disclosure is not limited to the above-described exemplary embodiments. Specific modified aspects are as follows. Two or more aspects selected from the following examples may be combined. (B-1: Variation 1) The above embodiment was an example of application to managing credentials for using financial services, but the present disclosure may also be applied to managing credentials for using services other than financial services, such as watching or posting videos, online games, or online shopping.

[0040] (B-2: Variation 2) In the above embodiment, the order of the multiple types of identification information constituting the credential when the multiple types of identification information are combined with a delimiter between them is determined for each financial service. However, when the multiple types of identification information include a first type of identification information, a second type of identification information, and a third type of identification information, at least one of the number or type of delimiter between the first type of identification information and the second type of identification information and the number or type of delimiter between the second type of identification information and the third type of identification information may be different. For example, when the credential is composed of a bank code, an account number, and a branch number, it is possible to place "¥n" between the bank code and the account number, and "¥n", "¥n", or "¥t" between the account number and the branch number. According to this aspect, the type of each identification information can be identified based on the type or number of delimiters between the first type of identification information, the second type of identification information, and the third type of identification information. Furthermore, one record may contain multiple pairs of financial institution identifiers and credentials, with spaces separating each pair as delimiters.

[0041] (B-2: Variation 3) In the above embodiment, the first generating unit 160b attempts to access the server using the multiple types of identification information acquired by the acquiring unit 160a, and generates the combined information if the access is successful. However, the access to the server by the first generating unit 160b may be omitted. That is, the first generating unit 160b may unconditionally generate the combined information based on the multiple types of identification information acquired by the acquiring unit 160a.

[0042] (B-4: Variation 4) The acquiring unit 160a, the first generating unit 160b, the second generating unit 160c, and the control unit 160d in the above embodiment are software modules. However, any one, any two, any three, or all of the acquiring unit 160a, the first generating unit 160b, the second generating unit 160c, and the control unit 160d may be hardware modules. Specific examples of hardware modules include DSP (Digital Signal Processor), ASIC (Application Specific Integrated Circuit), PLD (Programmable Logic Device), and FPGA (Field Programmable Gate Array). Even if any one, any two, any three, or all of the acquiring unit 160a, the first generating unit 160b, the second generating unit 160c, and the control unit 160d are hardware modules, the same effects as those of the above embodiment are achieved.

[0043] (B-4: Variation 4) In the above embodiment, the program PR1 is stored in the storage device 150 of the management device 10, but the program PR1 may be manufactured or sold separately. When selling the program PR1, the program PR1 may be provided to a purchaser by writing the program PR1 to a computer-readable recording medium such as a flash ROM and distributing it, or by downloading it via a telecommunications line.

[0044] (C:Other) (1) In the above-described embodiment, ROM, RAM, etc. are given as examples of storage device 150, but storage device 150 may also be a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disc), a smart card, a flash memory device (e.g., a card, a stick, a key drive), a CD-ROM (Compact Disc-ROM), a register, a removable disk, a hard disk, a floppy (registered trademark) disk, a magnetic strip, a database, a server, or any other suitable storage medium.

[0045] (2) In the above-described embodiments, the described information, signals, etc. may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0046] (3) In the above-described embodiment, the input / output information, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. The input / output information, etc. may be overwritten, updated, or added. The output information, etc. may be deleted. The input information, etc. may be transmitted to another device.

[0047] (4) In the above-described embodiments, the determination may be made based on a value represented by 1 bit (0 or 1), a Boolean (true or false) value, or a numerical comparison (e.g., comparison with a predetermined value).

[0048] (5) The order of the process steps, sequences, flow charts, etc. illustrated in the above-described embodiments may be changed without causing any inconsistency. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0049] (6) Each function illustrated in FIG. 1 is realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by using wires, wirelessly, etc.). The functional block may be realized by combining the one device or the multiple devices with software.

[0050] (7) The programs exemplified in the above-described embodiments should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., regardless of whether software is called software, firmware, middleware, microcode, hardware description language, or by other names.

[0051] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.

[0052] (8) In the above embodiments, the terms "system" and "network" are used interchangeably.

[0053] (9) The information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or corresponding other information.

[0054] (10) In the above-described embodiments, the mobile terminal includes a mobile station (MS). A mobile station may be referred to by those skilled in the art as a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term. In this disclosure, the terms "mobile station", "user terminal", "user equipment (UE)", "terminal", etc. may be used interchangeably.

[0055] (11) In the above-mentioned embodiments, the terms "connected" and "coupled" or any variation thereof refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "accessed". As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and light (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0056] (12) In the above embodiments, the phrase "based on" does not mean "based only on," unless otherwise specified. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0057] (13) As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in a table, database, or other data structure), ascertaining, and the like. Also, "determining" and "determining" may include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), and the like. In addition, "judgment" and "decision" can include considering resolving, selecting, choosing, establishing, comparing, etc., to be a "judgment" or "decision." In other words, "judgment" and "decision" can include considering some action to be a "judgment" or "decision." In addition, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0058] (14) In the above embodiments, when "include," "including," and variations thereof are used, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, the term "or" used in this disclosure is not intended to be an exclusive or.

[0059] (15) In this disclosure, where articles have been added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural.

[0060] (16) In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combined" may also be interpreted in the same way as "different."

[0061] (17) Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the specific information).

[0062] (D: Aspects understood from the above-described embodiments or modifications) Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented as modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. The following aspects can be understood from at least one of the above-mentioned embodiments or modifications.

[0063] A management device according to a first aspect of the present disclosure includes an acquisition unit, a first generation unit, a second generation unit, a storage unit, and a control unit. The acquisition unit acquires a plurality of types of identification information used when a server providing a service to a preregistered user authenticates an accessing user. In the first aspect, the type and number of the plurality of types of identification information used when the server authenticates an accessing user are determined for each service. The first generation unit generates combined information by combining each of the plurality of types of identification information with one or more delimiters in between. In the first aspect, the delimiter is a character different from any of the characters available for each of the plurality of types of identification information in the plurality of services. The second generation unit generates encrypted information by encrypting the combined information generated by the first generation unit. The storage unit stores the encrypted information in association with the user and the service. When the control unit detects that the user has started using the service, the control unit transmits to the server a plurality of types of identification information obtained by decrypting the encrypted information stored in the storage unit in association with the user and the service. The control unit refrains from attempting subsequent user authentication when user authentication using multiple types of identification information obtained by decrypting the encrypted information stored in the storage unit fails N consecutive times. In the first aspect, N is a positive integer equal to or less than M-1, and M is an integer equal to or greater than 2 that is determined for each service in order to reject subsequent authentication attempts if authentication fails M consecutive times. The management device of the first aspect facilitates centralized management of credentials even if the specifications of credentials of multiple financial institutions that transact with a user are different.

[0064] The first generating unit in a second aspect (an example of the first aspect) of the present disclosure attempts to access the server using the multiple types of identification information, and generates the combined information when the access to the server is successful. According to the second aspect, encrypted information is generated based on the identification information that has been successfully accessed.

[0065] In a third aspect (an example of the first aspect) of the present disclosure, the order of each of the multiple types of identification information when the multiple types of identification information are combined with a delimiter in between is determined for each service. According to the third aspect, the type of each of the identification information can be identified based on the order of the multiple types of identification information combined with a delimiter in between.

[0066] In a fourth aspect (an example of the first aspect) of the present disclosure, when the multiple types of identification information include a first type of identification information, a second type of identification information, and a third type of identification information, at least one of the number or type of delimiters placed between the first type of identification information and the second type of identification information when generating the combined information is different from the number or type of delimiters placed between the second type of identification information and the third type of identification information. According to the third aspect, the type of each identification information can be identified based on the type or number of delimiters placed between each of the first type of identification information, the second type of identification information, and the third type of identification information. [Explanation of symbols]

[0067] 10...management device, 130...communication device, 150...storage device, 160...processing device, 160a...acquisition unit, 160b...first generation unit, 160c...second generation unit, 160d...control unit, 190...bus, PR1...program.

Claims

1. an acquisition unit that acquires a plurality of types of identification information used when a server providing a service to a pre-registered user authenticates an access source user; a first generating unit that generates combined information by combining each of the multiple types of identification information acquired by the acquiring unit with one or more delimiters therebetween; a second generating unit that generates encrypted information by encrypting the combined information generated by the first generating unit; a storage unit that stores the encrypted information in association with the user and the service; a control unit that, when detecting that the user has started using the service, transmits to the server a plurality of types of identification information obtained by decrypting encrypted information that is associated with the user and the service and that is stored in the storage unit; The types and number of the multiple types of identification information used by the server to authenticate the accessing user are determined for each service, the delimiter is a character different from any of characters available for each of the plurality of types of identification information in the plurality of types of services, the control unit, when user authentication using a plurality of types of identification information obtained by decrypting the encrypted information stored in the storage unit fails N consecutive times, suspends subsequent attempts of user authentication; N is a positive integer equal to or less than M-1, M is an integer equal to or greater than 2 and is determined for each service in order to reject subsequent authentication attempts if authentication fails M consecutive times. An identification information management device.

2. The first generation unit is The management device according to claim 1 , further comprising: an access attempt unit that attempts to access the server using the plurality of types of identification information; and, if access to the server is successful, generates the combined information.

3. The management device according to claim 1 , wherein an order of the identification information when the plurality of types of identification information are combined with a delimiter therebetween is determined for each service.

4. The management device of claim 1, wherein when the multiple types of identification information include a first type of identification information, a second type of identification information, and a third type of identification information, at least one of the number or type of delimiter characters placed between the first type of identification information and the second type of identification information when generating the combined information is different from the number or type of delimiter characters placed between the second type of identification information and the third type of identification information.

Citation Information

Patent Citations

  • Account aggregation system, information processing apparatus and encryption key management method of the account aggregation system

    JP2011128985A