Accessing local information based on a browser session

Patent metadata

Field	Value
Publication number	US-10601831-B2
Application number	US-201514943225-A
Country	US
Kind code	B2
Filing date	Nov 17, 2015
Priority date	Nov 17, 2015
Publication date	Mar 24, 2020
Grant date	Mar 24, 2020

Abstract

When a user is attempting to access a server application, a challenge is received, in a browser, for a one or more login credentials to access a server application (e.g., a web page). For example, a user is requested to provide a user name and password to login to the server application. In response to the user providing the credentials via the browser, the login credentials are sent. If the credentials are validated, an access token is received by the browser from the server application. In response to receiving the access token for the server application, the browser sends the access token and an address for the server application, via a local loopback address, to a local application. This allows the local application to send local information, such as local files, to the server application using the token.

First claim

What is claimed is:

1. A method comprising:
receiving, by a processor and via a browser, a challenge for one or more user login credentials;
sending, by the processor and from the browser, the one or more user login credentials;
in response to sending the one or more user login credentials, receiving, by the processor and at the browser, a security access token for a remote server application; and
in response to receiving, at the browser, the security access token for the remote server application, sending, by the browser, via the processor, the security access token and an address for the remote server application, via a local loopback address, to a separate local application, wherein the processor, the browser, and the separate local application are on a user communication device and the remote server application is external to the user communication device.

2. The method of claim 1 , wherein the remote server application is a remote web server application, and further comprising:
sending, by the separate local application, the security access token to the remote web server application to allow the separate local application to directly communicate with the remote web server application; and
directly sending, by the separate local application, to the remote web server application, local information that cannot be accessed directly by the browser.

3. The method of claim 1 , wherein the separate local application sends information to the browser for display in the browser.

4. The method of claim 1 , further comprising:
sending, by the separate local application, a request to the remote server application using the security access token.

5. The method of claim 1 , wherein claim 1 is implemented as a plug-in the browser.

6. The method of claim 1 , wherein the separate local application is a non-browser application.

7. The method of claim 1 , wherein the separate local application comprises a plurality of separate local applications that each use the security access token to access the remote server application.

8. The method of claim 1 , wherein the separate local application has a Hyper Text Transfer Protocol (HTTP) stack that is bound to the loopback address.

9. The method of claim 8 , wherein the loopback address is within an IP address range of 127.0.0.0 to 127.0.0.8.

10. A communication device comprising:
a memory,
a processor in communication with the memory, the processor operable to execute software modules, the software modules comprising:
a browser that receives a challenge for one or more user login credentials; sends the one or more user login credentials; receives a security access token for a remote server application in response to sending the one or more user login credentials, and sends the security access token and an address of the remote server application, via a local loopback address, to a separate local application in response to receiving the security access token for the remote server application, wherein the separate local application is also on the communication device and wherein the remote server is external to the communication device.

11. The communication device of claim 10 , further comprising:
the separate local application that sends the security access token to the remote server application to allow the separate local application to directly communicate with the remote server application and directly sends local information that cannot be accessed directly by the browser to the remote server application.

12. The communication device of claim 10 , wherein the separate local application sends information to the browser for display in the browser.

13. The communication device of claim 10 , wherein the separate local application sends a request to the remote server application using the security access token.

14. The communication device of claim 10 , wherein a browser plug-in implements the system of claim 10 .

15. The communication device of claim 10 , wherein the separate local application is a non-browser application.

16. The communication device of claim 10 , wherein the separate local application comprises a plurality of separate local applications that each use the security access token to access the remote server application.

17. The communication device of claim 10 , wherein the separate local application has a Hyper Text Transfer Protocol (HTTP) stack that is bound to the loopback address.

18. The communication device of claim 17 , wherein the loopback address is within an IP address range of 127.0.0.0 to 127.0.0.8.

19. The communication device of claim 10 , wherein the security access token sent to the separate local application identifies a communication session between the browser and the remote server application.

20. The communication device of claim 11 , wherein the remote server application sends the sent local information for display in the browser.

Assignees

• Avaya Inc

Inventors

• Ezell Joel M
• Balasaygun Mehmet C
• Baskwill Geoff

Classifications

• H04L67/02

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• H04L63/10 Primary

  for controlling access to devices or network resources · CPC title

• H04L63/0807

  using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213) · CPC title