Application program as key for authorizing access to resources
In a networked environment, an application executed on a computing device may transmit a distribution rule associated with a resource. The distribution rule can require a key application to be enabled as hardware associated with a client device prior to access to a resource. The application may receive a request for access to the resource by the client device. In an instance in which it is determined that the client device complies with the distribution rule, the application may provide, to the client device, authorization to access the resource.
1. A method, comprising:
transmitting, from a computing device, a first distribution rule that requires a key application as a prerequisite to accessing a resource, wherein the first distribution rule further requires the key application to be enabled as hardware associated with a client device;
determining, on the client device, that a second distribution rule requires at least one other application installed on the client device;
receiving, on the computing device, a request for access to the resource by the client device; and
in an instance in which the client device complies with the distribution rule and the second distribution rule, providing, to the client device, authorization to access the resource.
2. The method of claim 1 , wherein the request further comprises a key application identifier identifying the key application as hardware.
3. The method of claim 1 , further comprising:
receiving, on the computing device, an authorization credential comprising a key, a token, a personal identification number, or a certificate provided by the key application.
4. The method of claim 3 , wherein the request further comprises the authorization credential.
5. The method of claim 3 , wherein the request further comprises the authorization credential and a user credential that is different from the authorization credential.
6. The method of claim 5 , wherein the user credential comprises at least one of: a user name or a password.
7. The method of claim 1 , further comprising:
transmitting, on the computing device, a request for confirmation that the client device complies with the first distribution rule and the second distribution rule.
8. A client device, comprising:
at least one application executable by a processor, wherein the at least one application, when executed, causes the processor to at least;
transmit, by the processor, a first distribution rule that requires a key application as a prerequisite to accessing a resource, wherein the first distribution rule further requires the key application to be enabled as hardware associated with the client device;
determine, by the processor, that a second distribution rule requires at least one other application installed on the client device;
receive, by the processor, a request for access to the resource by the client device; and
in an instance in which the client device complies with the first distribution rule and the second distribution rule, provide, by the processor, to the client device, authorization to access the resource.
9. The client device of claim 8 , wherein the request further comprises a key application identifier identifying the key application as hardware.
10. The client device of claim 8 , wherein the at least one application, when executed, further causes the processor to at least:
receive, by the processor, an authorization credential comprising a key, a token, a personal identification number, or a certificate provided by the key application.
11. The client device of claim 10 , wherein the request further comprises the authorization credential.
12. The client device of claim 10 , wherein the request further comprises the authorization credential and a user credential that is different from the authorization credential.
13. The client device of claim 12 , wherein the user credential comprises at least one of: a user name or a password.
14. The client device of claim 8 , wherein the at least one application, when executed, further causes the processor to at least:
transmit, by the processor, a request for confirmation that the client device complies with the first distribution rule.
15. A non-transitory computer-readable medium embodying a program executable in a client device, the program, when executed, causes the client device to at least:
transmit, by a processor, a first distribution rule to the client device, wherein the distribution rule requires a key application as a prerequisite to accessing a resource, wherein the first distribution rule further requires the key application to be enabled as hardware associated with a client device;
determine, by the processor, that a second distribution rule requires at least one other application installed on the client device;
receive, by the processor, a request for access to the resource by the client device; and
in an instance in which the client device complies with the first distribution rule and the second distribution rule, provide, by the processor, to the client device, authorization to access the resource.
16. The non-transitory computer-readable medium of claim 15 , wherein the request further comprises a key application identifier identifying the key application as hardware.
17. The non-transitory computer-readable medium of claim 15 , wherein the program, when executed, further causes the client device to at least:
receive, by the processor, an authorization credential comprising a key, a token, a personal identification number, or a certificate provided by the key application.
18. The non-transitory computer-readable medium of claim 17 , wherein the request further comprises the authorization credential.
19. The non-transitory computer-readable medium of claim 17 , wherein the request further comprises the authorization credential and a user credential that is different from the authorization credential.
20. The non-transitory computer-readable medium of claim 19 , wherein the user credential comprises at least one of: a user name or a password.