Cryptographic mechanisms for software setup using token-based two-factor authentication
A method and system for authenticating software licenses of a software includes a request for a software authentication received from one or more software subscribers and one or more electronic licenses distributed between one or more software vendors and the one or more software subscribers. Further, one or more tokens are validated through an authentication engine at a delivery packet delivered to the software subscriber. A license key associated with each validated token is generated and distributed through a licensing engine. The software is initiated to be enabled through the license key.
1. A method comprising;
receiving, by a computing device, a request for software authentication from a client machine of a software subscriber;
distributing, by the computing device, an electronic license between a software vendor and the client machine of the software subscriber based on the received request for the software authentication, wherein the electronic license comprises software responsive to the request and a token configured to interact with an authentication engine at the client machine for one or more validation checks;
generating, by the computing device, a license key in response to a received notification of the validation of the token by the authentication engine at the client machine; and
distributing, by the computing device, the generated license key to the client machine of the software subscriber, wherein the distributed license key is configured to initiate enablement of the software at the client machine.
2. The method as set forth in claim 1 wherein the token is a one-time encrypted token.
3. The method as set forth in claim 1 wherein the token is further configured to interact with the authentication engine at the client machine for the one or more validation checks comprising a determination if the token has previously been used.
4. The method as set forth in claim 1 further comprising:
reissuing, by the computing device, the generated token in response to a received notification of the validation of the token by the authentication engine at the client machine and an issue with the enablement of the software at the client machine.
5. A non-transitory machine readable medium having stored thereon instructions comprising machine executable code which when executed by at least one machine causes the machine to:
receive a request for software authentication from a client machine of a software subscriber;
distribute an electronic license between a software vendor and the client machine of the software subscriber based on the received request for the software authentication, wherein the electronic license comprises software responsive to the request and a token configured to interact with an authentication engine at the client machine for one or more validation checks;
generate a license key in response to a received notification of the validation of the token by the authentication engine at the client machine; and
distribute the generated license key to the client machine of the software subscriber, wherein the distributed license key is configured to initiate enablement of the software at the client machine.
6. The medium as set forth in claim 5 wherein the token is a one-time encrypted token.
7. The medium as set forth in claim 5 wherein the token is further configured to interact with the authentication engine at the client machine for the one or more validation checks comprising a determination if the token has previously been used.
8. The medium as set forth in claim 4 wherein the instructions further comprise machine executable code which when executed by at least one machine causes the machine to:
reissue the generated token in response to a received notification of the validation of the token by the authentication engine at the client machine and an issue with the enablement of the software at the client machine.
9. A computing device comprising:
a memory containing non-transitory machine readable medium comprising machine executable code having stored thereon instructions for managing workload within a storage system; and
a processor coupled to the memory, the processor configured to execute the machine executable code to cause the processor to:
receive a request for software authentication from a client machine of a software subscriber;
distribute an electronic license between a software vendor and the client machine of the software subscriber based on the received request for the software authentication, wherein the electronic license comprises software responsive to the request and a token configured to interact with an authentication engine at the client machine for one or more validation checks;
generate a license key in response to a received notification of the validation of the token by the authentication engine at the client machine; and
distribute the generated license key to the client machine of the software subscriber, wherein the distributed license key is configured to initiate enablement of the software at the client machine.
10. The device as set forth in claim 9 wherein the token is a one-time encrypted token.
11. The device as set forth in claim 9 wherein the token is further configured to interact with the authentication engine at the client machine for the one or more validation checks comprising a determination if the token has previously been used.
12. The device as set forth in claim 9 wherein the processor is further configured to execute the machine executable code to further cause the processor to:
reissue the generated token in response to a received notification of the validation of the token by the authentication engine at the client machine and an issue with the enablement of the software at the client machine.