Systems and methods for securing communication between a native application and an embedded hybrid component on an electronic device

A method for securing communication may include: (1) receiving, at the authorization platform and from a hybrid browser component of a computer application, an encrypted payload comprising an authentication code, a bundle identifier, and an application unique identifier; (2) registering, by the authorization platform, a username for a user; (3) receiving, at the authentication framework and from the computer application, the username and the encrypted payload; (4) receiving, at the authentication framework, user login credentials from the user; (5) validating, by the authentication framework, the user login credentials; (6) passing, by the authentication framework to the authorization platform, the encrypted payload; (6) comparing, by the authorization platform the encrypted payload received from the computer application to the encrypted payload received from the authentication framework; and (8) accepting, by the authentication framework, the encrypted payload and tying the process to the computer application.

BACKGROUND OF THE INVENTION

Field of the Invention

The present disclosure generally relates to systems and methods for securing communication between a native application and an embedded hybrid component on an electronic device.

Description of the Related Art

Computer programs or applications executed by mobile electronic devices may use embedded hybrid applications written in JavaScript to perform certain functions. This use enables the computer program to perform actions that it otherwise could not.

SUMMARY OF THE INVENTION

Systems and methods for securing communication between a native application and an embedded hybrid component on an electronic device are disclosed. In one embodiment, in an information processing apparatus comprising an authorization platform and an authentication framework, each comprising at least one computer processor, a method for securing communication between a native application and a hybrid browser component on an electronic device may include: (1) receiving, at the authorization platform and from a hybrid browser component of a computer application executed by an electronic device, an encrypted payload comprising an authentication code, a bundle identifier, and an application unique identifier; (2) registering, by the authorization platform, a username for a user; (3) receiving, at the authentication framework and from the computer application, the username and the encrypted payload; (4) receiving, at the authentication framework, user login credentials from the user; (5) validating, by the authentication framework, the user login credentials; (6) passing, by the authentication framework to the authorization platform, the encrypted payload; (6) comparing, by the authorization platform the encrypted payload received from the computer application to the encrypted payload received from the authentication framework; and (8) accepting, by the authentication framework, the encrypted payload and tying the process to the computer application.

In one embodiment, the authentication code may include a timestamp.

In one embodiment, the mobile computer application may execute digital account opening process.

In one embodiment, the authentication code has an expiration. The authorization platform may validate that the authentication code is unexpired.

In one embodiment, the encrypted payload further comprises a device identifier.

In one embodiment, the method may further include the authentication framework generating a session identifier and device identifier after validating the login credentials.

In one embodiment, the authentication framework may provide the session identifier to the authorization platform.

In one embodiment, the method may further include decisioning an application to open an account.

According to another embodiment, a system for securing communication between a native application and a hybrid browser component on an electronic device may include a mobile electronic device executing a computer application comprising a hybrid browser component; a security framework in communication with the hybrid browser component; an authorization platform in communication with the hybrid browser component; a risk engine in communication with the authorization platform; and an authentication framework in communication with the hybrid browser component. The hybrid browser component may receive an encrypted payload comprising an authentication code, a bundle identifier, and an application unique identifier from the security framework. The authorization platform may register a username for a user. The computer application may provide the authentication framework with the username and the encrypted payload, and may provide the authentication framework with user login credentials received from the user. The authentication framework may validate the user login credentials, and may provide the authorization platform with the encrypted payload. The authorization platform may compare the encrypted payload received from the computer application to the encrypted payload received from the authentication framework. The authentication framework may accept the encrypted payload and ties the process to the computer application.

In one embodiment, the authentication code may include a timestamp.

In one embodiment, the mobile computer application may execute a digital account opening process.

In one embodiment, the authentication code has an expiration. The authorization platform may validate that the authentication code is unexpired.

In one embodiment, the encrypted payload may also include a device identifier.

In one embodiment, the authentication framework may generate a session identifier and device identifier after validating the login credentials.

In one embodiment, the authentication framework may provide the session identifier to the authorization platform.

In one embodiment, the authentication platform may decision an application to open an account.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Embodiments are directed to systems and methods for securing communication between a native application and an embedded hybrid component on an electronic device.

In one embodiment, during digital account opening, or DAO, using a native application that uses a hybrid component (e.g., written in JavaScript running within a context of a hybrid browser, such as WebView), a one-time token may be securely transferred between the hybrid browser session within the native application and the application. The one-time token may establish a connection between the two independent instances within the mobile (e.g., native) application. It may further establish device trust during digital account opening.

