Passing authentication token to authorize access to rest calls via web sockets
Various techniques for facilitating communication with and across a clinical environment and a cloud environment are described. For example, a method for authenticating a network device residing in the clinical environment using a token is described. An authentication proxy in the cloud environment can receive a request from a connectivity adapter in the clinical environment and retrieve a security token from an authentication system in the cloud. The connectivity adapter can use the security token to send signed requests to the authentication system.
1. A method for authenticating a network device residing in a clinical environment, the method comprising:
processing, by an authentication proxy in communication with (i) the network device residing in the clinical environment, and (ii) an authentication system, an authentication request from the network device residing in the clinical environment via a first network connection, wherein the authentication request includes identifying information associated with the clinical environment, and wherein the clinical environment includes one or more medical devices in communication with the network device;
transmitting login credentials usable to authenticate the network device to the authentication system via a second network connection different from the first network connection via which the authentication request was received;
receiving a token from the authentication system, the token being usable by the network device to transmit requests to the authentication system; and
transmitting the token to the network device residing in the clinical environment via the first network connection that is different from the second network connection via which the token was received.
2. The method of claim 1 , wherein the first network connection is a Web Socket connection.
3. The method of claim 1 , wherein the first network connection is secured and authenticated.
4. The method of claim 1 , further comprising causing the network device residing in the clinical environment to transmit a signed request to the authentication system.
5. The method of claim 1 , wherein the first network connection and the second network connection are both established over a wide area network.
6. The method of claim 1 , further comprising receiving a message from the network device residing in the clinical environment via the first network connection, wherein the message includes information associated with the one or more medical devices in communication with the network device.
7. The method of claim 6 , wherein the network device is configured to communicate with the one or more medical devices over a local area network.
8. A system configured to authenticate a network device residing in a clinical environment, the system comprising:
one or more processors in communication with (i) a network device residing in the clinical environment, and (ii) an authentication system configured to authenticate requests from the network device; and
one or more memories in communication with the one or more processors and storing computer-executable instructions that, when executed by the one or more processors, configure the one or more processors to:
process an authentication request from the network device residing in the clinical environment via a first network connection, wherein the authentication request includes identifying information associated with the clinical environment, and wherein the clinical environment includes one or more medical devices in communication with the network device;
cause login credentials usable to authenticate the network device to be transmitted to the authentication system via a second network connection different from the first network connection via which the authentication request was received;
receive a token from the authentication system, the token being usable by the network device to transmit requests to the authentication system; and
cause the token to be transmitted to the network device residing in the clinical environment via the first network connection that is different from the second network connection via which the token was received.
9. The system of claim 8 , wherein the first network connection is a Web Socket connection.
10. The system of claim 8 , wherein the first network connection is secured and authenticated.
11. The system of claim 8 , wherein the computer-executable instructions, when executed by the one or more processors, further configure the one or more processors to cause the network device residing in the clinical environment to transmit a signed request to the authentication system.
12. The system of claim 8 , wherein the first network connection and the second network connection are both established over a wide area network.
13. The system of claim 8 , wherein the computer-executable instructions, when executed by the one or more processors, further configure the one or more processors to receive a message from the network device residing in the clinical environment via the first network connection, wherein the message includes information associated with the one or more medical devices in communication with the network device.
14. The system of claim 13 , wherein the network device is configured to communicate with the one or more medical devices over a local area network.
15. Non-transitory physical computer storage storing computer-executable instructions that, when executed by one or more computing devices in communication with (i) a network device residing in a clinical environment, and (ii) an authentication system, configure the one or more computing devices to:
process an authentication request from the network device residing in the clinical environment via a first network connection, wherein the authentication request includes identifying information associated with the clinical environment, and wherein the clinical environment includes one or more medical devices in communication with the network device;
cause login credentials usable to authenticate the network device to be transmitted to the authentication system via a second network connection different from the first network connection via which the authentication request was received;
receive a token from the authentication system, the token being usable by the network device to transmit requests to the authentication system; and
cause the token to be transmitted to the network device residing in the clinical environment via the first network connection that is different from the second network connection via which the token was received.
16. The non-transitory physical computer storage of claim 15 , wherein the first network connection is a secured and authenticated Web Socket connection.
17. The non-transitory physical computer storage of claim 15 , wherein the computer-executable instructions, when executed by the one or more computing devices, further configure the one or more computing devices to cause the network device residing in the clinical environment to transmit a signed request to the authentication system.
18. The non-transitory physical computer storage of claim 15 , wherein the first network connection and the second network connection are both established over a wide area network.
19. The non-transitory physical computer storage of claim 15 , wherein the computer-executable instructions, when executed by the one or more computing devices, further configure the one or more computing devices to receive a message from the network device residing in the clinical environment via the first network connection, wherein the message includes information associated with the one or more medical devices in communication with the network device.
20. The non-transitory physical computer storage of claim 15 , wherein the network device is configured to communicate with the one or more medical devices over a local area network.