Method and system for authenticating secure credential transfer to a device - Patents.com
The method authenticates secure credential transfer by verifying user and device identities through a trusted security chip and server, enhancing security and reducing user interaction in device setup.
Patent Information
- Application Number
- JP2023117262
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-07-30
- Filing Date
- 2023-07-19
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2040-07-22
AI Technical Summary
Existing methods for setting up new devices require users to log in with passwords or two-factor authentication, which do not verify the device's security, leading to uncertainty about device safety and user needs.
A method for authenticating secure credential transfer involves user input on a first client device to initiate transfer, verifying user and device identities through a trusted security chip and an authentication server, establishing a secure communication channel using tokens.
This method enhances security by verifying device trustworthiness, reducing user interaction, and ensuring secure credential transfer without manual login, improving user confidence in device safety.
Smart Images

Figure 0007586975000001 
Figure 0007586975000002 
Figure 0007586975000003
Abstract
Description
[Background technology]
[0001] REFERENCE TO RELATED APPLICATIONS This application is a continuation of U.S. Application 16 / 526,384, filed July 30, 2019, the entire disclosure of which is incorporated herein by reference.
[0002] background When setting up a new device, the user must log back into the system by providing a password, using two-factor authentication, or in other ways. This login process may include additional steps, such as accessing a password retrieval system. Prior to logging in, the user cannot fully explore the new device and determine whether the new device meets their needs or whether the new device is a secure device for work or other uses. Summary of the Invention [Means for solving the problem]
[0003] overview Aspects of the present disclosure provide a method for authenticating a secure credential transfer to a device, the method comprising: one or more first processors on a first client device; clientreceiving a user input to initiate a secure credential transfer to the device, the user input triggering sending of information to the second client device; verifying a user identity by the one or more first processors requesting input of a user ID and receiving the input of the user ID; verifying a device identity of the second client device by the one or more second processors of the second client device determining a security status of the second client device from hardware of the second client device, invoking an identifier associated with the security status of the second client device to an authentication server, and receiving from the authentication server a certification for the second client device based on the invoked identifier; receiving one or more tokens associated with the account for performing the secure credential transfer; and after verifying the user identity and the device identity, the one or more first processors and the one or more second processors establishing a secure communication channel between the first client device and the second client device using the one or more tokens.
[0004] In one example, the second client The user input to initiate the secure credential transfer to the device includes a tap entered into an applet installed on the first client device. In another example, the information is transmitted from the first client device to the second client device using near field communication. In this example, the method further includes one or more second processors of the second client device receiving the information and then transmitting the information to the second client device. client The method further includes requesting user confirmation for secure credential transfer to the device.
[0005] In a further example, the input of the user ID is a pre-existing verification of the user identity of the first client device. In yet another example, the secure state of the second client device is determined from a trusted security chip of the second client device. In yet another example, a certificate from the authentication server indicates that the called identifier is associated with a known client device in the authentication server's database.
[0006] In another example, the method further includes the one or more first processors receiving a certificate of the second client device. In a further example, the method further includes the one or more first processors receiving a selection of an account for performing the secure credential transfer. In yet another example, calling an identifier associated with a secure state of the second client device to an authentication server includes using the first client device as a proxy for calling the identifier to the authentication server.
[0007] Another aspect of the present disclosure provides a non-transitory computer-readable medium configured to store instructions executable by one or more processors that, when executed, cause the one or more processors to perform a method, the method comprising: a first client device transmitting a second clientreceiving a user input to initiate a secure credential transfer to the device, the user input triggering sending of information to the second client device; the first client device verifying the user identification information by requesting input of a user ID and the one or more first processors receiving the input of the user ID; the second client device verifying a device identification information of the second client device by determining a safety state of the second client device from hardware of the second client device, calling an identifier associated with the safety state of the second client device to an authentication server, and receiving from the authentication server a certificate for the second client device based on the called identifier; receiving from the authentication server one or more tokens associated with an account for performing the secure credential transfer; and establishing a secure communication channel between the first client device and the second client device for performing the secure credential transfer after verifying the user identification information and the device identification information.
[0008] In one example, the second client The user input to initiate the secure credential transfer to the device includes a tap entered into an applet installed on the first client device. In another example, the information is transmitted from the first client device to the second client device using near field communications. In a further example, the secure state of the second client device is determined from a trusted security chip of the second client device. In yet another example, a certificate from an authentication server indicates that the invoked identifier is associated with a known client device in the authentication server's database.
[0009] In a further example, the method further includes the first client device receiving a certificate of the second client device. In another example, the method further includes the first client device receiving a selection of an account for the secure credential transfer. In a further example, calling an identifier associated with the secure state of the second client device to an authentication server includes using the first client device as a proxy for calling the identifier to the authentication server.
[0010] A further aspect of the present disclosure provides a system comprising a memory for storing a database including device identities of a plurality of devices whose secure state has already been validated, and one or more processors in communication with the memory, the one or more processors configured to receive from a first computing device information related to initiating a secure credential transfer and receive from a second computing device a validation request including challenge information, the validation request including information related to validating the user identity, a first identifier from the previous challenge information, and a signature obtained from the second computing device including a second identifier related to the secure state of the second computing device, the one or more processors configured to perform a validation of the validation request, the validation of the validation request including verifying that the information related to validating the user identity is from the first computing device, verifying that the first identifier matches the second identifier, and verifying that the second identifier matches a device in a database containing device identification information, wherein the one or more processors are configured to provide one or more tokens to the first computing device and the second computing device to establish a secure communication channel for secure credential transfer to the second computing device.
[0011] In one example, the one or more processors are configured to provide the one or more tokens by providing a first token to a second computing device including a validation request certificate, receiving a selection of a user account from the first computing device, providing a second token for the user account to the first computing device, receiving a signed second token from the second computing device, and providing a third token to the second computing device for establishing a secure communications channel for secure credential transfer. [Brief description of the drawings]
[0012] [Figure 1] FIG. 1 is a functional diagram illustrating an example system 100 according to an embodiment of the present disclosure. [Diagram 2] FIG. 1 is a schematic diagram illustrating an exemplary system 100 according to an embodiment of the present disclosure. [Diagram 3] 3 is a flow diagram 300 illustrating an exemplary method according to an embodiment of the present disclosure. [Figure 4] 4 is a detailed diagram 400 illustrating an exemplary method according to an embodiment of the present disclosure. [Diagram 5] 5 is a flow diagram 500 illustrating an exemplary method according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] Detailed Description overview The disclosed technology relates to a method and system for authenticating secure credential transfer to a device. When a user uses a new or loaned device, credentials are typically required to transfer the user profile and other settings to the device. Typically, some combination of passwords, two-factor authentication, and other verification methods are performed. However, one problem with these methods is that they typically do not include a means to verify that the device is a secure device. The methods and systems described herein provide a series of steps that can verify the user and the device prior to the transfer of credentials. Additionally, the methods and systems described herein require less user interaction than other authentication methods and systems, thus providing a simpler process for the user. Additionally, the methods described herein can improve the security of the user profile and other settings by reducing the need to manually enter credentials into a new or loaned device and / or by allowing temporary transfer / authentication of credentials.
[0014] The authentication system includes a first client device, a second client device, and an authentication server. A user may have a user profile accessible on or from the first client device. The user profile may include device settings, application downloads, application settings, or account settings. The second client device may be any device that does not store or access a user profile from the device. The authentication server may have a database that includes device identities of multiple devices whose security is known or has already been verified.
[0015] To initiate a secure credential transfer of a user profile, the first client device may receive a user input, and then the second client device may confirm the transfer from the first client device to the second client device. In response to the confirmation, the second client device may The first client device may transmit an identifier of the second client device to the first client device. The identifier may be obtained from the hardware of the second client device and may include a secure state indicating that the second client device is a trusted forwarding device. After receiving a user confirmation from the second client device, the first client device may perform a user identity verification to further verify the request for secure credential forwarding to the second client device. Also, the first client device may perform a device identity verification of the second client device by transmitting and verifying a signature of the second client device to the authentication server. If the second client device is verified, the authentication server may provide the second client device's certificate and a forwarding token to the second client device. The second client device may transmit the certificate and the forwarding token to the first client device, and the first client device may perform an additional check of the second client device's certificate.
[0016] The first client device receives user input to select an account, e.g., a user profile and a validity time, for the secure credential transfer. The first client device can then request a temporary token for the selected account from the authentication server. The authentication server then sends the temporary token to the first client device, which in turn sends the temporary token to the second client device. The second client device can sign the temporary token and send the signed temporary token to the authentication server to verify the channel between the first and second client devices. Once the information associated with the signed temporary token is verified, the authentication server provides the second client device with a regular session token that includes an expiration time for the requested secure credential transfer. The regular session token is then used to The method performs a secure credential transfer of a user profile from a first client device to a second client device, i.e., the second client device is authenticated by the first client device and can access the user profile during the validity period.
[0017] The above features have the technical effect of providing a more secure method for granting access to user credentials on a client device. The method has the technical effect of requiring less user input by authenticating a second client device with a client device that is already trusted by the user, and can improve security by eliminating the need to manually enter user credentials on an unknown device. This authentication method does not require user input of login information and additional user verification, but rather a user request for transfer and authentication of a specific account from a trusted device. The method also provides a method for authenticating a second client device with an authentication server. client To verify the device as a trusted device, the user may provide user credentials to a second client The method provides a higher degree of confidence in the security of transferring or utilizing user credentials to the client device, and the method can further improve security by cross-verifying the identities of both the first client device and the second client device prior to transferring the user credentials.
[0018] Exemplary System 1 and 2 illustrate an exemplary system 100 in which the features described herein can be implemented. The exemplary system may be a system for authenticating client computing devices. In this example, the system 100 may include multiple computing devices 110, 120, 130 and a storage system 150 connected via a network 160. The computing device 110 may be a server computing device acting as an authentication server. The computing devices 120 and 130 may be client computing devices.
[0019] As shown in FIG. 1, the authentication server 110 includes one or more processors 112, memory 114, instructions 116, and data 118. The one or more processors 112 may be any conventional processor, such as a commercially available CPU. Alternatively, the one or more processors may be a dedicated processor, such as an ASIC or other hardware-based processor. Although FIG. 1 functionally depicts the processor, memory, and other elements of the computing device 110 as being located in the same block, one skilled in the art will appreciate that a processor, computing device, or memory may actually include multiple processors, multiple computing devices, or multiple memories located or stored in the same or different physical housings. In one example, the one or more computing devices 110 may include one or more server computing devices, which may include multiple computing devices, e.g., load-balanced server farms, that exchange information over different nodes of a network to receive, process, and transmit data to and from other computing devices.
[0020] The memory 114 stores information accessible by one or more processors 112, such as instructions 116 and data 118 that may be executed or used by the processors 112. The memory 114 may be any type of medium capable of storing information accessible by the processor, such as a computing device readable medium or other medium that stores data that may be read via an electronic device, such as a hard drive, memory card, ROM, RAM, DVD, other optical disks, other writable memory and read-only memory. The systems and methods may include different combinations of the foregoing. Thus, different portions of the instructions and data may be stored on different types of media. In particular, the memory 114 may be configured to store a database that includes device identification information for a plurality of computing devices.
[0021] The instructions 116 may be any instructions executed directly by a processor (e.g., machine code) or indirectly (e.g., script). For example, the instructions may be stored on a computing device readable medium as computing device code. In this case, the terms "instructions" and "program" may be used interchangeably herein. The instructions may be stored in an object code format that the processor can process directly, or in any other computing device language, including a script or a collection of independent source code modules that are interpreted on demand or precompiled. The processes, functions, methods, and routines of the instructions are described in more detail below. The instructions 116 may also include compiling and updating a database that includes device identification information for devices that are known to be secure or have been verified to be secure.
[0022] The processor 112 may obtain, store, or modify the data 118 according to the instructions 116. As an example, the data 118 stored in the memory 114 may be a database including device identification information for a plurality of computing devices. The data 118 may also include data for supporting services for one or more client computing devices, e.g., client computing devices 120, 130. This data may include data for supporting web-based application hosting, file sharing services, communication services, gaming services, video or audio file sharing services, or any other network-based service.
[0023] Each of the client computing devices 120 and 130 is configured similarly to the authentication server 110 described above to include one or more processors, memory, instructions, and data. Each client computing device 120, 130 may be a personal computing device used by a user. As shown in FIG. 2, both client computing devices 120 and 130 may be used by a single user 220. In some alternatives, the authentication server 110 may be part of the client computing device 120 or 130, rather than being separate from the client computing device 120 or 130.
[0024] Each client computing device 120, 130 also includes all of the components typically used in connection with a personal computing device, such as one or more processors (e.g., a central processing unit (CPU)), memory (e.g., RAM and an internal hard drive) for storing data and instructions, a display such as display 122, 132 (e.g., a monitor having a screen, a touch screen, a projector, a television, or other device operable to display information), speakers, and user input devices 124, 134 (e.g., a mouse, keyboard, touch screen, camera, or microphone). The one or more processors of each client computing device may be the same as or similar to the one or more processors 112. The memory of each client computing device for storing instructions and data may be the same as or similar to the memory 114 for storing instructions 116 and data 118. Each client computing device may also include one or more components that enable Near Field Communication (NFC) functionality.
[0025] Each client computing device 120, 130 may be a full-sized personal computing device, or alternatively, a mobile computing device capable of wirelessly exchanging data with a server computing device (e.g., server computing device 110) over a network such as the Internet. As one example, client computing device 120 may be a mobile phone, a wireless-enabled PDA, a tablet PC, a wearable computing device or system, or a netbook capable of obtaining information over the Internet or other network. As another example, client computing device 120 may be a wearable computing system, such as a smart watch.
[0026] A user profile for a user, e.g., user 220, is on or accessible on the client computing device 120. The user profile may include device settings, application downloads, application settings, and / or account settings. The client computing device 130 may have a user profile stored on it or may not have a user profile accessible from it. For example, the client computing device 130 may be a newly purchased or loaned laptop, or may be a laptop on display in a retail environment.
[0027] Storage system 150, like memory 114, may be any type of computer storage medium capable of storing information accessible by server computing device 110, such as hard drives, memory cards, ROM, RAM, DVDs, CD-ROMs, writeable memory, and read-only memory. Storage system 150 may also include a distributed storage system configured to store data on multiple different storage devices that are physically located in the same or different locations. Storage system 150 may be connected to the computing devices via network 160, as shown, and / or may be directly connected to or incorporated into any of computing devices 110, 120, 130. Storage system 150 may have any of the features described herein. To implement some or all of the features, various information may be stored in one or more server computing devices, such as authentication server 110, and / or one or more client computing devices, such as client computing devices 120 or 130, that can be obtained or accessed by the one or more server computing devices, such as authentication server 110, or one or more client computing devices, such as client computing devices 120 or 130.
[0028] 1 functionally depicts the processor, memory, and other elements of a computing device as being located in the same block, a processor, computer, computing device, or memory may actually include multiple processors, multiple computing devices, or multiple memories located or contained in the same or different physical housings. For example, memory 114 may be a hard drive or other storage medium located in a housing different from that of computing device 110.
[0029] A processor, computer, computing device, or memory described herein may be understood to include a set of processors, computers, computing devices, or memories that can operate in parallel or serially. For example, computing device 110 may include a server computing device operating, for example, as a load-balanced server farm or distributed system. Additionally, although some functionality described below is shown as being implemented on a single computing device including a single processor, various aspects of the subject matter described herein may be implemented by multiple computing devices that communicate information, for example, via network 160.
[0030] The network 160 and intermediate nodes can include a variety of configurations and protocols, such as short-range communication protocols such as Bluetooth® and Bluetooth® LE, the Internet, the World Wide Web, intranets, virtual private networks, wide area networks, local networks, private networks using one or more company proprietary communication protocols, Ethernet, WiFi®, HTTP, and various combinations thereof. Any device capable of sending and receiving data to and from other computing devices, such as modems and wireless interfaces, can facilitate such communications.
[0031] Exemplary Methods In addition to the operations described above and illustrated in the figures, various operations are described below. The following operations need not be performed in the exact order described below. Rather, various operations may be performed in a different order or simultaneously, and operations may be added or omitted. For example, FIG. 3 illustrates a flow diagram 300 according to an embodiment of the present disclosure. More specifically, FIG. 3 illustrates an exemplary method flow for authenticating a secure credential transfer from a client computing device 120 (hereinafter referred to as a "first client device") to a client computing device 130 (hereinafter referred to as a "second client device") using an authentication server 110. The first client device 120 and the second client device 130 may be NFC-enabled devices. FIG. 4 also illustrates a functional diagram 400 illustrating additional details of the method illustrated in FIG. 3, such as the communication between the first client device 120, the second client device 130, and the authentication server 110.
[0032] In block 302, the first client device 120 and the second client device 130 may receive user input to initiate a secure credential transfer of a user profile. For example, as shown in FIG. 4, in step 402, the first client device 120 may receive user input to initiate a process for authenticating the second client device 130. The user input may be The user input device 124 of the device may be a tap received using an applet installed on the first client device or a browser opened on the first client device. It should be understood that alternatively, other types of user input may be used. In some cases, the user input may represent an account for performing the secure credential transfer. In step 404a, the user input may trigger the transmission of first information from the first client device to the authentication server. The first information may include information related to the first client device, information related to initiating the secure credential transfer, and / or information related to an account for performing the transfer. Also, in step 404b, the user input may trigger the transmission of second information using NFC or another short-range communication protocol. The second information may include instructions for initiating the secure credential transfer on the second client device. The second client device may detect the information from the first client device and present a prompt to the user to confirm the transfer on the second client device in step 406a. The prompt may include opening a browser (or other application) on the second client device and requesting user input via the browser. In step 406b, the second client device may receive user confirmation using a user input device on the second client device.
[0033] At block 304, the second client device may transmit an identifier of the second client device to the first client device in response to the user confirmation. As shown in step 408 of FIG. 4, the identifier may be obtained from the hardware of the second client device, such as a trusted security chip. The identifier may also include a secure state, which may also be obtained from the hardware of the second client device. In particular, the secure state of the second client device may indicate that the second client device is prepared for secure credential transfer. For example, the secure state may indicate that the second client device is in a "verified boot mode." The secure state of the verified boot mode may indicate that the platform firmware and / or operating system of the second client device have been authenticated as being from a known, trusted source. In one example, the secure state of the verified boot mode may indicate that all code executed on the second client device has been authenticated as being from a known, trusted source tree. As shown in step 410, once the identifier of the second client device has been obtained, it may be transmitted to the first client device 120, for example, via NFC.
[0034] In block 306, the first client device performs a user identity verification to confirm the request for secure credential transfer to the second client device. As shown in step 412 of FIG. 4, the second client device can request a user identity verification after receiving the user confirmation. The second client device can send the user identity verification request as challenge information, for example, using NFC or another short-range communication protocol. In step 414, the first client device can present a prompt to input a user identity in response to receiving the verification request. The prompt may be presented on the display 122 of the first client device. This has the technical advantage of facilitating a two-way verification process and improving the credential transfer security. The input of the user identity may be an existing verification process on the first client device. For example, a user ID, for example, a password, fingerprint authentication, face recognition, which unlocks the first client device, can be input. As shown in step 416, once the user ID is input and verified by the first client device, the user identity verification is completed. If desired, verification of user identity may occur at a later stage, for example when selecting an account for making the transfer, in block 312 below.
[0035] In block 308, the identifier of the second client device may be used to perform verification of the device identity of the second client device. After the first client device completes the verification of the user identity, the first client device may start to verify the device identity of the second client device. As shown in step 418 of FIG. 4, the first client device may send challenge information including at least the identifier of the second client device to the second client device. In some implementations, the challenge information may be composite challenge information indicating an association between the current challenge information and the previous challenge information. The association may be an association between the challenge information for verifying the current device identity and the challenge information for verifying the user identity performed in block 306. Thus, the composite challenge information may include the identifier of the second client device and information related to the verification of the user identity.
[0036] In response to receiving the challenge information for verifying the device identity, the second client device can insert a signature including an identifier associated with the security state of the second client device. As described above, the security state of the second client device can be obtained from the hardware of the second client device, for example, a trusted security chip. In step 420, the signature including the identifier is sent to the authentication server together with a validation request. In some implementations where the authentication server is part of the second client device 130, the validation request may be sent to the authentication server together with the signature including the identifier by invoking or referencing the signature including the identifier.
[0037] In step 422, after receiving the validation request, the authentication server verifies the second client device as a secure device using the identifier and a database containing device identification information. As described above, the database containing device identification information may be stored in the memory 114 of the authentication server 110 or in a storage system 150 accessible by one or more processors 112 of the authentication server. The database containing device identification information may contain identifiers of known secure devices. If the identifier in the signature matches an identifier of a device in the database, the second client device is verified as a secure device. This verification may also include verifying that the identifier in the challenge information matches the identifier in the signature to ensure that a validation of a given client device has been performed. This verification may also include verifying that the information related to the verification of the user identification information is from the first client device.
[0038] Then, in step 424, the authentication server sends a response to the second client device with a transfer token for verification (certificate) confirmation and secure credential transfer. The certificate may be a signature including the authentication server's identifier further inserted in the challenge information. Then, in step 426, the second client device can send the transfer token to the first client device with the challenge information updated with the certificate.
[0039] In step 428, the first client device may optionally perform additional checks of the second client device's certificate based on the updated challenge information. The additional checks may include (i) verifying that the signature of the second client device matches the signature in the certificate, and (ii) verifying that the authentication server's signature includes the identifier of a known authentication server. By performing additional authentication, the security and integrity of the process of verifying device identity may be further improved.
[0040] In block 310, the first client device receives user input to select an account for the secure credential transfer (if an account has not already been selected). The selected account may be a user profile on the first client device. In step 430 of FIG. 4, the first client device may present a prompt for user input regarding the selection of an account after receiving the transfer token and / or after performing additional checks of the certificate. The prompt may be presented on the display 122 of the first client device. Thus, the security of the credential transfer process may be improved since no information indicative of the user's account is provided to the second client device until confirmation is received that the second client device is trusted and prepared to perform a secure credential transfer. The user input may be received in step 432 and may include a request regarding the expiration of the account's official session token. The expiration may be between 15 and 45 minutes, for example 30 minutes. This may facilitate a temporary authentication of the user account or profile and associated settings. This temporary authentication may improve user security by preventing access by a third party at a later time. If necessary, a verification of the user identity may be performed before or after the account is selected.
[0041] In block 312, a secure communication channel is established between the first client device and the second client device using one or more tokens generated by the authentication server. In step 434 of FIG. 4, the first client device may request a temporary token for the selected account from the authentication server. In response, the authentication server may send the temporary token to the first client device in step 436 and, if necessary, record the expiration date of the requested formal session token. The temporary token may be valid for a relatively short time, for example, between 10 and 30 seconds. The expiration date of the temporary token may be long enough to establish a secure communication channel. In step 438, the first client device sends the temporary token to the second client device using NFC, and the second client device signs the temporary token. For example, the second client device may sign the temporary token using an identifier obtained from the security chip. In step 440, the second client device sends the signed temporary token and the transfer token to the authentication server to verify the communication channel between the first client device and the second client device. If the signature / identifier, temporary token, and transfer token all match those stored in the authentication server, the authentication server verifies the communication channel in step 442. The authentication server then sends the second client device a valid session token, including an expiration time for the requested secure credential transfer, in step 444.
[0042] In block 314, a secure credential transfer of the user profile is performed from the first client device to the second client device using the formal session token. In step 446 of FIG. 4, the second client device sends the formal session token to the first client device. The first client device then authenticates the second client device as a trusted device for the requested expiration time using NFC in step 448. The second client device is allowed to access the user profile through an application such as a browser for the expiration time. Alternatively, the first client sends the user profile to the second client device after receiving the formal session token. In some other examples, another period may be used instead of the expiration time when the user does not specify an expiration time. This period may be a preset period or may be defined as a period during which the first client device is located in the vicinity of the second client device.
[0043] In some alternatives, a Trusted Platform Module (TPM), security-related instruction code embedded in the central processing unit, or a Trusted Execution Environment (TEE) solution may be used to authenticate the second client instead of the trusted security chip. The state of the device or a signed identifier may be provided.
[0044] In another example, if the second client device does not have a network connection that allows it to access the authentication server, the first client device can utilize the first client device as an Internet gateway to communicate with the authentication server. To this end, the first client device can act as a proxy by providing a temporary wireless connection to the second client device and sending / receiving to / from the authentication server on behalf of the second client device or by other known means.
[0045] 5 is a flow diagram 500 according to an aspect of the disclosure. More specifically, FIG. 5 illustrates a flow of an example method performed by one or more processors 112 of the authentication server 110 for authenticating a secure credential transfer from a first client device 120 to a second client device 130.
[0046] At block 502, the one or more processors 112 may receive information related to initiating a secure credential transfer from a first computing device. As described above in connection with steps 402 and 404a, the transmission of the information may be triggered based on user input received at the first computing device, such as a tap entered into an applet open on the first computing device.
[0047] At block 504, a validation request may be received from the second computing device. The validation request may include challenge information, which may include information related to the verification of the user identity, a first identifier from the previous challenge information, and a signature obtained from the second computing device including a second identifier related to the secure state of the second computing device. The information related to the verification of the user identity may be obtained as described above in connection with steps 412-416. The first identifier may be obtained as described above in connection with steps 408, 410, and 418.
[0048] At block 506, the one or more processors 112 may verify the validation request. As shown at block 506 and further described in connection with step 422 above, the verification may include (i) verifying that the information related to verifying the user identity is from the first computing device, (ii) verifying that the first identifier matches the second identifier, and (iii) verifying that the second identifier matches a device in a database that includes device identification information.
[0049] At block 508, the one or more processors 112 may transmit one or more tokens to the first computing device and the second computing device to establish a secure communication channel for secure credential transfer to the second computing device. Specifically, the one or more processors 112 may generate a first token and transmit it to the second computing device together with the validation request certificate. As described above in relation to steps 424 and 426, the first token may be a transfer token. Also, the one or more processors 112 may generate and transmit a second token of the selected user account to the first computing device. As described above in relation to steps 434 and 436, the second token may be a temporary token requested by the first client device after receiving a user input indicating a selection of the user account. Furthermore, the one or more processors 112 may generate and transmit a third token to the second computing device to establish a secure communication channel for secure credential transfer. As described above in connection with steps 442 and 444, the third token may be generated and transmitted after verifying the communication channel based on the signed temporary token and the forward token.
[0050] The above features provide a more secure method for granting access to user credentials on a client device. This method requires less user input by authenticating the second client device with a client device that is already trusted by the user, thus improving security by eliminating the need to manually enter user credentials on an unknown device. This authentication method does not require user input of login information and additional user verification, but rather a user request for transfer and authentication of a specific account from a trusted device. This method also does not require authentication using an authentication server to authenticate the second client device. client To verify the device as a trusted device, the user may provide user credentials to a second clientThe method provides a higher degree of confidence in the security of transferring or utilizing user credentials to the client device, and the method can further improve security by cross-verifying the identities of both the first client device and the second client device prior to transferring the user credentials.
[0051] Unless otherwise stated, the aforementioned alternatives are not mutually exclusive and may be implemented in various combinations to achieve certain advantages. Various variations and combinations of the above-described features may be utilized without departing from the subject matter defined by the claims. The above description of the embodiments is illustrative and does not limit the subject matter defined by the claims. In addition, the examples described herein and expressions such as "for example," "including," and the like should not be construed as limiting the claims to a particular example. Rather, the example is intended to illustrate only one of many possible embodiments. Moreover, in different drawings, the same reference numbers indicate the same or similar elements.
[0052] The systems described herein provide the user with one or more opportunities to control whether a program or feature collects user information (e.g., passwords, information about the user's social networks, user characteristics (e.g., age, gender, and occupation), social behavior or activities, user preferences, content created or submitted by the user, information about the user's current geographic location) when collecting personal information or when using personal information. Certain data may also be processed in one or more ways to remove personally identifiable information before it is stored or used. For example, a user's ID may be processed so that the user's personally identifiable information cannot be determined, or the user's geographic location, if location information is available (e.g., to the city, zip code, or state level), may be generalized so that the user's location cannot be determined. Thus, the user can control what user information is collected, what use of the information is made of, and what information is provided to the user.
Claims
1. receiving, by one or more processors of the first client device, an input from a user to initiate a process of authenticating the second client device; sending instructions to the second client device, in response to receiving the user input, to initiate a secure credential transfer on the second client device; receiving, by the one or more processors, from the second client device, an identifier of the second client device transmitted in response to the transmitted instructions; the one or more processors verifying the identity of the user; the one or more processors verifying an identity of the second client device according to the received identifier; and initiating a session during a preset period of time that grants the second client device access to a user account or user profile in response to the one or more processors verifying the identity of the user and the identity of the second client device.
2. The method of claim 1 , wherein the user input provides information indicative of the user account for which the secure credential transfer is to occur.
3. 3. The method of claim 2, further comprising: the one or more processors, in response to receiving the user input, transmitting information relating to at least one of the first client device, the user account, or the user profile to an authentication server for performing the secure credential transfer.
4. transmitting challenge information to the second client device in response to verifying the identity of the user; The method of claim 3 , further comprising: the one or more processors receiving, in response to the challenge information, a transfer token for effecting the secure credential transfer.
5. The one or more processors, in response to receiving the transfer token, display a prompt on a display of the first client device regarding a selection of the user account. Presenting to a user; The method of claim 4 , further comprising: the one or more processors, in response to the prompt, receiving input from the user including a selected account.
6. The method of claim 5 , further comprising the one or more processors sending a request to the authentication server to request a temporary token for the selected account.
7. The method of claim 6 , further comprising the one or more processors receiving the temporary token in response to the transmitted request.
8. The method of claim 7 , further comprising the one or more processors, in response to receiving the temporary token, transmitting the temporary token to the second client device.
9. The method of claim 8 , further comprising the one or more processors receiving a formal session token from the second client device in response to transmitting the temporary token.
10. 10. The method of claim 9, further comprising granting the second client device access to the selected account in response to receiving the valid session token.
11. 1. A method comprising: one or more processors of a first client device receive, from a second client device, first information including instructions for initiating a secure credential transfer on the first client device, the second client device being associated with a user account or user profile; generating, on the first client device, a prompt for user confirmation of the secure credential transfer in response to receiving the first information; the one or more processors, in response to receiving the user confirmation, sending (i) an identifier of the first client device and (ii) a user identity verification request to the second client device; and generating a response to the received validation challenge, the response including a signature including an identifier associated with a secure state of the first client device. the one or more processors sending the generated response to an authentication server; and obtaining, from the authentication server, one or more tokens for effecting the secure credential transfer; and initiating a session with the second client device using the obtained one or more tokens, the session being public for a preset period of time; and the one or more processors accessing the user account or the user profile at the preset time period.
12. The method of claim 11 , wherein the obtained one or more tokens further include a transfer token.
13. The method of claim 12 , further comprising the one or more processors transmitting the forwarding token to the second client device.
14. The method of claim 11 , further comprising the one or more processors receiving a temporary token from the second client device.
15. The one or more tokens obtained further include a transfer token; the one or more processors signing the temporary token with an identifier from a security component; 15. The method of claim 14, further comprising the one or more processors sending the signed temporary token and the forwarded token to the authentication server to verify a channel between the first client device and the second client device.
16. The method of claim 15 , wherein the obtained one or more tokens further include an official session token.
17. 17. The method of claim 16, further comprising the one or more processors receiving the formal session token from the authentication server in response to the signed and transmitted temporary token.
18. 20. The method of claim 17, further comprising the one or more processors transmitting the formal session token to the second client device.
19. 20. The method of claim 18, further comprising the one or more processors receiving, in response to the transmitted formal session token, from the second client device, authorization to access the user account or the user profile.
20. 20. The method of claim 18, further comprising the one or more processors receiving the user profile from the second client device in response to the transmitted formal session token.
Citation Information
Patent Citations
Methods, systems, and mobile devices that can enable credit card personalization using wireless networks
JP2008537370A
Terminal authentication method and terminal authentication system in network
JP2014238664A
Issuer trusted party system
US20130073463A1