Embodiments may facilitate the transfer of an opaque blob or payload that may be used to store session keys, secure data, etc., while maintaining confidentiality and integrity throughout the process, from a mobile application platform to an embedded hybrid web view back to a service endpoint. The blob or payload may include, for example, an application universally unique identifier (UUID), an application bundle identifier that may uniquely identify an application, and an authentication code.

A security framework may generate an authentication code (e.g., AUTH_CODE) that may be a short-lived code, such as 3-5 minutes. In one embodiment, authentication code may include a timestamp. The authentication code may be based, for example, on a random number.

In one embodiment, the security framework may provide an API to return an encrypted payload using, for example, RSA public key encryption.

In one embodiment, fields and or information that may be used to identify the device (e.g., AUTH_MOBILE_MIS) may be included in the blob or payload.

The mobile application, using the security framework, may launch a DAO flow. In one embodiment, the mobile application may call the security framework to retrieve the encrypted blob or payload, and may pass the encrypted blob or payload as part of java bridge to a DAO hybrid browser, which may be a component of the mobile application. The application may then pass the encrypted blob or payload to authentication after a successful DAO.

In one embodiment, the user may complete the DAO flow, and may enter a username and password. The username and password may be encrypted and provided to an authorization platform. The authorization platform may decrypt the blob or payload and may generate a session identifier (e.g., SM_SESSION) and device identifier (e.g., device_id) for the user. The DAO process may receive the session identifier from authorization platform, and may store the session identifier in store (e.g., a cookie store) of the native application.

The hybrid browser may pass the encrypted payload to the authentication platform, and the authentication platform may decrypt the payload and persist this data against the username. If necessary, the user may complete the DAO flow and may successfully register username and password to the authentication platform. The DAO hybrid browser may return the username to mobile application.

The authentication framework may launch a login flow after a successful DAO for a new customer. The customer may enter, for example, the customer's username and password. The framework may encrypt the application UUID, the bundle identifier, and the authentication code. For example, AES with a key generated using PBKFD2(username+password+fixedsalt+iteration_count). The encrypted payload may be sent as part of login to the authentication platform.

In another embodiment, the authentication framework may also check for a session identifier (e.g., SM_SESSION) with a store (e.g., a cookie store).

The authorization platform may receive the encrypted payload as part of login request; decrypt the payload by deriving the same AES key using, for example, username+password+fixedsalt, iteration_count; and may compare the decrypted payload to match what was received above.

In one embodiment, the session identifier may be provided to authentication framework. The authentication framework may provide authentication services.

If the decrypted payload matches the earlier payload, and the timestamp has not expired, authentication services may accept the payload and may tie the DAO application from device to first application login.

After successful login, authentication services may send this event to a back-end risk engine to evaluate risks and preset rules to update the trust level for the customer. For example, the risk engine may receive a trust flag, and may provide this to the authorization platform, which may provide this trust flag to the authentication framework.

Embodiments may provide some or all of the following advantages: (1) a man-in-the-middle on Java-bridge cannot understand the encrypted payload and the format used to read this token; (2) the user may be made to enter username and password to generate an encryption key on an authorization framework to re-encrypt the payload, so this verifies the user; (3) the authorization platform may reject the authentication code based on expiration and/or use count, which prevents replay attacks; (4) the payload may be encrypted when it leaves the mobile application; (5) the authorization platform receives the same blob or payload from the mobile application and the authentication framework, which proves that DAO was initiated from a native app context, and not by a rogue or tampered DAO middleware on the native app.

Referring toFIG. 1, a system for securing communication between a native application and an embedded hybrid component on an electronic device is disclosed according to one embodiment. System100may include mobile device110that may execute one or more computer applications, programs, etc. such as mobile application112. Mobile device110may be any suitable mobile device, including smartphones, tablet computers, notebook computers, desktop computers, smart watches, Internet of Things (IoT) appliances, etc.

Mobile application112may include browser114, which may be a hybrid browser, such as WebView.

Mobile device110, mobile application112, and/or browser114may interface with security framework120, which may be provided by a financial institution providing a digital account opening process. In one embodiment, security framework120may be hosted by the financial institution; in another embodiment, security framework120may be hosted by a third party.

