Dynamically determining a server for enrollment with management system
Examples described herein include systems and methods for dynamically determining a server for enrollment with a management system. An example method can include receiving user input at an application executing on a user device, such as a portal application that provides access to and authentication for other applications through a catalogue of application icons. If the user input includes a first URL but that URL produces an error when used in conjunction with extensions associated with a management server, the application can automatically use extensions associated with an application-support server. The application can then retrieve a second URL from the application-support server and use it for performing enrollment steps at the management server. The enrollment steps can include authenticating the user at an identity service and determining the user's group ID for enrollment, for example.
1. A method for dynamically enrolling a user device with a management system, comprising:
receiving an enrollment request from a user device;
determining that the enrollment request includes at least one of a uniform resource locator (“URL”) and a scanned code corresponding to the URL;
attempting to contact a first server using the URL provided by the enrollment request;
receiving an error indication;
automatically modifying the URL to form a modified URL;
contacting at least one of the first server and a second server using the modified URL;
receiving a new URL from the contacted server;
providing the new URL to the user device; and
instructing the user device to use the new URL to perform enrollment with an enrollment server.
2. The method of claim 1 , wherein automatically modifying the URL comprises adding an extension to the URL, the extension being associated with at least one of the first server and the second server.
3. The method of claim 1 , wherein attempting to contact the first server using the URL comprises adding an extension associated with the first server to the URL prior to attempting to contact the first server.
4. The method of claim 1 , further comprising:
receiving an identity URL from the contacted server; and
instructing the user device to use the identity URL to authenticate with an identity service.
5. The method of claim 4 , wherein instructing the user device comprises causing the user device to display a screen associated with the identity service.
6. The method of claim 4 , further comprising:
receiving an access token from the user device indicating that the user device has authenticated with the identity service; and
validating the access token with the identity service.
7. The method of claim 6 , further comprising providing an authentication token to the user device, the authentication token authorizing a portal application on the user device to provide access to one or more additional applications through a user interface of the portal application.
8. A non-transitory, computer-readable medium containing instructions that, when executed by a hardware-based processor, perform stages for dynamically enrolling a user device with a management system, the stages comprising:
receiving an enrollment request from a user device;
determining that the enrollment request includes at least one of a uniform resource locator (“URL”) and a scanned code corresponding to the URL;
attempting to contact a first server using the URL provided by the enrollment request;
receiving an error indication;
automatically modifying the URL to form a modified URL;
contacting at least one of the first server and a second server using the modified URL;
receiving a new URL from the contacted server;
providing the new URL to the user device; and
instructing the user device to use the new URL to perform enrollment with an enrollment server.
9. The non-transitory, computer-readable medium of claim 8 , wherein automatically modifying the URL comprises adding an extension to the URL, the extension being associated with at least one of the first server and the second server.
10. The non-transitory, computer-readable medium of claim 8 , wherein attempting to contact the first server using the URL comprises adding an extension associated with the first server to the URL prior to attempting to contact the first server.
11. The non-transitory, computer-readable medium of claim 8 , the stages further comprising:
receiving an identity URL from the contacted server; and
instructing the user device to use the identity URL to authenticate with an identity service.
12. The non-transitory, computer-readable medium of claim 11 , wherein instructing the user device comprises causing the user device to display a screen associated with the identity service.
13. The non-transitory, computer-readable medium of claim 11 , the stages further comprising:
receiving an access token from the user device indicating that the user device has authenticated with the identity service; and
validating the access token with the identity service.
14. The non-transitory, computer-readable medium of claim 13 , the stages further comprising providing an authentication token to the user device, the authentication token authorizing a portal application on the user device to provide access to one or more additional applications through a user interface of the portal application.
15. A system for dynamically enrolling a user device with a management system, comprising:
a memory storage including a non-transitory, computer-readable medium comprising instructions; and
a computing device including a hardware-based processor that executes the instructions to carry out stages comprising:
receiving an enrollment request from a user device;
determining that the enrollment request includes at least one of a uniform resource locator (“URL”) and a scanned code corresponding to the URL;
attempting to contact a first server using the URL provided by the enrollment request;
receiving an error indication;
automatically modifying the URL to form a modified URL;
contacting at least one of the first server and a second server using the modified URL;
receiving a new URL from the contacted server;
providing the new URL to the user device; and
instructing the user device to use the new URL to perform enrollment with an enrollment server.
16. The system of claim 15 , wherein automatically modifying the URL comprises adding an extension to the URL, the extension being associated with at least one of the first server and the second server.
17. The system of claim 15 , wherein attempting to contact the first server using the URL comprises adding an extension associated with the first server to the URL prior to attempting to contact the first server.
18. The system of claim 15 , the stages further comprising:
receiving an identity URL from the contacted server; and
instructing the user device to use the identity URL to authenticate with an identity service.
19. The system of claim 18 , wherein instructing the user device comprises causing the user device to display a screen associated with the identity service.
20. The system of claim 18 , the stages further comprising:
receiving an access token from the user device indicating that the user device has authenticated with the identity service; and
validating the access token with the identity service.