Middleware as a service

• US 10,205,611 B2
• Filed: 06/17/2015
• Issued: 02/12/2019
• Est. Priority Date: 02/11/2015
• Status: Active Grant

• Current Assignee: Dell Products LP (Dell Technologies Inc.)
• Original Assignee: Dell Products LP (Dell Technologies Inc.)
• Inventors: Fausak, Andrew T., Rombakh, Oleg
• Primary Examiner(s): Chacko, Joe
• Application Number:
  US14/742,092
• Publication Number:
  US 20160234286A1
• Time in Patent Office: 1,336 Days
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 12/4679 Arrangements for the registration or de-registration of VLAN attribute values, e.g. VLAN identifiers, port VLAN membership
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/08 specially adapted for terminal emulation, e.g. Telnet
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/131 Protocols for games, networked simulations or virtual reality
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols
• CPC Class Codes: H04L 9/3213 using tickets or tokens, e.g. Kerberos network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807
• CPC Class Codes: Y02D 30/50 in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

In particular embodiments, a first computing device may receive a request from a software to access information of a remote device of a client device, the client device being coupled to the first computing device, and access the information of the remote device based at least on a virtual interface of the remote device, and send, responsive to the received request, the accessed information to the software.

Claims

1. A method comprising, by a first computing device:

receiving, via a middleware of the first computing device, a request from a software to access information of a remote device of a client device, the client device being coupled to the first computing device, wherein the client device cannot access the information of the remote device;

accessing the information of the remote device based at least on a virtual interface of the remote device, wherein the virtual interface is associated with the middleware, and wherein accessing the information comprises;

instructing, by the middleware, the remote device to read the information from a smart card of the remote device; and

transcoding the accessed information received from the remote device between at least a first protocol and a second protocol;

sending, responsive to the received request, the accessed information to the software, wherein the information redirects the client device from the first computing device to one or more servers, wherein the accessed information authenticates and authorizes a user of the client device to access the one or more servers; and

sending an instruction to the client device to connect with the one or more servers, wherein the information comprises one or more additional credentials that authenticate and authorize the client device to connect with the one or more servers.

2. The method of claim 1, wherein the software resides on the first computing device.

3. The method of claim 1, wherein the software resides on a second computing device, the second computing device being coupled to the first computing device.

4. The method of claim 1, wherein the remote device is secured, the secured remote device being accessible only by one or more pre-determined software.

5. The method of claim 1, wherein the client device being coupled to the first computing device comprises a remote desktop protocol connection between the client device and the first computing device, and wherein the virtual interface comprises one or more virtual channels of the remote desktop protocol connection.

6. The method of claim 1, wherein the remote device is a radio-frequency identification (RFID) reader.

7. The method of claim 1, wherein the virtual interface comprises a virtual universal serial bus (USB) interface of the remote device.

8. The method of claim 1, wherein accessing the information of the remote device comprises:

one or more primitive device input/output operations; and

one or more protocols, the protocols being associated with a multi-factor authentication algorithm.

9. The method of claim 1, wherein the accessed information comprises hardware extractable information, the hardware extractable information being utilized by the software for authentication.

10. One or more computer-readable non-transitory storage media embodying logic that is operable when executed to:

by a first computing device;

receiving, via a middleware of the first computing device, a request from a software to access information of a remote device of a client device, the client device being coupled to the first computing device, wherein the client device cannot access the information of the remote device;

accessing the information of the remote device based at least on a virtual interface of the remote device, wherein the virtual interface is associated with the middleware, and wherein accessing the information comprises;

instructing, by the middleware, the remote device to read the information from a smart card of the remote device; and

transcoding the accessed information received from the remote device between at least a first protocol and a second protocol;

sending, responsive to the received request, the accessed information to the software, wherein the information redirects the client device from the first computing device to one or more servers, wherein the accessed information authenticates and authorizes a user of the client device to access the one or more servers; and

sending an instruction to the client device to connect with the one or more servers, wherein the information comprises one or more additional credentials that authenticate and authorize the client device to connect with the one or more servers.

11. The media of claim 10, wherein the software resides on the first computing device.

12. The media of claim 10, wherein the software resides on a second computing device, the second computing device being coupled to the first computing device.

13. The media of claim 10, wherein the virtual interface comprises a virtual universal serial bus (USB) interface of the remote device.

14. The media of claim 10, wherein accessing the information of the remote device comprises:

one or more primitive device input/output operations; and

one or more protocols, the protocols being associated with a multi-factor authentication algorithm.

15. The media of claim 10, wherein the accessed information comprises hardware extractable information, the hardware extractable information being utilized by the software for authentication.

16. An information handling system comprising:

one or more processors; and

a memory coupled to the processors comprising instructions executable by the processors, the processors being operable when executing the instructions to;

by a first computing device;

receiving, via a middleware of the first computing device, a request from a software to access information of a remote device of a client device, the client device being coupled to the first computing device, wherein the client device cannot access the information of the remote device;

accessing the information of the remote device based at least on a virtual interface of the remote device, wherein the virtual interface is associated with the middleware, and wherein accessing the information comprises;

instructing, by the middleware, the remote device to read the information from a smart card of the remote device; and

transcoding the accessed information received from the remote device between at least a first protocol and a second protocol;

sending, responsive to the received request, the accessed information to the software, wherein the information redirects the client device from the first computing device to one or more servers, wherein the accessed information authenticates and authorizes a user of the client device to access the one or more servers; and

sending an instruction to the client device to connect with the one or more servers, wherein the information comprises one or more additional credentials that authenticate and authorize the client device to connect with the one or more servers.

17. The information handling system of claim 16, wherein the software resides on the first computing device.

18. The information handling system of claim 16, wherein the software resides on a second computing device, the second computing device being coupled to the first computing device.

19. The information handling system of claim 16, wherein the virtual interface comprises a virtual universal serial bus (USB) interface of the remote device.

20. The information handling system of claim 16, wherein accessing the information of the remote device comprises:

one or more primitive device input/output operations; and

one or more protocols, the protocols being associated with a multi-factor authentication algorithm.