In one embodiment, security framework120may generate and/or provide a payload for mobile application112and/or browser114. The payload may include, for example, an authentication code. In one embodiment, the authentication code may be a short-lived code, such as 3-5 minutes. In one embodiment, authentication code may include a timestamp. The authentication code may be based, for example, on a random number.

Mobile device110, mobile application112, and/or browser114may interface with authorization platform130. In one embodiment, authorization platform may decision a request for digital account opening. In one embodiment, authorization platform may interface with systems that may be internal to or external to the financial institution, including, for example, risk engine150.

Risk engine150may provide a risk assessment of the digital account opening request. In one embodiment, the risk assessment may be based on the mobile device from which the request originated, the IP address of the request, the username and password, past experience with the username, etc.

Mobile device110, mobile application112, and/or browser114may interface with authentication framework140. Authentication framework140may authenticate the user based on the username and password received from mobile application112and/or browser114.

Referring toFIG. 2, a method for securing communication between a native application and an embedded hybrid component on an electronic device is disclosed according to one embodiment.

In step200, a user may initiate the DAO process using a mobile application or computer program. In one embodiment, the mobile application may include a hybrid browser component.

In one embodiment, using the mobile application, the user may initiate the DAO process by selecting an option to open an account. Any other suitable manner of initiating the DAO process may be used as is necessary and/or desired.

In step205, the mobile application may receive an encrypted payload (i.e., a blob) from a security framework. In one embodiment, the encrypted payload may include an authentication code. In one embodiment, the authentication code may be a short-lived code, such as 3-5 minutes. The authentication code may have a longer life, or a short life, as is necessary and/or desired. In one embodiment, authentication code may include a timestamp. The authentication code may be based, for example, on a random number, a pseudo-random number, etc.

In one embodiment, the mobile application may use an API to retrieve the encrypted payload.

In step210, the mobile application may launch a digital account opening (DAO) process using, for example, a hybrid browser component, and, in step215, the mobile application may pass the payload including, for example, the authentication code, a bundle identifier, and an application unique identifier (e.g., application UUID) from a hybrid browser in the mobile application to an authorization platform.

In one embodiment, the payload may be encrypted.

In one embodiment, fields and or information that may be used to identify the device (e.g., AUTH_MOBILE_MIS) may be included in the payload.

In step220, the user may complete the DAO flow and may successfully register username with the authorization platform. The hybrid browser may return the username to mobile application using, for example, a Java bridge.

If necessary, in step225, the user may enter a username and password into the mobile application, and the mobile application may provide the username and password to an authentication framework to authenticate the user. In one embodiment, the username and password may be encrypted before they are provided to the authentication framework.

In one embodiment, the user may be asked for authentication information if any criteria in the risk engine does not match. In one embodiment, challenge questions, out-of-band authentication, etc. may be used as is necessary and/or desired.

In step230, the authentication framework may decrypt the username and password and may validate the username and password. In one embodiment, after validation, the authentication framework may pass the encrypted application unique identifier, the bundle identifier, and the authentication code to the authorization platform. The authentication framework may further generate a session identifier (e.g., SM_SESSION) and device identifier (e.g., device_id) for the user.

In one embodiment, the authentication framework may receive the information with the username and password

In one embodiment, the session identifier may be provided to the authorization platform.

In step235, the authorization platform may receive and decrypt the payload. If the decrypted payload matches the earlier payload, and the timestamp has not expired, authentication services may accept the payload and may tie the DAO application from the device to first application login.

In step240, the authorization platform may decision the application. In one embodiment the authorization engine may provide information to a back-end risk engine to evaluate risks and preset rules to update the trust level.

Although several embodiments have been disclosed, it should be recognized that these embodiments are not exclusive to each other, and certain elements or features from one embodiment may be used with another.

The processing machine used to implement the invention may utilize a suitable operating system. Thus, embodiments of the invention may include a processing machine running the iOS operating system, the OS X operating system, the Android operating system, the Microsoft Windows™ operating systems, the Unix operating system, the Linux operating system, the Xenix operating system, the IBM AIX™ operating system, the Hewlett-Packard UX™ operating system, the Novell Netware™ operating system, the Sun Microsystems Solaris™ operating system, the OS/2™ operating system, the BeOS™ operating system, the Macintosh operating system, the Apache operating system, an OpenStep™ operating system or another operating system or platform.