Use of device-bound credentials for enhanced authentication security in native applications
By using device-bound credentials to sign refresh tokens, the OAuth system verifies that tokens are used on the original device, addressing the challenge of unauthorized token presentation and enhancing security.
Patent Information
- Application Number
- JP2024526490
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-11-10
- Filing Date
- 2022-09-15
- Publication Date
- 2024-11-21
- Estimated Expiration
- 2042-09-15
AI Technical Summary
Existing OAuth systems lack the ability to verify that refresh tokens are being presented from the same device to which they were originally issued, making it difficult to ensure the authenticity and security of token usage.
Implementing device-bound credentials using public key infrastructure (PKI) and Fast Identity Online (FIDO) to sign refresh tokens, ensuring that the refresh token flow can only occur on the device where the initial grant was established, thereby verifying the device's authenticity.
This approach enhances the security of OAuth systems by ensuring that refresh tokens are used only on the intended device, preventing unauthorized access and improving the integrity of token-based authentication processes.
Smart Images

Figure 2024543338000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to protecting computer resources. More particularly, one or more embodiments of the present invention provide secure access to certain computer resources. Even more particularly, one or more embodiments of the present invention provide a novel and useful solution for ensuring that refresh tokens presented by native applications during Open Authorization (OAuth) refreshes are sent from the same device to which those refresh tokens were issued. Summary of the Invention
[0002] In one or more embodiments of the invention, an authorization server receives from a native application on the device an initial authorization grant, a public key of a private / public key pair generated on the device, and a certificate of authenticity of the native application. The authorization server receives from the native application on the device a refresh token and a digital signature of the refresh token created using the private key, and the authorization server recognizes the refresh token only if the refresh token is verified using the pre-registered public key. The authorization server validates the digital signature of the refresh token. In response to validating the refresh token from the native application on the device, the authorization server sends a new access token and a new refresh token to the native application on the device such that the new access token enables the native application on the device to access computer resources.
[0003] In one or more embodiments, the methods described herein are performed by execution of a computer program product on a computer system. [Brief description of the drawings]
[0004] [Figure 1] FIG. 1 illustrates an example system and network in which the present disclosure may be implemented. [Diagram 2] FIG. 1 illustrates an overview of one or more embodiments of the present invention implemented within an Open Authorization (OAuth) system. [Diagram 3] FIG. 2 is an overview flowchart of one or more operations performed in one or more embodiments of the present invention. [Figure 4] FIG. 1 illustrates an exemplary blockchain network that may be utilized in one or more embodiments of the present invention. [Diagram 5] FIG. 1 illustrates an exemplary blockchain ledger as may be used in one or more embodiments of the present invention. [Figure 6] FIG. 1 illustrates a high-level sequence of operations for using a blockchain in accordance with one or more embodiments of the present invention. [Figure 7] FIG. 1 illustrates an exemplary neural network as may be used in one or more embodiments of the present invention. [Figure 8] FIG. 1 illustrates a cloud computing environment in accordance with an embodiment of the present invention. [Figure 9] FIG. 2 illustrates an abstract model layer of a cloud computing environment in accordance with an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0005] As described herein, one or more embodiments of the present invention utilize device-bound Public Key Infrastructure (PKI) credentials to sign Open Authorization (OAuth) refresh tokens in the refresh token message payload, such that in one or more embodiments of the present invention, public key registration of a credential pair is performed during establishment of the initial grant, and provides for the addition of a signature on the refresh token during all subsequent refresh token flows.
[0006] One or more embodiments of the present invention leverage patterns such as Fast Identity Online (FIDO) to establish a device-bound key pair, including a certificate for such key pair, and do not require anything other than an application-level payload (i.e., no Transport Layer Security (TLS) extensions are required).
[0007] In one or more embodiments of the invention where an OAuth system is utilized, a FIDO assertion payload is added to the refresh token's payload parameters and validated by the server, using the refresh token itself as a challenge to ensure that the signing is performed with a key that was previously registered in a device-bound manner.
[0008] Such OAuth systems provide an identity security pattern for native applications, such that after a user installs the application, they participate in a registration ceremony, establish long-lived OAuth grants (first refresh and access tokens), and allow the application to act as its user when invoking Application Programming Interfaces (APIs) to computer resources such as data, programs, and hardware.
[0009] An exemplary OAuth registration process for a user begins with the user entering a user profile (e.g., name, address, etc.) for initial identification information. In one or more registration scenarios, multi-factor authentication (MFA) is used, in which the user provides not only a password, but also biometric information (e.g., the user's fingerprint), the user's current location as determined by a Global Positioning System (GPS) sensor in an electronic device used by the user, a current communication connection to a particular cell tower in a cellular network, etc., and access to a security token, such as a dongle that generates a constantly changing character that is known by the security system to be valid at the current time.
[0010] After the user enters their user profile, MFA credentials, etc., this information is exchanged for an initial OAuth grant from the authorization server.
[0011] The native application may launch the system browser on the device and the user may authenticate via a browser-based mechanism to initiate an Authorization Code grant type flow, or the native application may provide this functionality for the initial OAuth grant built into the application itself. The native application honors any redirect Uniform Resource Identifiers (URIs) that are the app's registered custom launch URI.
[0012] The user authenticates in a browser on another device (e.g., on a laptop) and is presented with a Quick Response (QR) code that contains an authorization code, allowing the native application to scan the QR code.
[0013] Regardless of the particular flow (either the flow described above or a similar variation), an initial grant is established for the application on the device, and then the refresh token is stored in secure storage specific to the app to prevent disclosure to other apps.
[0014] After registration, whenever a native application on the device (e.g. a mobile device such as a smartphone) needs a new access token to make an API call, the refresh token flow is executed by the native application making a call to the authorization server's token endpoint. The refresh token itself alone serves to identify the grant that is being refreshed.
[0015] A problem with the OAuth process just described, which one or more embodiments of the present invention overcome in a new and useful way, is that there is no proof that the refresh token is presented from the device to which the refresh token was originally issued, so that without the present invention, the authentication server cannot determine / distinguish between situations where the refresh token has been compromised from the device, native application, or network, or any combination thereof, as the refresh token is presented from a different device or program.
[0016] To address this issue, one or more embodiments of the present invention have the native application sign the refresh token using asymmetric device-bound credentials that the application creates during the registration phase every time the refresh token flow is performed. By ensuring that the signing operation can only occur on the device on which the grant was originally established, the server can have a very high level of trust that the OAuth grant is being used by the application on the device for which the grant was issued.
[0017] One or more embodiments of the present invention provide a distinct improvement over token binding. Token binding uses cryptographic certificates, but requires the use of Transport Layer Security (TLS) extensions to obtain cryptographic certificates at both ends of the TLS connection (e.g., between the client and the authorization server). As such, user equipment in such systems requires a high level of expertise, time, and computer resources that the present invention does not require. Furthermore, token binding does not enforce that credentials created at the client are bound to the device, thus making the credentials less secure. As such, one or more embodiments of the present invention provide a solution for resource security that is at the application data level (e.g., using additional parameters in the OAuth payload) and does not depend on the implementation of token binding in TLS.
[0018] From an overview, one or more embodiments of the present invention include two stages: a registration stage and a subsequent grant refresh stage.
[0019] Registration stage
[0020] During registration, the native application receives or collects "initial grant data" from the user. In one or more embodiments of the invention, this initial grant data is Resource Owner Password Credentials (ROPC) user credentials, such as a username / password provided to the native application via a user interface on the client device.
[0021] In one or more embodiments of the invention, this initial grant data is an authorization code obtained from a handoff from a system browser (custom launch URI invocation) or scanned via a QR code.
[0022] Before the native application sends this initial grant data to the token endpoint to obtain the first authorization grant, the native application creates a public / private key credential that is bound to the local device.
[0023] In one or more embodiments of the invention, the device's operating system provides a Fast Identity Online-2 (FIDO2) platform authenticator application program interface (API) that is used to create credentials.
[0024] In one or more embodiments of the invention, a platform API (e.g., a secure enclave API) creates the credentials.
[0025] The credentials created may or may not require a user verification to be created and used. This choice ultimately becomes a security requirement (policy) of the API services the enterprise offers and the desired user experience. In Fast Identity Online (FIDO) terminology and standards, user verification is optional and thus remains an idea described herein.
[0026] After creating the key pair, the native application constructs a FIDO attestationObject that is included in the initial grant data in a request to the OAuth token endpoint in the authentication server. In one or more embodiments of the invention, a packed attestation format is used so that the clientDataJSON input to the creation of this attestation object is the initial grant data (instead of a challenge provided by the server).
[0027] In one or more embodiments of the invention, the certificate private key is embedded in the native application source itself, and protection of the certificate private key is performed using techniques such as white-box cryptography and secure native code distribution practices.
[0028] One or more embodiments of the present invention utilize a certificate protocol, such as FIDO2 certificates.
[0029] Certificates such as FIDO2 certificates provide the authentication server with proof of the make / model of the client authenticator used. In the case of a native application acting as a client authenticator, this proof is to attest to the integrity of the application by identifying the vendor and version of the native application as specified by the application developer so that the application can be trusted to be doing what it was coded to do.
[0030] In one or more embodiments of the invention, the authentication server must be able to attest that the credentials being created used to sign the refresh token flow are bound to the device such that the private key will only be used on the device for which it was established. Without such attestation, the server cannot know that the client communicating with the server is a genuine installation of the application. If the application uses native FIDO2 APIs provided by the client device's operating system, the attestation will be provided by the platform. Otherwise, the attestation will be provided within the native application code.
[0031] The native application then presents the initial grant data, the attestationObject (which contains the public key of the device-bound credentials), and a signature of the initial grant data (to verify the public key) to the token endpoint of the OAuth authorization server.
[0032] The OAuth authorization server validates the certificate using pre-configured metadata, including the trusted signer of the certificate private key. This validation includes checking that the authenticator data in the certificate object indicates that user validation was performed, if it is the server's policy. The initial grant data is also validated. The public key of the device-bound credential is associated with the OAuth grant on the server side, and initial refresh and access tokens are returned to the native application client.
[0033] Subsequent Grant Refresh
[0034] The native application occasionally performs a new refresh token flow when the access token expires. In one or more embodiments of the invention, the refresh token flow includes the FIDO authenticatorData along with the refresh token, and a signature (of a hash of the refresh token) performed using the private key of the credential bound to the device registered during the establishment of the initial grant. This provides proof to the server on each refresh that the request was generated on the device on which the grant was established. The clientDataJSON described in the FIDO authentication documentation includes the refresh token instead as a challenge provided by the server.
[0035] In one or more embodiments of the invention, the refresh_token is given a unique type. Example pseudocode for clientDataJSON is as follows: { “type”: “urn:mycustomapp:oauth”, “refresh_token”: “RT_value” }
[0036] Therefore, the challenge, origin, or tokenBinding fields defined by WebAuthn are not required.
[0037] Then the entire post body for the refresh token flow looks like this: POST / oauth / token client_id=public_client&grant_type=refresh_token&refresh_token=RT_value&authenticatorData=b64url_authenticator_data&signature=b64url_sig
[0038] The authentication server ensures that the RT_value is valid and represents a refresh token (RT) known to the server, looks up the associated public key registered in the grant at grant establishment (this public key becomes the allowCredentials list in FIDO terminology), and then ensures that the rest of the validation procedure in verifying the authentication assertion is successful, and since this is a native scenario and not a browser using pure WebAuthn, some non-critical considerations are given to the data values (such as origin, which in one or more embodiments of the invention is a Uniform Resource Name (URN)).
[0039] In one or more embodiments of the present invention, other mitigations, such as certificate pinning, are also employed as part of the overall solution to prevent application-level Man In The Middle (MITM) attacks.
[0040] Referring now to the figures, and in particular to FIG. 1, there is shown a block diagram of an exemplary system and network that may be utilized by and / or in the implementation of one or more embodiments of the present invention. With respect to server 101, some or all of the exemplary architecture including both the illustrated hardware and software shown within server 101 may be utilized by client device 123 or software deployment server 149 or computer resource server 151 or computer resource 153 or application certification service server 155 or artificial intelligence (AI) system 157 or blockchain network 159 or combinations thereof shown in FIG. 1, or by resource owner 200 or authorization server 201 or client device 223 or computer resource server 251 or computer resource 253 or application certification service server 255 or combinations thereof shown in FIG. 2, or by other processing devices shown in other figures associated with one or more embodiments of the present invention, or combinations thereof.
[0041] Exemplary server 101 includes processor 103 coupled to system bus 105. Processor 103 may utilize one or more processors, each of which includes one or more processor cores. A video adapter 107, which drives / supports a display 109, is also coupled to system bus 105. System bus 105 is coupled to input / output (I / O) bus 113 via bus bridge 111. I / O interface 115 is coupled to I / O bus 113 and provides communication with various I / O devices, including keyboard 117, mouse 119, media tray 121 (which may include storage devices such as CD-ROM drives, multimedia interfaces, etc.), and external USB port 125. The type of ports connected to I / O interface 115 may be any known to those skilled in the art of computer architecture, but in one embodiment, some or all of these ports are universal serial bus (USB) ports.
[0042] As shown, server 101 can communicate with network 127 using network interface 129. Network interface 129 is a hardware network interface such as a network interface card (NIC). Network 127 can be an external network, such as the Internet, or an internal network, such as an Ethernet or a virtual private network (VPN).
[0043] A hard drive interface 131 is also coupled to the system bus 105. The hard drive interface 131 interfaces with a hard drive 133. In one embodiment, the hard drive 133 inputs data to a system memory 135, which is also coupled to the system bus 105. The system memory is defined as the lowest level of volatile memory within the server 101. This volatile memory includes additional higher levels of volatile memory (not shown), including but not limited to cache memory, registers, and buffers. Data input to the system memory 135 includes the server's 101's operating system (OS) 137 and application programs 143.
[0044] The OS 137 includes a shell 139 for providing transparent user access to resources such as application programs 143. Generally, the shell 139 is a program that provides an interpreter and interface between a user and the operating system. More specifically, the shell 139 executes commands entered into a command line user interface or from a file. Thus, the shell 139 (also called a command processor) is typically the highest level software layer of an operating system and functions as a command interpreter. The shell provides a system prompt, interprets commands entered by keyboard, mouse, or other user input medium, and sends the interpreted commands to the appropriate lower level of the operating system (e.g., kernel 141) for processing. It is noted that while the shell 139 is a text-based, line-oriented user interface, one or more embodiments of the present invention suitably support other user interface modes as well, such as graphical, speech, gesture, etc.
[0045] As shown in the figure, OS 137 also includes a kernel 141 which contains the lower level functions of OS 137, including providing essential services required by other parts of OS 137 and application programs 143 (including memory management, process and task management, disk management, and mouse and keyboard management).
[0046] The application programs 143 include a renderer, illustratively shown as a browser 145. The browser 145 includes program modules and instructions that enable a world wide web (WWW) client (i.e., server 101) to send and receive network messages to the Internet using hypertext transfer protocol (HTTP) messaging, thus enabling communication with a client device 123 or a software deployment server 149 or a computer resource server 151 or a computer resource 153 or an application certification service server 155 or other computer systems, or combinations thereof.
[0047] The application programs 143 in the system memory of the server 101 also include a Program for Secure Access to Computer Resources (PSACR) 147. The PSACR 147 includes code for implementing the processes described below, including the processes described in Figures 2-7. In one or more embodiments of the invention, the server 101 can download the PSACR 147 from a software deployment server 149, which includes an on-demand download, where the code of the PSACR 147 is not downloaded until needed for execution. It is further noted that in one or more embodiments of the invention, the software deployment server 149 performs all of the functions related to the present invention (including execution of the PSACR 147), and therefore the server 101 does not need to use its own internal computing resources to execute the PSACR 147.
[0048] It is noted that the hardware elements depicted in server 101 are not intended to be exhaustive, but are representative to highlight essential components required by one or more embodiments of the present invention. For example, server 101 may include alternative memory storage devices such as magnetic cassettes, digital versatile disks (DVDs), Bernoulli cartridges, etc. These and other variations are intended to be within the scope of the present invention.
[0049] Referring now to FIG. 2, there is shown a high level overview of one or more embodiments of the present invention implemented within a modified Open Authorization (OAuth) system 206.
[0050] As shown in steps 1 and 2, the resource owner 200 is either a human user that interfaces with the client device 223 via a user interface, or a computer that is used by the user to present initial grant credentials to the client device via an application program interface (API), which in turn presents the initial grant credentials to the native application 202. Examples of such credentials include, but are not limited to, an authorization code, a username and password, etc.
[0051] As represented in step 2a (which is shown occurring within the client device 223 and communicating with an application credential service server 255 similar to the application credential service server 155 shown in FIG. 1), the native application 202 sends the initial grant credentials received from the resource owner 200 to the application credential service server 255. The application credential service server 255 provides a native application credential service that validates that the native application 202 has not been modified and is running on a genuine client device 223. The application credential service server 255 provides a cryptographic attestation of this credential, which is included in the payload of step 3a.
[0052] As shown in step 2b, the client device 223 then generates a public / private key pair 204 that is used as described below.
[0053] As shown in step 3a, the native application 202 sends the initial authorization grant, the certificate result (generated by the native application certificate service), the public key (generated by the native application 202), and a signature of the initial authorization grant signed using the corresponding private key to the authorization server 201.
[0054] As shown in step 3b, the authorization server validates the application's certificate using the application certificate service. If the certificate is not validated by the certificate service, the enrollment is aborted.
[0055] As shown in step 3c, the authorization server 201 verifies the public key using the signature of the initial authorization grant and stores the public key, which is used in the steps below to grant access to computer resources 253.
[0056] As shown in step 4, the authorization server 201 generates an initial access token and a refresh token and returns them to the native application. The initial access token allows the native application 202 to access computer resources 253, and the refresh token allows the authorization server 201 to refresh / renew the access token.
[0057] As shown in step 5, the native application 202 uses the access token (i.e., either the initial access token or a new access token whose generation by the authorization server 201 has been authorized by the refresh token) to access the computer resource 253 by the native application 202 on behalf of the resource owner 200.
[0058] Access tokens have a limited validity period (e.g., less than 5 minutes) and therefore need to be refreshed periodically through the use of a refresh token.
[0059] Thus, as shown in step 6, the native application 202 periodically exchanges the current refresh token with a new access token and a new refresh token with the authorization server 201. That is, the new refresh token replaces the old / current refresh token since the refresh token is disposable. When the native application 202 requests the authorization server 201 to generate a new refresh token, the old refresh token is signed by the native application 202 with its private key and this signature is sent to the authorization server 201 as part of the token refresh flow. Thus, the authorization server 201 generates and returns a new access token and a new refresh token only if the signature of the old refresh token is verified with the public key received in step 3a.
[0060] Referring now to FIG. 3, there is shown an overview flowchart of one or more operations that may be performed in one or more embodiments of the present invention.
[0061] After start block 301, as shown in block 303 and described in more detail in FIG. 2, the authorization server receives from the native application on the device an initial authorization grant, a public key of a private / public key pair generated on the device, and a certificate of authenticity for the native application.
[0062] As shown in block 305 and described in more detail in Figure 2, the authorization server receives the refresh token from the native application on the device and a digital signature of the refresh token created using the private key. In one or more embodiments of the invention, the authorization server recognizes the refresh token only if the refresh token is verified using a previously registered public key.
[0063] As shown in block 307 and described in more detail in FIG. 2, the authorization server then verifies the validity of the digital signature on the refresh token.
[0064] In response to validating the refresh token from the native application on the device, the authorization server sends a new access token and a new refresh token from the authorization server to the native application on the device, as shown in block 309 and described in more detail in Figure 2. The new access token enables the native application on the device to access computer resources.
[0065] The flow chart ends at end block 311.
[0066] In one or more embodiments of the present invention, as described herein, public / private keys are generated on the device and the private key is protected from unauthorized use or extraction by being bound to the device, i.e., the private key cannot be "hacked" by a malicious actor because only the client device that generated the public / private key pair has access to the private key.
[0067] In one or more embodiments of the invention, the authorization server and client are components of an Open Authorization (OAuth) architecture that has been modified by the invention (e.g., the modified Open Authorization (OAuth) system 206 shown in FIG. 2).
[0068] In one or more embodiments of the invention, as described above, data in the application payload from the client is used to verify that the refresh authorization grant comes from the device to which the refresh authorization grant was issued, without using Transport Layer Security (TLS) protocol extensions.
[0069] In one or more embodiments of the invention, one or more processors (e.g., in the authorization server 201 shown in FIG. 2) verify the identity of the device by applying Fast Identity Online (FIDO) authentication as part of the refresh authorization grant process. Details of FIDO and / or FIDO2 are described above.
[0070] In one or more embodiments of the present invention, the identity of a device is determined and / or confirmed by an identifier for that particular device, such as an Internet Protocol (IP) address used by that particular device and identified by a lookup table that associates that particular device with a particular IP address, a Media Access Control (MAC) address assigned by that particular device to a network interface controller for use as a network address in communicating within a network segment, a Uniform Universal Identifier (UUID) generated for that particular device that is unique to that particular device, etc.
[0071] As such, in one or more embodiments of the present invention, the authorization server validates the validity of a refresh token from a native application on a device only if the refresh token comes from the particular device that created the initial authorization grant and the public key of the private / public key pair. The authorization server, in one or more embodiments of the present invention, identifies that particular device by the IP address currently used by the particular device, the MAC address currently used by the particular device, the UUID of the particular device, etc., that are part of the header sent from that particular device to the authorization server when that particular device sends the initial authorization grant, the public key of the private / public key pair generated on the device, the certificate of authenticity of the native application, and the refresh token to the authorization server.
[0072] Thus, in one or more embodiments of the invention, the authorization server validates the validity of a refresh token from a native application on a device only if the refresh token comes from the particular device that created the initial authorization grant and the public key of the private / public key pair, regardless of which application in that device or another device sent the refresh token, initial authorization grant, and / or the public key of the private / public key pair to the authorization server.
[0073] In one or more embodiments of the present invention, a blockchain system is used to ensure that the data / elements / coefficients used by the authorization server 201 shown in FIG. 2 to generate access tokens and / or refresh tokens are valid by storing such data / elements / coefficients in a blockchain ledger.
[0074] Thus, referring to FIG. 4, in one or more embodiments of the present invention, a blockchain network 459 (similar to the blockchain network 159 shown in FIG. 1) is used to provide infrastructure (e.g., chaincode execution) and services (e.g., membership services such as identity management) to securely and transparently store, track, and manage transactions in a “single trusted location.” The blockchain network 459 maintains a verifiable record (in a single trusted location) of any and all transactions ever made in the system. After data are entered into the blockchain, they cannot be erased (immutable) or changed. That is, any change to the record is considered to issue / introduce a new transaction. Thus, the prohibition of such erasure or change ensures the auditability and verifiability of the data.
[0075] A blockchain network459 (also known as a "blockchain fabric", "blockchain system", "open blockchain", or "Hyperledger Fabric") is based on a distributed database of records of all transactions or digital events that are performed and shared among participating parties. Individual transactions in the blockchain are validated or verified through a consensus mechanism that incorporates the majority of participants in the system, thus allowing participating entities to know with certainty that a digital event has occurred by creating an irrefutable record in a permissioned public ledger.
[0076] When a transaction is executed, the corresponding chaincode is executed by multiple validating peers of the system. For example, as shown in FIG. 4, peers 418a-418d establish the validity of the transaction parameters and after the peers reach consensus, a new block is generated and added to the blockchain network. That is, an application process 408 (e.g., an OAuth process running on the authentication server 201 as described in FIG. 2) running on a monitoring computer 401 (e.g., the authentication server 201 shown in FIG. 2 or the server 101 shown in FIG. 1 or both) executes an application such as the app 403 (e.g., an OAut application) shown in the figure, which causes a software development kit (SDK) 410 to communicate using general remote procedure calls (grpc) with a membership service 409 supporting a peer-to-peer network 404, which supports a blockchain 416 using peers 418a-418g.
[0077] Referring to FIG. 5, an exemplary blockchain ledger 500 in blockchain 416 is shown, as may be utilized in one or more embodiments of the present invention.
[0078] In one or more embodiments of the invention, the blockchain ledger 500 includes an identifier (shown in block 502) of a monitoring computer, such as the authentication server 201 shown in FIG. 2 or the server 101 shown in FIG. 1, or both, that also supports and / or utilizes the peer-to-peer network 404 shown in FIG. 4. For example, in one or more embodiments of the invention, the block 502 includes an internet protocol (IP) address, uniform resource locator (URL), etc., of the monitoring computer. This information is used by peers in the peer-to-peer network 404 shown in FIG. 4 to receive transactions related to the process flows described herein.
[0079] In one or more embodiments of the invention, the blockchain ledger 500 also includes copies of the initial authorization grant (block 504), the public key (block 506), the certificate of authenticity of the native application (block 508), the refresh token (block 510), and the digital signature of the refresh token (block 512) that are utilized by the authentication server to generate a first new access token and a first new refresh token. The information from the blockchain ledger 500 is then retrieved in a form that is guaranteed to be unchanged since it was first presented to (but not necessarily used by) the authentication server. That is, the initial authorization grant, the public key of the private / public key pair generated on the device, and the certificate of authenticity of the native application are created and sent in parallel to both the authorization server and the blockchain. However, the initial authorization grant, the public key of the private / public key pair generated on the device, and the certificate of authenticity of the native application may be corrupted before being used by the authorization server. Therefore, the initial authorization grant, the public key of the private / public key pair generated on the device, and an uncorrupted version of the native application’s certificate of authenticity are stored on the blockchain, and these are stored in the blockchain system, preventing any data corruption.
[0080] An exemplary operation of the blockchain network 459 shown in FIG. 4 is illustrated in FIG. 6. As described in step 601, a computing device (e.g., the monitoring computer 401 shown in FIG. 4, which in one or more embodiments is the server 101 shown in FIG. 1 or the authorization server 201 shown in FIG. 2, or both) executes a transaction (e.g., receives a native application on the device, an initial authorization grant, a public key of a private / public key pair generated on the device, a certificate of authenticity for the native application, a refresh token, a digital signature of the refresh token created using the private key, etc., as previously described in FIG. 2). As shown in step 603, the monitoring computer 401 hashes the transaction using a hashing algorithm, such as the Secure Hash Algorithm (SHA-2), and then signs the hash using a digital signature. This signature is then broadcast to the peer-to-peer network 404 shown in FIG. 4, as described in step 605. As shown in step 607, a peer in the peer-to-peer network 404 (e.g., peer 418a) aggregates transactions into the blockchain 416 shown in FIG. 4. As shown in block 609, each block includes a link to the previous block. The newly modified blockchain 416 is validated (step 611) by one or more other peers among peers 418a-418d, or by other peers from other permissioned blockchain systems, or both. As described in step 613, the validated block is then broadcast to peers 418b-418d. These peers 418b-418d listen and receive the new block and merge the block into their copy of the blockchain 416 (step 615).
[0081] Thus, the Blockchain Fabric described in Figures 4-6 represents a blockchain deployment technology that provides a distributed ledger that persists and manages digital events, called transactions, shared among multiple participants, each of whom has a stake in these events. The ledger can only be updated by consensus among the participants. Furthermore, after transactions are recorded, they cannot be changed (they are immutable). All such recorded transactions are cryptographically verifiable using proofs of agreement from the participants, thus providing a robust provenance mechanism to track transaction origins.
[0082] Therefore, Blockchain Fabric maintains a digital ledger of events using a distributed network, thus achieving the superior security of a digital ledger, as the blockchain stored at each peer relies on previous blocks, which in turn provide secured data for subsequent blocks in the blockchain.
[0083] That is, the blockchain fabric described herein provides a decentralized system in which all nodes in the decentralized system contain a copy of the blockchain, thereby avoiding the need to have a centralized database managed by a trusted third party. Transactions are broadcast to the network using software applications. Network nodes can verify the validity of transactions, add them to their own copies, and then broadcast these additions to other nodes. But as previously mentioned, the blockchain is nevertheless highly secure because each new block is secured (e.g., hashed) based on one or more previous blocks.
[0084] Thus, in one or more embodiments of the present invention, it is assumed that the new access token described above in FIG. 3 is identified as the first new access token and the new refresh token is identified as the first new refresh token.
[0085] In one or more embodiments of the invention, a blockchain architecture (e.g., server 101 shown in FIG. 1, or authorization server 201 shown in FIG. 2, or monitoring computer 401 or blockchain network 459 or both, or a combination thereof, shown in FIG. 4) stores a stored blockchain including an initial authorization grant, a public key, a certificate of authenticity for the native application, a refresh token, and a digital signature of the refresh token that is utilized by the authentication server to generate a first new access token and a first new refresh token.
[0086] The monitoring computer (e.g., authorization server 201) retrieves the stored blockchain from the blockchain architecture and generates a second new access token and a second new refresh token by using the initial authorization grant from the stored blockchain, the public key, the certificate of authenticity of the native application, the refresh token, and the digital signature of the refresh token.
[0087] The one or more processors compare the first new access token and the first new refresh token to the second new access token and the second new refresh token to determine that the first new access token and the first new refresh token match the second new access token and the second new refresh token.
[0088] In response to determining that the first new access token and the first new refresh token match the second new access token and the second new refresh token, the one or more processors authorize the first new access token and the first new refresh token generated by the authorization server to be sent from the authorization server to the native application.
[0089] In one or more embodiments of the invention, the new access token is a first new access token and the new refresh token is a first new refresh token, the blockchain just described includes an initial authorization grant, a public key, a certificate of authenticity of the native application, a refresh token, and a digital signature of the refresh token that are utilized by the authentication server to generate the first new access token and the first new refresh token, the stored blockchain is retrieved from the blockchain architecture, and the authentication server generates a second new access token and a second new refresh token by using the initial authorization grant, the public key, the certificate of authenticity of the native application, the refresh token, and the digital signature of the refresh token from the stored blockchain.
[0090] However, in one or more of these embodiments, the one or more processors compare the first new access token and the first new refresh token to the second new access token and the second new refresh token to determine that the first new access token and the first new refresh token do not match the second new access token and the second new refresh token, and thus, in response to determining that the first new access token and the first new refresh token do not match the second new access token and the second new refresh token, the one or more processors prevent transmission of the first new access token and the first new refresh token generated by the authorization server from the authorization server to the native application.
[0091] Thus, the contents of the blockchain are used to verify that the initial authorization grant, public key, certificate of authenticity of the native application, refresh token, and digital signature of the refresh token utilized by the authentication server to generate the first new access token and the first new refresh token are valid, as guaranteed by their prior storage in the blockchain.
[0092] In one or more embodiments of the present invention, artificial intelligence (e.g., neural networks) is used to validate the access and refresh tokens generated by the authorization server.
[0093] 7, an exemplary artificial intelligence system for use in one or more embodiments of the present invention is a deep neural network (DNN) 757 (similar to artificial intelligence system 157 shown in FIG. 1) as utilized in one or more embodiments of the present invention. The nodes in DNN 757 may represent hardware processors, virtual processors, or software algorithms, or may represent combinations of hardware processors, virtual processors, or software algorithms.
[0094] In one or more embodiments of the invention, the DNN 757 is trained to generate neural network-generated access tokens or neural network-generated refresh tokens, or both, as shown in block 702.
[0095] The DNN 757 is trained to generate neural network-generated access tokens and / or neural network-generated refresh tokens using authorization server data 700 (e.g., initial authorization grants, public keys, certificates of authenticity for native applications, refresh tokens, and digital signatures of refresh tokens that are utilized by the authorization server to generate new access tokens and new refresh tokens), as shown in block 702. The DNN 757 is trained by using various known types of initial authorization grants, known types of public keys, known types of certificates of authenticity for native applications, known types of refresh tokens, and known types of digital signatures of refresh tokens that are used to generate known neural network-generated access tokens and / or neural network-generated refresh tokens.
[0096] DNN 757 is an exemplary type of neural network that may be used in one or more embodiments of the present invention. Other neural networks that may be used in one or more embodiments of the present invention include convolutional neural networks (CNNs) and neural networks that use other forms of deep learning.
[0097] Neural networks, as the name implies, are loosely modeled after biological neural networks (e.g., the human brain). Biological neural networks consist of a series of interconnected neurons that influence each other. For example, a first neuron may be electrically connected to a second neuron through the release of neurotransmitters that are received by the second neuron (from the first neuron) by a synapse. These neurotransmitters can cause excitation or inhibition of the second neuron. The pattern of interconnected neurons in excitation / inhibition ultimately leads to biological outcomes including thoughts, muscle movements, memory retrieval, etc. This description of biological neural networks is highly simplified, but the high-level overview is that one or more biological neurons influence the behavior of one or more other bioelectrically connected biological neurons.
[0098] Electronic neural networks are similarly made up of electronic neurons, but unlike biological neurons, electronic neurons are never technically "inhibitory" - only "excitatory" to varying degrees.
[0099] The electronic neurons (also referred to herein simply as "neurons" or "nodes") in the DNN 757 are arranged in layers known as the input layer 703, hidden layer 705, and output layer 707. The input layer 703 contains neurons / nodes that receive and send input data to a series of hidden layers of neurons (e.g., hidden layer 705), with neurons from one of the hidden layers interconnected with all neurons in the next of the hidden layers 705. The final layer of the hidden layers 705 then outputs the results of its calculations to the output layer 707, which is often a single node that holds vector information.
[0100] As previously mentioned, each node in the illustrated DNN 757 represents an electronic neuron, such as illustrated neuron 709. As shown in block 711, each neuron (including neuron 709) functionally includes at least four features: an algorithm, an output value, a weight, and a bias value.
[0101] An algorithm is a mathematical formula for processing data from one or more upstream neurons. For example, assume that one or more of the neurons shown in the central hidden layer 705 send data values to neuron 709. Neuron 709 then processes these data values by performing the mathematical function shown in block 711 to create one or more output values, which are then sent to another neuron, such as another neuron in the hidden layer 705 or a neuron in the output layer 707. Each neuron also has a weight that is specific to that neuron or other connected neurons or both. Additionally, the output value is added to a bias value to increase or decrease the output value, allowing the DNN 757 to be further "fine-tuned."
[0102] For example, assume that neuron 713 is sending the results of an analysis of a portion of data to neuron 709. Neuron 709 has a first weight that defines how important the data coming from neuron 713 in particular is. If this data is important, the data coming from neuron 713 is weighted more heavily and / or augmented by a bias value, thus causing the mathematical function in neuron 709 to generate a larger output that has a greater influence on the neurons in the output layer 707. Similarly, if neuron 713 is determined to be important to the operation of neuron 709, the weight of neuron 713 is increased so that neuron 709 receives a larger value of the output of the mathematical function in neuron 713. Alternatively, the output of neuron 709 can be minimized by reducing the weight and / or bias used to influence the output of neuron 709. These weights / biases can be adjusted for one, some, or all of all neurons in DNN 757 so that reliable outputs result from the output layer 707. In one or more embodiments of the present invention, finding the weight and bias values is performed automatically by training a neural network. In one or more embodiments of the present invention, manual tuning is applied to adjust hyperparameters such as learning rate, dropout, regularization factor, etc. Training a neural network thus involves performing forward and backward propagation over multiple datasets until optimal weight and bias values are reached that minimize a loss function. The loss function measures the difference in the predicted values and actual labels by the neural network for various inputs.
[0103] When manually adjusted during DNN 757 training, the weights are adjusted in an iterative manner until the outputs from the output layer 707 match expectations.
[0104] When automatically adjusted, the weights (and / or mathematical functions) are adjusted using "backpropagation," which adjusts the weight values of neurons by using a "gradient descent" method to determine in which direction each weight value should be adjusted. This gradient descent process moves the weights in each neuron in a particular direction until the output from the output layer 707 improves (e.g., correctly generates the appropriate access and refresh tokens).
[0105] As shown in FIG. 7, the individual layers of neurons are shaded differently to indicate that, in one or more embodiments of the present invention, these layers are specifically trained to recognize different aspects of the information used by the authentication server when generating refresh tokens.
[0106] Thus, in one or more embodiments of the invention, within hidden layer 705 there is layer 706 containing neurons designed to evaluate the type of authorization grant, layer 708 containing neurons designed to evaluate the type of public key, and layer 710 containing neurons designed to evaluate the type of certificate of trustworthiness of the native application.
[0107] The outputs of neurons from layer 710 then control the values detected in the output layer 707 .
[0108] Thus, one or more embodiments of the present invention input an initial authorization grant, a public key, a certificate of authenticity of the native application, a refresh token, and a digital signature of the refresh token to a neural network, where the neural network is trained to generate a neural network-generated access token and a neural network-generated refresh token. The one or more processors then compare the new access token and the new refresh token generated by the authorization server with the access token and the refresh token generated by the neural network to verify the validity of the new access token and the new refresh token generated by the authorization server.
[0109] In one or more embodiments of the invention, the one or more processors determine that the new access token and the new refresh token match the access token generated by the neural network and the refresh token generated by the neural network. In response to determining that the new access token and the new refresh token match the access token generated by the neural network and the refresh token generated by the neural network, the one or more processors send the new access token and the new refresh token to the native application.
[0110] In one or more embodiments of the invention, the one or more processors determine that the new access token and the new refresh token do not match the access token generated by the neural network and the refresh token generated by the neural network. In response to determining that the new access token and the new refresh token do not match the access token generated by the neural network and the refresh token generated by the neural network, the one or more processors prevent transmission of the new access token and the new refresh token to the native application.
[0111] Thus, in one or more embodiments of the present invention, the neural network validates or invalidates the work performed by the aforementioned authentication server.
[0112] Therefore, attestation of authenticity of a native application, as described in various embodiments presented herein, ensures the integrity and authenticity of the native application and the device.
[0113] In one or more embodiments, the present invention is implemented using cloud computing. Nevertheless, although this disclosure includes detailed descriptions of cloud computing, it is understood in advance that implementation of the subject matter presented herein is not limited to a cloud computing environment. Rather, embodiments of the present invention may be implemented in conjunction with any other type of computing environment now known or later developed.
[0114] Cloud computing is a service delivery model for enabling convenient, on-demand network access to a shared pool of configurable computational resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) and for rapidly provisioning and releasing these resources with minimal administrative effort or interaction with the service provider. This cloud model includes at least five characteristics, at least three service models, and at least four deployment models.
[0115] The features are as follows:
[0116] On-Demand Self-Service: Cloud customers can automatically provision server time and computing power, such as network storage, as needed, without the need for unilateral human interaction with the service provider.
[0117] Broad Network Access: The capability is available over the network and can be accessed using standard mechanisms, facilitating use by heterogeneous thin-client or thick-client platforms (e.g., cell phones, laptops, and PDAs).
[0118] Resource Pool: The provider's computing resources are pooled and offered to multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically allocated and reallocated according to demand. Consumers typically have a sense of location independence in that they have no control or knowledge regarding the exact location of the resources offered to them, but can still specify a location (e.g., country, state, or data center) at a higher level of abstraction.
[0119] Rapid Elasticity: Capacity is provisioned quickly and elastically, in some cases automatically, so it can be quickly scaled out and quickly released to quickly scale in. Capacity available for provisioning often appears to the consumer as unlimited, available for purchase in any quantity at any time.
[0120] Metered Services: Cloud systems leverage metering to automatically control and optimize resource usage at a level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency to both providers and consumers of the services utilized.
[0121] SaaS (Software as a Service): The capability provided to the consumer is the use of the provider's applications running on a cloud infrastructure. Those applications can be accessed from a variety of client devices through thin-client interfaces such as web browsers (e.g., web-based email). The consumer does not manage or control the underlying cloud infrastructure, including the network, servers, operating systems, storage, or individual application functionality, except for the possibility of limited user-specific application configuration settings.
[0122] PaaS (Platform as a Service): The capability provided to a consumer is to deploy applications that the consumer creates or acquires, written using programming languages and tools supported by the provider, onto a cloud infrastructure. The consumer does not manage or control the underlying cloud infrastructure, including networks, servers, operating systems, or storage, but does have control over the deployed applications and, in some cases, the configuration of the application hosting environment.
[0123] Infrastructure as a Service (IaaS): The capability provided to a consumer is the provisioning of processing, storage, network, and other basic computing resources onto which the consumer can deploy and run any software, which may include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure, but has control over the operating systems, storage, deployed applications, and in some cases, limited control over selected network components (e.g., host firewalls).
[0124] The deployment model is as follows:
[0125] Private Cloud: The cloud infrastructure is operated solely for the organization. In one or more embodiments, the cloud infrastructure is managed by the organization or a third party and / or resides on-premise or off-premise.
[0126] Community Cloud: The cloud infrastructure is shared by multiple organizations to support a particular community with shared concerns (e.g., mission, security requirements, policies, and compliance considerations). In one or more embodiments, the cloud infrastructure is managed by these organizations or a third party, and / or resides on-premises or off-premises.
[0127] Public Cloud: This cloud infrastructure is available for use by general users or large industry organizations and is owned by an organization that sells cloud services.
[0128] Hybrid cloud: This cloud infrastructure is a combination of two or more clouds (private, community, or public) that remain uniquely connected to each other through standardized or proprietary technologies that allow for data and application portability (e.g., cloud bursting to balance the load between clouds).
[0129] A cloud computing environment is a service-oriented environment with an emphasis on statelessness, loose coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure that comprises a network of interconnected nodes.
[0130] 8, an exemplary cloud computing environment 50 is shown. As shown, the cloud computing environment 50 includes one or more cloud computing nodes 10 with which local computing devices used by cloud consumers (e.g., personal digital assistants (PDAs) or mobile phones 54A, desktop computers 54B, laptop computers 54C, or automotive computer systems 54N, or combinations thereof) communicate. In addition, the nodes 10 communicate with each other. In one embodiment, the nodes are physically or virtually grouped (not shown) in one or more networks, such as a private cloud, a community cloud, a public cloud, or a hybrid cloud, or combinations thereof, as previously described. This allows the cloud computing environment 50 to provide an infrastructure, platform, or SaaS, or combinations thereof, that does not require the cloud consumer to maintain resources on a local computing device. The types of computing devices 54A-54N illustrated in FIG. 8 are intended as examples only, and it will be understood that the computing node 10 and cloud computing environment 50 may communicate with any type of computer-controlled device via any type of network or network-addressable connection (e.g., a connection using a web browser) or both.
[0131] 9, there is shown a set of functional abstraction layers provided by cloud computing environment 50 (FIG. 9). It should be understood in advance that the components, layers, and functions shown in FIG. 8 are intended to be illustrative only and that embodiments of the present invention are not limited thereto. As shown, the following layers and corresponding functions are provided:
[0132] The hardware and software layer 60 includes hardware and software components. Examples of hardware components include mainframes 61, RISC (Reduced Instruction Set Computer) architecture based servers 62, servers 63, blade servers 64, storage devices 65, and networks and network components 66. In some embodiments, the software components include network application server software 67 and database software 68.
[0133] The virtualization layer 70, in one or more embodiments, comprises an abstraction layer at which virtual entities such as virtual servers 71, virtual storage 72, virtual networks including virtual private networks 73, virtual applications and operating systems 74, and virtual clients 75 are provided.
[0134] By way of example, the management layer 80 provides the following functions: Resource provisioning 81 dynamically procures computing and other resources utilized to execute tasks within the cloud computing environment; Metering and pricing 82 tracks costs as resources are utilized within the cloud computing environment and sends bills or invoices for the utilization of those resources; By way of example, those resources include application software licenses; Security verifies the identity of cloud users and tasks, and protects data and other resources; User portal 83 provides access to the cloud computing environment for users and system administrators; Service level management 84 allocates and manages cloud computing resources to meet required service levels; Service level agreement (SLA) planning and execution 85 pre-provisions and procures cloud computing resources in anticipation of upcoming demands and in accordance with SLAs.
[0135] Workload layer 90 illustrates examples of functionality utilized in a cloud computing environment in one or more embodiments. Examples of workloads and functionality provided from this layer include mapping and navigation 91, software development and lifecycle management 92, virtual classroom instruction delivery 93, data analytics processing 94, transaction processing 95, and secure computer resource access processing 96 that perform one or more of the inventive features described herein.
[0136] The present invention may be a system, method, or computer program product, or a combination thereof. The computer program product may include one or more computer readable storage media containing computer readable program instructions for causing a processor to perform aspects of the present invention.
[0137] A computer readable storage medium can be a tangible device that can hold and store instructions for use by an instruction execution device. A computer readable storage medium can be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. A non-exhaustive list of more specific examples of computer readable storage media includes portable floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disk read-only memory (CD-ROM), digital versatile disk (DVD), memory stick, floppy disk, mechanically encoded devices such as punch cards or ridge structures in grooves on which instructions are recorded, and any suitable combination thereof. As used herein, a computer-readable storage medium should not be construed as a signal that is itself ephemeral, such as electric waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., light pulses passing through a fiber optic cable), or electrical signals transmitted over wires.
[0138] The computer readable program instructions described herein may be downloaded from a computer readable storage medium to each computing device / processing device or to an external computer or storage device over a network (e.g., the Internet, a local area network, a wide area network, or a wireless network, or a combination thereof) that may include copper transmission cables, optical transmission fiber, wireless transmission, routers, firewalls, switches, gateway computers, or edge servers, or a combination thereof. A network adapter card or network interface within each computing device / processing device receives the computer readable program instructions from the network and transfers the computer readable program instructions for storage on a computer readable storage medium within each computing device / processing device.
[0139] The computer readable program instructions for carrying out the operations of the present invention may be assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including object oriented programming languages such as Java, Smalltalk, C++, and traditional procedural programming languages such as the "C" programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partially on the user's computer as a standalone software package, partially on the user's computer and on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or wide area network (WAN), or the connection may be made to an external computer (e.g., via the Internet using an Internet Service Provider). In some embodiments, to carry out aspects of the invention, electronic circuitry including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), may execute computer readable program instructions to customize the electronic circuitry by utilizing state information of the computer readable program instructions.
[0140] Aspects of the present invention are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks included in the flowchart illustrations and / or block diagrams, can be implemented by computer readable program instructions.
[0141] These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, executed by the processor of the computer or other programmable data processing apparatus, produce means for performing the functions / operations specified in one or more blocks of the flowcharts and / or block diagrams. These computer readable program instructions may be stored on a computer readable storage medium and capable of directing a computer, programmable data processing apparatus, or other device, or combination thereof, to function in a particular manner, such that the computer readable storage medium on which the instructions are stored comprises an article of manufacture containing instructions for performing aspects of the functions / operations specified in one or more blocks of the flowcharts and / or block diagrams.
[0142] Computer-readable program instructions may be loaded into a computer, other programmable data processing apparatus, or other device such that the instructions, which execute on the computer, other programmable apparatus, or other device, perform the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams, thereby causing a series of operable steps to be performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process.
[0143] The terms used herein are for the purpose of describing particular embodiments only and are not intended to be limiting of the invention. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and / or "comprising", as used herein, indicate the presence of stated features, integers, steps, operations, elements or components, or combinations thereof, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or groups thereof, or combinations thereof.
[0144] Corresponding structures, materials, acts, and equivalents of all means or steps and functional elements within the scope of the following claims are intended to include any structures, materials, or acts for performing functions in combination with other claimed elements as specifically claimed. The description of various embodiments of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or to limit the invention in the disclosed form. Many changes and modifications will become apparent to those skilled in the art without departing from the scope of the invention. The embodiments have been selected and described in order to best explain the principles and practical application of the invention and to enable others skilled in the art to understand the invention in terms of various embodiments with various modifications as suited to the particular use contemplated.
[0145] In one or more embodiments of the invention, any of the methods described in this disclosure are implemented by using VHDL (VHSIC Hardware Description Language) programs and VHDL chips. VHDL is an example of a design entry language for field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), and other similar electronic devices. Thus, in one or more embodiments of the invention, any of the software-implemented methods described herein are emulated by a hardware-based VHDL program and then applied to a VHDL chip, such as an FPGA.
[0146] Thus, having described in detail the embodiments of the invention in this application, and with reference to the example embodiments, it will be apparent that changes and modifications are possible without departing from the scope of the invention as defined in the appended claims.
Claims
1. receiving, by an authorization server, from a native application on a device, an initial authorization grant, a public key of a private / public key pair generated on the device, and a certificate of authenticity of the native application; receiving, by the authorization server, from the native application on the device, a refresh token and a digital signature of the refresh token created using the private key, wherein the authorization server recognizes the refresh token only if the refresh token is verified using the pre-registered public key; verifying, by the authorization server, the validity of the digital signature of the refresh token; in response to validating the refresh token from the native application on the device, transmitting, by the authorization server, a new access token and a new refresh token from the authorization server to the native application on the device, the new access token enabling the native application on the device to access the computer resource; A method comprising:
2. The method of claim 1 , wherein the attestation of authenticity of the native application ensures the integrity and authenticity of the native application and device.
3. The method of claim 1 , wherein the public / private keys are generated on the device, and the private key is protected from unauthorized use or extraction by being bound to the device.
4. The method of claim 1 , wherein the authorization server and the client are components of an Open Authorization (OAuth) architecture.
5. 2. The method of claim 1, wherein a refresh authorization grant is verified to come from the device to which the refresh authorization grant was issued using data in an application payload from the client without using Transport Layer Security (TLS) protocol extensions.
6. 10. The method of claim 1, further comprising verifying, by one or more processors, an identity of the device by applying Fast Identity Online (FIDO) authentication as part of a refresh authorization grant process.
7. inputting the initial authorization grant, the public key, the certificate of authenticity of the native application, the refresh token, and the digital signature of the refresh token into a neural network, wherein the neural network is trained to generate a neural network-generated access token and a neural network-generated refresh token; comparing, by one or more processors, the new access token and the new refresh token generated by the authorization server with the access token and the refresh token generated by the neural network to verify validity of the new access token and the new refresh token generated by the authorization server; The method of claim 1 further comprising:
8. determining, by one or more processors, that the new access token and the new refresh token match the access token generated by the neural network and the refresh token generated by the neural network; sending, by one or more processors, the new access token and the new refresh token to the native application in response to determining that the new access token and the new refresh token match the access token generated by the neural network and the refresh token generated by the neural network; The method of claim 7 further comprising:
9. determining, by one or more processors, that the new access token and the new refresh token do not match the access token generated by the neural network and the refresh token generated by the neural network; blocking, by one or more processors, transmission of the new access token and the new refresh token to the native application in response to determining that the new access token and the new refresh token do not match the access token generated by the neural network and the refresh token generated by the neural network; The method of claim 7 further comprising:
10. The new access token is a first new access token, the new refresh token is a first new refresh token, and the method further comprises: storing a stored blockchain in a blockchain architecture, the stored blockchain including the initial authorization grant utilized by the authentication server to generate the first new access token and the first new refresh token, the public key, the certificate of authenticity of the native application, the refresh token, and the digital signature of the refresh token; Retrieving the stored blockchain from the blockchain architecture; and generating, by the authentication server, a second new access token and a second new refresh token by using the initial authorization grant from the stored blockchain, the public key, the certificate of authenticity of the native application, the refresh token, and the digital signature of the refresh token; comparing, by one or more processors, the first new access token and the first new refresh token with the second new access token and the second new refresh token to determine that the first new access token and the first new refresh token match the second new access token and the second new refresh token; in response to determining that the first new access token and the first new refresh token match the second new access token and the second new refresh token, authorizing, by one or more processors, the first new access token and the first new refresh token generated by the authorization server to be sent from the authorization server to the native application; The method of claim 1 further comprising:
11. The new access token is a first new access token, the new refresh token is a first new refresh token, and the method further comprises: storing in a blockchain architecture a stored blockchain including the initial authorization grant, the public key, the certificate of authenticity of the native application, the refresh token, and the digital signature of the refresh token that is utilized by the authentication server to generate the first new access token and the first new refresh token; Retrieving the stored blockchain from the blockchain architecture; and generating, by the authentication server, a second new access token and a second new refresh token by using the initial authorization grant from the stored blockchain, the public key, the certificate of authenticity of the native application, the refresh token, and the digital signature of the refresh token; comparing, by one or more processors, the first new access token and the first new refresh token with the second new access token and the second new refresh token to determine that the first new access token and the first new refresh token do not match the second new access token and the second new refresh token; in response to determining that the first new access token and the first new refresh token do not match the second new access token and the second new refresh token, blocking, by one or more processors, transmission of the first new access token and the first new refresh token generated by the authorization server from the authorization server to the native application; The method of claim 1 further comprising:
12. A computer program product comprising a computer readable storage medium having program code embodied therein, the computer readable storage medium itself not being a transitory signal, the program code being readable and executable by a processor to perform a method, the method comprising: receiving from a native application on a device an initial authorization grant, a public key of a private / public key pair generated on the device, and a certificate of authenticity of the native application; receiving, from the native application on the device, a refresh token and a digital signature of the refresh token created using the private key, wherein the authorization server recognizes the refresh token only if the refresh token is verified using the pre-registered public key; validating the digital signature of the refresh token; and in response to validating the refresh token from the native application on the device, transmitting a new access token and a new refresh token from the authorization server to the native application on the device, the new access token enabling the native application on the device to access the computer resource; 2. A computer program product comprising:
13. 13. The computer program product of claim 12, wherein the attestation of authenticity of the native application ensures the integrity and authenticity of the native application and device.
14. 13. The computer program product of claim 12, wherein the public / private keys are generated on the device, and the private key is protected from unauthorized use or extraction by being bound to the device.
15. 13. The computer program product of claim 12, wherein the authorization server and the client are components of an Open Authorization (OAuth) architecture.
16. 13. The computer program product of claim 12, wherein a refresh authorization grant is verified to come from the device to which the refresh authorization grant was issued using data in an application payload from the client without using a Transport Layer Security (TLS) protocol extension.
17. 13. The computer program product of claim 12, wherein the program code is provided as a service in a cloud environment.
18. 1. A computer system comprising one or more processors, one or more computer readable memories, and one or more computer readable non-transitory storage media, wherein program instructions are stored in at least one of the one or more computer readable non-transitory storage media for execution by at least one of the one or more processors via at least one of the one or more computer readable memories, the stored program instructions comprising: receiving from a native application on a device an initial authorization grant, a public key of a private / public key pair generated on the device, and a certificate of authenticity of the native application; receiving, from the native application on the device, a refresh token and a digital signature of the refresh token created using the private key, wherein the authorization server recognizes the refresh token only if the refresh token is verified using the pre-registered public key; validating the digital signature of the refresh token; and in response to validating the refresh token from the native application on the device, transmitting a new access token and a new refresh token from the authorization server to the native application on the device, the new access token enabling the native application on the device to access the computer resource; A computer system configured to perform a method including:
19. 20. The computer system of claim 18, wherein the authorization server and the client are components of an Open Authorization (OAuth) architecture, and a refresh authorization grant is verified to come from the device to which the refresh authorization grant was issued using data in an application payload from the client without using a Transport Layer Security (TLS) protocol extension.
20. 20. The computer system of claim 18, wherein the stored program instructions are provided as a service in a cloud environment.
Citation Information
Patent Citations
Authorization server and control method thereof, program, and right transfer system
JP2018081643A
Information processing apparatus, information process system, and program
JP2021060924A
Broker-Based Authentication System Architecture and Design
US20160259936A1
Refresh token for credential renewal
US20200153831A1
Information processing apparatus, information processing system, and non-transitory computer readable medium storing program
US20210112048A1
