SECURED DATA ACCESS FROM A MOBILE DEVICE EXECUTING A NATIVE MOBILE APPLICATION AND A HEADLESS BROWSER

• US 20180262910A1
• Filed: 05/16/2018
• Published: 09/13/2018
• Est. Priority Date: 03/31/2016
• Status: Active Grant

• Current Assignee: AppBrilliance, Inc.
• Original Assignee: AppBrilliance, Inc.
• Inventors: Smith, Charles Eric, Dutrow, Chris, Ayestaran, Sergio
• Granted Patent: US 10,785,651 B2
• Time in Patent Office: Days
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: H04B 1/3827 Portable transceivers
• CPC Class Codes: H04L 63/168 above the transport layer
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04W 12/068 using credential vaults, e.g. password manager applications or one time password [OTP] applications
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 12/086 using security domains

Abstract

Systems, methods, and computer-readable storage devices to enable secured data access from a mobile device executing a native mobile application and a headless browser are disclosed.

Claims

1. A mobile device comprising:

a wireless transceiver;

a processor;

a display device; and

a memory storing instructions executable by the processor to perform operations comprising;

receiving, at a native application, access credential data;

providing the access credential data from the native application to a headless browser;

initiating a secured connection via the wireless transceiver from the headless browser to a remote server that hosts a website, the server supporting access to secured data without relying on an application programming interface;

sending, by the headless browser via the secured connection, the access credential data to the remote server;

receiving first web page data of the website from the remote server via the secured connection;

parsing the first web page data to identify user-specific data;

sending the user-specific data to the native application for display in a graphical user interface at the display device;

receiving a user command via a user input device;

sending, by the headless browser via the secured connection, a request to the remote server to access the secured data based on the user command; and

receiving, by the headless browser via the secured connection, at least a portion of the secured data.

2. The mobile device of claim 1, wherein the graphical user interface of the native application includes information based on virtual application programming interface (API) fingerprint data associated with the website, and wherein the virtual API fingerprint data indicates service pathways associated with a log in, an authentication, an operation at the remote server, or a combination thereof.

3. The mobile device of claim 1, wherein the headless browser comprises a web browser not having a corresponding displayed graphical user interface.

4. The mobile device of claim 1, wherein the secured connection comprises a secure sockets layer (SSL) connection.

5. The mobile device of claim 1, wherein the website includes content formatted for presentation on a desktop computer or a laptop computer.

6. The mobile device of claim 1, wherein the website includes content formatted for presentation on mobile devices.

7. The mobile device of claim 1, wherein sending the access credential data to the remote server emulates a request to login to the website from a non-headless browser.

8. The mobile device of claim 1, further comprising a location device, the display device, and a user input device.

9. The mobile device of claim 1, wherein the wireless transceiver includes or is coupled to radio frequency (RF) circuitry, a controller, an antenna, or any combination thereof.

10. The mobile device of claim 1, wherein the native application enables, via the headless browser, a read operation with respect to the secured data, a write operation with respect to the secured data, or both.

11. The mobile device of claim 1, wherein code corresponding to the native application includes code corresponding to the headless browser.

12. The mobile device of claim 1, wherein the processor is configured to access the headless browser via at least one web browsing software library.

13. The mobile device of claim 1, wherein the processor is configured to access an instance of the headless browser via one or more application programming interface (API) calls to an operating system of the mobile device.

14. A method of operation at a mobile device, the method comprising:

receiving, at a native application, access credential data;

providing the access credential data from the native application to a headless browser;

initiating a secured connection from the headless browser to a remote server that hosts a website, the server supporting access to secured data without relying on an application programming interface;

sending, by the headless browser via the secured connection, the access credential data to the remote server;

receiving first web page data of the website from the remote server via the secured connection;

parsing the first web page data to identify user-specific data;

displaying the user-specific data in a graphical user interface of the native application;

receiving a user command via a user input device;

sending, by the headless browser via the secured connection, a request to the remote server to access secured data based on the user command; and

receiving, by the headless browser via the secured connection, at least a portion of the secured data.

15. The method of claim 14, wherein the user command includes a command to read at least the portion of the secured data.

16. The method of claim 14, wherein the graphical user interface of the native application includes information based on virtual application programming interface (API) fingerprint data associated with the website, and wherein the virtual API fingerprint data indicates service pathways associated with a log in, an authentication, an operation at the remote server, or a combination thereof.

17. The method of claim 14, wherein identifying the user-specific data comprises accessing a mapping between the native application and the website, and wherein the mapping is determined based on a scraping operation performed on the website, through javascript injection or other supported language interpreted by a web browser, or a combination thereof.

18. A computer-readable storage device storing instructions that, when executed by a processor, cause the processor to perform operations comprising:

receiving, at a native application, access credential data;

providing the access credential data from the native application to a headless browser;

initiating a secured connection from the headless browser to a remote server that hosts a website, the server supporting access to secured data without relying on an application programming interface;

sending, by the headless browser via the secured connection, the access credential data to the remote server;

receiving first web page data of the website from the remote server via the secured connection;

parsing the first web page data to identify user-specific data; and

displaying the user-specific data in a graphical user interface of the native application.

19. The computer-readable storage device of claim 18, wherein the graphical user interface of the native application includes information based on fingerprint data associated with the website, and wherein the fingerprint data indicates service pathways associated with a log in, an authentication, an operation at the remote server, or a combination thereof.

20. The computer-readable storage device of claim 18, wherein the operations further comprise:

receiving a user command via a user input device;

sending, by the headless browser via the secured connection, transaction data to the remote server to modify at least a portion of the secured data based on the user command; and

receiving, by the headless browser via the secured connection, a confirmation of the modification of at least the portion of the secured data.