Using secure web sockets to extend reach of conditional access systems
A system and method for securely and bi-directionally transmitting information including conditional access private data between a client and a headend is disclosed. In an exemplary embodiment, the method includes: establishing a hypertext transfer protocol secure (HTTPs) connection, establishing a hypertext transfer protocol secure (HTTPs) connection; upgrading the HTTPs connection to a persistent bi-directional connection, accepting a first message from a client via the web socket connection, wherein the first message comprises an identifier of the client, parsing the message for the identifier of the client, associating the identifier of the client with the secure web socket connection, and transmitting a second message notifying the headend of the secure web site that connection, the message comprising the identifier of the client.
1. A method of securely and bi-directionally transmitting information comprising conditional access private data between a client and a headend, the method comprising:
establishing a hypertext transfer protocol secure (HTTPs) connection;
upgrading the HTTPs connection to a persistent bi-directional connection;
accepting a first message from the client via the persistent bi-directional connection, wherein the first message comprises an identifier of the client;
parsing the first message for the identifier of the client;
associating the identifier of the client with the persistent bi-directional connection; and
transmitting a second message notifying the headend of the persistent bi-directional connection, the second message comprising the identifier of the client.
2. The method of claim 1 , wherein establishing an HTTPs connection comprises transmitting an HTTPs connect message from the client to a web server.
3. The method of claim 1 wherein the persistent bi-directional connection is a secure web socket connection.
4. The method of claim 3 , further comprising upstreaming the secure web socket connection to a server side application.
5. The method of claim 3 , wherein:
the first message further comprises a state of the client; and
wherein the second message further comprises the state of the client.
6. The method of claim 3 , wherein a server side application manages the secure web socket connection.
7. The method of claim 3 , further comprising:
receiving an entitlement request via the secure web socket connection;
looking up the identifier of the client based upon the secure web socket connection;
providing the entitlement request received via the secure web socket connection and the identifier of the client to the headend;
receiving an entitlement response from the headend;
up the secure web socket connection based upon the identifier of the client; and
providing the entitlement response to the client via the secure web socket connection.
8. An apparatus for securely and bi-directionally transmitting information comprising conditional access private data between a client and a headend, the apparatus comprising:
a processor;
a memory, communicatively coupled to the processor, the memory comprising processor instructions comprising instructions for:
establishing a hypertext transfer protocol secure (HTTPs) connection;
upgrading the HTTPs connection to a persistent bi-directional connection;
accepting a first message from the client via the persistent bi-directional connection, wherein the first message comprises an identifier of the client;
parsing the first message for the identifier of the client;
associating the identifier of the client with the persistent bi-directional connection; and
transmitting a second message notifying the headend of the persistent bi-directional connection, the second message comprising the identifier of the client.
9. The apparatus of claim 8 , wherein establishing an HTTPs connection comprises transmitting an HTTPs connect message from the client to a web server.
10. The apparatus of claim 8 wherein the persistent bi-directional connection is a secure web socket connection.
11. The apparatus of claim 10 , further comprising upstreaming the secure web socket connection to a server side application.
12. The apparatus of claim 10 , wherein:
first message further comprises a state of the client; and
wherein the second message further comprises the state of the client.
13. The apparatus of claim 10 , wherein a server side application manages the secure web socket connection.
14. The apparatus of claim 10 , further comprising:
receiving an entitlement request via the secure web socket connection;
looking up the identifier of the client based upon the secure web socket connection;
providing the entitlement request received via the secure web socket connection and the identifier of the client to the headend;
receiving an entitlement response from the headend;
looking up the secure web socket connection based upon the identifier of the client; and
providing the entitlement response to the client via the secure web socket connection.