Connected provisioning
Disclosed are various embodiments for provisioning client devices. A configuration file previously installed on the computing device can be read. The configuration file can contain a provisioning address. Then, a user account is automatically created using a predefined username and credential stored in the configuration file. Next, an enrollment request can be sent to the provisioning address to enroll the computing device with a provisioning service using the user account. In response, an enrollment response can be received from the provisioning service. The computing device can then be configured based upon the enrollment response.
1. A system, comprising:
at least one computing device comprising a processor and a memory; and
machine-readable instructions stored in the memory that, when executed by the processor, cause the at least one computing device to at least:
receive an enrollment request from a client device, the enrollment request comprising at least one user credential and an enterprise identifier that uniquely identifies an enterprise associated with the client device with respect to another enterprise;
identify a configuration profile based at least in part on the enterprise identifier;
authenticate the client device based at least in part on the at least one user credential; and
send an enrollment response to the client device, the enrollment response comprising a provisioning package (PPKG) file.
2. The system of claim 1 , wherein the machine-readable instructions that cause the at least one computing device to identify the configuration profile based at least in part on the enterprise identifier further cause the at least one computing device to at least:
query a data store to search for an enterprise profile associated with the enterprise identifier; and
identify the configuration profile from the enterprise profile based at least in part on a device identifier of the client device.
3. The system of claim 1 , wherein the PPKG file comprises at least one of an application installer for an application to be installed on the client device or a configuration value for a configuration setting of the client device.
4. The system of claim 3 , wherein the machine-readable instructions, when executed, further cause the at least one computing device to at least:
identify the at least one of the application installer or the configuration value from the configuration profile; and
package the at least one of the application installer or the configuration value from the configuration profile into the PPKG file.
5. The system of claim 1 , wherein the PPKG file comprises instructions to implement a staging user account.
6. The system of claim 1 , wherein the machine-readable instructions that cause the at least one computing device to authenticate the client device based at least in part on the at least one user credential further cause the at least one computing device to at least compare the at least one user credential to at least one staging user credential specified in a staging user account.
7. The system of claim 1 , wherein the machine-readable instructions, when executed, further cause the at least one computing device to at least provide the enterprise identifier and a one-time authentication token to the client device.
8. A method, comprising:
receiving an enrollment request from a client device, the enrollment request comprising at least one user credential and an enterprise identifier that uniquely identifies an enterprise associated with the client device with respect to another enterprise;
identifying a configuration profile based at least in part on the enterprise identifier;
authenticating the client device based at least in part on the at least one user credential; and
sending an enrollment response to the client device, the enrollment response comprising a provisioning package (PPKG) file.
9. The method of claim 8 , wherein identifying the configuration profile based at least in part on the enterprise identifier further comprises:
querying a data store to search for an enterprise profile associated with the enterprise identifier; and
identifying the configuration profile from the enterprise profile based at least in part on a device identifier of the client device.
10. The method of claim 8 , wherein the PPKG file comprises at least one of an application installer for an application to be installed on the client device or a configuration value for a configuration setting of the client device.
11. The method of claim 10 , further comprising:
identifying the at least one of the application installer or the configuration value from the configuration profile; and
packaging the at least one of the application installer or the configuration value from the configuration profile into the PPKG file.
12. The method of claim 8 , wherein the PPKG file comprises instructions to implement a staging user account.
13. The method of claim 8 , wherein authenticating the client device based at least in part on the at least one user credential further comprises comparing the at least one user credential to at least one staging user credential specified in a staging user account.
14. The method of claim 8 , further comprising providing the enterprise identifier and a one-time authentication token to the client device.
15. A non-transitory, computer-readable medium, comprising machine-readable instructions stored in a memory of a computing device that, when executed by a processor of the computing device, cause the computing device to at least:
receive an enrollment request from a client device, the enrollment request comprising at least one user credential and an enterprise identifier that uniquely identifies an enterprise associated with the client device with respect to another enterprise;
identify a configuration profile based at least in part on the enterprise identifier;
authenticate the client device based at least in part on the at least one user credential; and
send an enrollment response to the client device, the enrollment response comprising a provisioning package (PPKG) file.
16. The non-transitory, computer-readable medium of claim 15 , wherein the machine-readable instructions that cause the computing device to identify the configuration profile based at least in part on the enterprise identifier further cause the at least one computing device to at least:
query a data store to search for an enterprise profile associated with the enterprise identifier; and
identify the configuration profile from the enterprise profile based at least in part on a device identifier of the client device.
17. The non-transitory, computer-readable medium of claim 15 , wherein the PPKG file comprises at least one of an application installer for an application to be installed on the client device or a configuration value for a configuration setting of the client device and the machine-readable instructions, when executed, further cause the computing device to at least:
identify the at least one of the application installer or the configuration value from the configuration profile; and
package the at least one of the application installer or the configuration value from the configuration profile into the PPKG file.
18. The non-transitory, computer-readable medium of claim 15 , wherein the PPKG file comprises instructions to implement a staging user account.
19. The non-transitory, computer-readable medium of claim 15 , wherein the machine-readable instructions that cause the computing device to authenticate the client device based at least in part on the at least one user credential further cause the at least one computing device to at least compare the at least one user credential to at least one staging user credential specified in a staging user account.
20. The non-transitory, computer-readable medium of claim 15 , wherein the machine-readable instructions, when executed, further cause the computing device to at least provide the enterprise identifier and a one-time authentication token to the client device.