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 determining a server for enrolling a user device with a management system, comprising:
receiving user input at a portal application executing on the user device, the user input indicating a first uniform resource locator (“URL”);
modifying the first URL by adding an extension associated with a management server to form a first modified first URL;
following the first modified first URL;
receiving an error indication;
based on receiving the error indication, automatically modifying the first URL by adding an extension associated with an application-support server to form a second modified first URL;
providing the second modified first URL to the application-support server;
receiving, from the application-support server, a second URL;
using the second URL to contact the management server; and
receiving instructions to enroll the user device through the portal application.
2. The method of claim 1 , further comprising receiving, from the application-support server, a group ID indicating an enrollment group for the user.
3. The method of claim 1 , wherein the management server uses the second URL to retrieve information regarding an identity service for authenticating the user.
4. The method of claim 3 , further comprising receiving an instruction to redirect a screen of the portal application to the identity service.
5. The method of claim 4 , further comprising:
authenticating the user at the identity service;
receiving an access token from the identity service; and
providing the access token to the management server for validation.
6. The method of claim 5 , further comprising receiving, in response to validation of the access token, an authentication token from the management server, wherein the authentication token authorizes the portal application to provide access to one or more additional applications through a user interface of the portal application.
7. The method of claim 6 , wherein the portal application provides access to the one or more additional applications through a catalogue of icons generated by the application-support server and corresponding to applications accessible by the user based on the authentication token.
8. A non-transitory, computer-readable medium containing instructions that, when executed by a hardware-based processor, performs stages for dynamically determining a server for enrolling a user device with a management system, the stages comprising:
receiving user input at a portal application executing on the user device, the user input indicating a first uniform resource locator (“URL”);
modifying the first URL by adding an extension associated with a management server to form a first modified first URL;
following the first modified first URL;
receiving an error indication;
based on receiving the error indication, automatically modifying the first URL by adding an extension associated with an application-support server to form a second modified first URL;
providing the second modified first URL to the application-support server;
receiving, from the application-support server, a second URL;
using the second URL to contact the management server; and
receiving instructions to enroll the user device through the portal application.
9. The non-transitory, computer-readable medium of claim 8 , the stages further comprising receiving, from the application-support server, a group ID indicating an enrollment group for the user.
10. The non-transitory, computer-readable medium of claim 8 , wherein the management server uses the second URL to retrieve information regarding an identity service for authenticating the user.
11. The non-transitory, computer-readable medium of claim 10 , the stages further comprising receiving an instruction to redirect a screen of the portal application to the identity service.
12. The non-transitory, computer-readable medium of claim 11 , the stages further comprising:
authenticating the user at the identity service;
receiving an access token from the identity service; and
providing the access token to the management server for validation.
13. The non-transitory, computer-readable medium of claim 12 , the stages further comprising receiving, in response to validation of the access token, an authentication token from the management server, wherein the authentication token authorizes the portal application to provide access to one or more additional applications through a user interface of the portal application.
14. The non-transitory, computer-readable medium of claim 13 , wherein the portal application provides access to the one or more additional applications through a catalogue of icons generated by the application-support server and corresponding to applications accessible by the user based on the authentication token.
15. A system for dynamically determining a server for 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 user input at a portal application executing on the user device, the user input indicating a first uniform resource locator (“URL”);
modifying the first URL by adding an extension associated with a management server to form a first modified first URL;
following the first modified first URL;
receiving an error indication;
based on receiving the error indication, automatically modifying the first URL by adding an extension associated with an application-support server to form a second modified first URL;
providing the second modified first URL to the application-support server;
receiving, from the application-support server, a second URL;
using the second URL to contact the management server; and
receiving instructions to enroll the user device through the portal application.
16. The system of claim 15 , the stages further comprising receiving, from the application-support server, a group ID indicating an enrollment group for the user.
17. The system of claim 15 , wherein the management server uses the second URL to retrieve information regarding an identity service for authenticating the user.
18. The system of claim 17 , the stages further comprising receiving an instruction to redirect a screen of the portal application to the identity service.
19. The system of claim 18 , the stages further comprising:
authenticating the user at the identity service;
receiving an access token from the identity service; and
providing the access token to the management server for validation.
20. The system of claim 19 , the stages further comprising receiving, in response to validation of the access token, an authentication token from the management server, wherein the authentication token authorizes the portal application to provide access to one or more additional applications through a user interface of the portal application.