Device connector service for device and management service integration
Disclosed are various examples of device and management service integration using a device connector service that acts as a proxy. The device connector service can receive a device communication that is relayed by a device connector client executed on an edge device. The device communication includes device connector authentication data, and a device identifier for a device. The device communication is modified into a modified device communication that includes management service authentication data, and a management unique device identifier (UDID) that is different from the device identifier. The device connector service transmits the modified device communication to a management service.
1. A system, comprising:
at least one computing device comprising at least one processor; and
at least one memory comprising machine-readable instructions, wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
receive, by a device connector service, a device communication that is relayed from a device to the device connector service by a device connector client, the device communication comprising: device connector authentication data, and a device identifier for the device;
modify, by the device connector service, the device communication into a modified device communication comprising: management service authentication data, and a management unique device identifier (UDID) that is different from the device identifier;
transmit, by the device connector service, the modified device communication to a management service;
receive, from the management service, a command notification indicating that at least one command is pending for the device, wherein the command notification is received based at least in part on at least one of a polling mechanism; and
transmit, to the device connector client, an indication that the at least one command is pending for the device, wherein the device connector client comprises a messaging broker subscription associated with the device connector service.
2. The system of claim 1 , wherein the device communication comprises a device check-in request for the device, or a device data sample from the device.
3. The system of claim 1 , wherein the device identifier comprises: a manufacturer-assigned device identifier, an enterprise-assigned device identifier, or a serial number.
4. The system of claim 1 , wherein the management UDID is an identifier generated by the device connector service based at least in part on a device identifier for the device and an enterprise identifier for an enterprise.
5. The system of claim 1 , wherein the device connector service maintains a data structure that maps device identifiers to management UDIDs for a plurality of devices that the device connector service integrates with the management service.
6. The system of claim 1 , wherein the command notification is received based at least in part the polling mechanism.
7. The system of claim 1 , wherein the device connector client is executed by an edge device or a third-party management service that is separate from the management service.
8. A non-transitory computer-readable medium comprising machine-readable instructions, wherein the instructions, when executed by at least one processor, cause at least one computing device to at least:
receive, by a device connector service, a device communication that is relayed from a device to the device connector service by a device connector client, the device communication comprising: device connector authentication data, and a device identifier for the device;
modify, by the device connector service, the device communication into a modified device communication comprising: management service authentication data, and a management unique device identifier (UDID) that is different from the device identifier;
transmit, by the device connector service, the modified device communication to a management service;
receive, from the management service, a command notification indicating that at least one command is pending for the device; and
transmit, to the device connector client, an indication that the at least one command is pending for the device, wherein the device connector client comprises a messaging broker subscription associated with the device connector service.
9. The non-transitory computer-readable medium of claim 8 , wherein the device communication comprises a device check-in request for the device, or a device data sample from the device.
10. The non-transitory computer-readable medium of claim 8 , wherein the device identifier comprises: a manufacturer-assigned device identifier, an enterprise-assigned device identifier, or a serial number.
11. The non-transitory computer-readable medium of claim 8 , wherein the management UDID is an identifier generated by the device connector service based at least in part on a device identifier for the device and an enterprise identifier for an enterprise.
12. The non-transitory computer-readable medium of claim 8 , wherein the device connector service maintains a data structure that maps device identifiers to management UDIDs for a plurality of devices that the device connector service integrates with the management service.
13. The non-transitory computer-readable medium of claim 8 , wherein the command notification is received based at least in part on at least one of a polling mechanism, or a publish-subscribe mechanism.
14. The non-transitory computer-readable medium of claim 8 , wherein the device connector client is executed by an edge device or a third-party management service that is separate from the management service.
15. A method performed by instructions executed by at least one processor of at least one computing device, the method comprising:
receiving, by a device connector service, a device communication that is relayed from a device to the device connector service by a device connector client, the device communication comprising: device connector authentication data, and a device identifier for the device;
modifying, by the device connector service, the device communication into a modified device communication comprising: management service authentication data, and a management unique device identifier (UDID) that is different from the device identifier; and
transmitting, by the device connector service, the modified device communication to a management service;
receiving, from the management service, a command notification indicating that at least one command is pending for the device; and
transmitting, to the device connector client, an indication that the at least one command is pending for the device, wherein the device connector client comprises a messaging broker subscription associated with the device connector service.
16. The method of claim 15 , wherein the device communication comprises a device check-in request for the device, or a device data sample from the device.
17. The method of claim 15 , wherein the device identifier comprises: a manufacturer-assigned device identifier, an enterprise-assigned device identifier, or a serial number.
18. The method of claim 15 , wherein the management UDID is an identifier generated by the device connector service based at least in part on a device identifier for the device and an enterprise identifier for an enterprise.
19. The method of claim 15 , wherein the device connector service maintains a data structure that maps device identifiers to management UDIDs for a plurality of devices that the device connector service integrates with the management service.
20. The method of claim 15 , wherein the command notification is received based at least in part on at least one of a polling mechanism, or a publish-subscribe mechanism.