I/WE CLAIM:
1. One or more computer readable media having instructions thereon
that, in response to execution by one or more processing devices of an
apparatus, cause the apparatus to:
receive, via a stateless protocol message, a pairing request from an application, wherein the pairing request specifies a hardware resource of a computing device, remote from the apparatus, with which the application requests a pairing;
provide, via a stateless protocol message, request data to the computing device, wherein the request data includes an identifier of the application and an identifier of the hardware resource to the computing device;
receive, via a stateless protocol message, pairing approval from the computing device, wherein the pairing approval is generated by the computing device based on at least some of the request data; and
in response to receipt of the pairing approval, generate a pairing token for provision to the application, wherein the pairing token is to be provided to the computing device by the application, via a stateless protocol message, to pair the application with the hardware resource.
2. The one or more computer readable media of claim 1, wherein the
stateless protocol messages are Representational State Transfer (REST) calls.
3. The one or more computer readable media of claim 1, further having
instructions thereon that, when executed by the one or more processing devices
of the apparatus, cause the apparatus to:
generate a temporary token for provision to the application, in response to receipt of the pairing request, wherein the temporary token is to be provided to the computing device by the application, via a stateless protocol message, to trigger a request from the computing device to the apparatus, via a stateless protocol message including the temporary token, for the request data.
4. The one or more computer readable media of claim 3, further having
instructions thereon that, when executed by the one or more processing devices
of the apparatus, cause the apparatus to:
in response to a stateless protocol message including the temporary token from the application and receipt of the pairing approval, provide the pairing token to the application via a stateless protocol message.
5. The one or more computer readable media of claim 1, wherein the
request data includes an Internet Protocol (IP) address of the application.
6. The one or more computer readable media of claim 5, further having
instructions thereon that, when executed by the one or more processing devices
of the apparatus, cause the apparatus to:
provide, via a stateless protocol message to the computing device, an IP address of the computing device.
7. One or more computer readable media having instructions thereon
that, in response to execution by one or more processing devices of an
apparatus, cause the apparatus to:
receive, via a stateless protocol message, request data from a computing device, wherein the request data includes an identifier of a hardware resource of the apparatus and an identifier of an application that has provided a pairing request for pairing with the hardware resource;
in response to receipt of the request data, provide, via a stateless protocol message, an approval of the pairing request or a denial of the pairing request to the computing device;
receive, via a stateless protocol message, an access request for access to the hardware resource from the application, wherein the access request includes a pairing token that was generated and provided to the application by the computing device in response to receipt by the computing device of an approval of the pairing request;
validate or invalidate the pairing token; and
provide, via a stateless protocol message, data from the hardware resource for provision to the application in response to validation of the pairing token.
8. The one or more computer readable media of claim 7, wherein the
application executes on the apparatus.
9. The one or more computer readable media of claim 7, wherein the
access request is received from the computing device, and wherein the
application executes on a second computing device different from the computing
device.
10. The one or more computer readable media of claim 9, wherein the
access request includes an Internet Protocol (IP) address of the application, and
wherein validate or invalidate the pairing token comprises determine that the IP
address of the application matches or does not match, respectively, an IP
address of the apparatus.
11. The one or more computer readable media of claim 7, wherein the
access request is received from a third computing device different from the
computing device and different from a second computing device on which the
application executes.
12. The one or more computer readable media of claim 7, wherein
validate or invalidate the pairing token comprises determine that the pairing token
does or does not identify the apparatus.
13. An apparatus for regulating pairing with hardware resources,
comprising:
pairing request receipt logic to receive, via a stateless protocol message, a pairing request from an application, wherein the pairing request specifies a hardware resource of a computing device, remote from the apparatus, with which the application requests a pairing;
intermediary logic, coupled with the pairing request receipt logic, to:
provide, via a stateless protocol message, request data to the computing device, wherein the request data includes an identifier of the application and an identifier of the hardware resource to the computing device, and
receive, via a stateless protocol message, pairing approval from the computing device, wherein the pairing approval is generated by the computing device based on at least some of the request data; and
token generation logic, coupled with the intermediary logic, to, in response to receipt of the pairing approval, generate a pairing token for provision to the application, wherein the pairing token is to be provided to the computing device by the application, via a stateless protocol message, to pair the application with the hardware resource.
14. The apparatus of claim 13, wherein the application executes on the
computing device.
15. The apparatus of claim 13, wherein the token generation logic is
coupled to the pairing request receipt logic, and is further to generate a
temporary token for provision to the application, in response to receipt of the
pairing request, wherein the temporary token is to be provided to the computing
device by the application, via a stateless protocol message, to trigger a request
from the computing device to the apparatus, via a stateless protocol message
including the temporary token, for the request data.
16. The apparatus of claim 15, wherein the token generation logic is
further to, in response to a stateless protocol message including the temporary
token from the application and receipt of the pairing approval, provide the pairing
token to the application via a stateless protocol message.
17. The apparatus of claim 13, wherein the request data includes an
Internet Protocol (IP) address of the application.
18. The apparatus of claim 17, wherein the intermediary logic is further to
provide, via a stateless protocol message to the computing device, an IP address
of the computing device.
19. An apparatus for regulating access to hardware resources,
comprising:
pairing request evaluation logic to:
receive, via a stateless protocol message, request data from a computing device, wherein the request data includes an identifier of a hardware resource of the apparatus and an identifier of an application that has provided a pairing request for pairing with the hardware resource, and
in response to receipt of the request data, provide, via a stateless protocol message, an approval of the pairing request or a denial of the pairing request to the computing device; token evaluation logic to:
receive, via a stateless protocol message, an access request for access to the hardware resource from the application, wherein the access request includes a pairing token that was generated and provided to the application by the computing device in response to receipt by the computing device of an approval of the pairing request provided by the pairing request evaluation logic, and
validate or invalidate the pairing token; and resource management logic, coupled with the token evaluation logic, to provide, via a stateless protocol message, data from the hardware resource for provision to the application in response to validation of the pairing token.
20. The apparatus of claim 19, wherein the application executes on the
apparatus.
21. The apparatus of claim 19, wherein the access request is received
from the computing device, and wherein the application executes on a second
computing device different from the computing device.
22. The apparatus of claim 21, wherein the access request includes an
Internet Protocol (IP) address of the application, and wherein validate or
invalidate the pairing token comprises determine that the IP address of the
application matches or does not match, respectively, an IP address of the
apparatus.
23. The apparatus of claim 19, wherein the access request is received
from a third computing device different from the computing device and different
from a second computing device on which the application executes.
24. The apparatus of claim 19, wherein the pairing request evaluation
logic is included in a kernel application, a network interface card, or a
manageability engine.
25. The apparatus of claim 19, wherein the stateless protocol messages
are Representational State Transfer (REST) calls.