Device specific secure licensing
Device-specific secure software licensing techniques are disclosed. In various embodiments, a key/token pair associated with a client requesting license validation is received. It is determined whether the key/token pair matches an entry in a store of currently valid key/token pairs. An affirmative response is sent in the event the key/token pair matches a corresponding entry in the store of currently valid key/token pairs.
1. A method of licensing software, comprising:
receiving, at a server, a key-token pair associated with a client requesting license validation in response to the client (a) obtaining a network connection or (b) determining that the license validation is due based on the current day and time;
determining that the key-token pair matches an entry in a store of currently valid key-token pairs;
generating a new token based at least in part on the determination that the key-token pair matches the entry;
replacing the entry with a new key-token pair including the new token; and
sending to the client an encrypted file that includes (a) the new token and (b) a next check time, wherein the next check time defines a particular day and a particular time by which a next validation request should be sent to the server.
2. The method of claim 1 , further comprising taking responsive action in the event the key-token pair does not match any entry in the store of currently valid key-token pairs.
3. The method of claim 1 , wherein the key comprises an activation key.
4. The method of claim 3 , further comprising receiving an activation request that includes the activation key; determining that activation is authorized; and generating and providing a response that includes the key-token pair.
5. The method of claim 1 , further comprising configuring the client to request validation opportunistically without at least initially interfering with access to or use of the licensed software.
6. The method of claim 1 , further comprising configuring the client to at least temporarily block or otherwise restrict access to or use of the licensed software in the event a successful validation has not been completed within a prescribed time.
7. The method of claim 2 , wherein the responsive action includes blocking or otherwise restricting access to and/or use of the licensed software at the client.
8. The method of claim 2 , wherein the responsive action includes blocking or otherwise restricting access to and/or use of the licensed software at clients associated with the key included in the key-token pair received from the client.
9. A license enforcement system, comprising:
a communication interface configured to receive a key-token pair associated with a client requesting license validation in response to the client (a) obtaining a network connection or (b) determining that the license validation is due based on the current day and time; and
a computer processor coupled to the communication interface and configured to:
determine that the key-token pair matches an entry in a store of currently valid key-token pairs;
generate a new token based at least in part on the determination that the key-token pair matches the entry;
replace the entry with a new key-token pair including the new token; and
send to the client an encrypted file that includes (a) the new token and (b) a next check time, wherein the next check time defines a particular day and a particular time by which a next validation request should be sent to the server.
10. The system of claim 9 , wherein the processor is further configured to take responsive action in the event the key-token pair does not match any entry in the store of currently valid key-token pairs.
11. The system of claim 10 , wherein the responsive action includes blocking or otherwise restricting access to and/or use of the licensed software at the client.
12. The system of claim 10 , wherein the responsive action includes blocking or otherwise restricting access to and/or use of the licensed software at clients associated with the key included in the key-token pair received from the client.
13. A computer program product embodied in a tangible, non-transitory computer readable storage medium and comprising computer instructions for:
receiving a key-token pair associated with a client requesting license validation in response to the client (a) obtaining a network connection or (b) determining that the license validation is due based on the current day and time;
determining that the key-token pair matches an entry in a store of currently valid key-token pairs;
generating a new token based at least in part on the determination that the key-token pair matches the entry;
replacing the entry with a new key-token pair including the new token; and
sending to the client an encrypted file that includes (a) the new token and (b) a next check time, wherein the next check time defines a particular day and a particular time by which a next validation request should be sent to the server.
14. The computer program product of claim 13 , further comprising computer instructions for taking responsive action in the event the key-token pair does not match any entry in the store of currently valid key-token pairs.
15. The method of claim 1 , further comprising configuring the client to at least temporarily block or otherwise restrict access to or use of the licensed software if a successful validation has not been completed prior to the next check time.
16. The system of claim 9 , further comprising configuring the client to at least temporarily block or otherwise restrict access to or use of the licensed software if a successful validation has not been completed prior to the next check time.