# US 10,484,462 B2 · Dynamic registration of an application with an enterprise system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,484,462 B2 - Document ID: US10484462B2 - Status: Granted - Kind: B2 - Application number: 16/056,945 - Filed: 2018-08-07 - Published: 2018-12-27 - Granted: 2019-11-19 - Earliest claimed: 2013-05-28 - Assignees: VMware, Inc. - Applicants: VMware, Inc. - Inventors: Emily Hong Xu - Web page: https://patentgrep.com/patent/US10484462B2 ## CPC - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - G06F 21/335: {for accessing specific resources, e.g. using Kerberos tickets} - G06F 21/45: Structures or tools for the administration of authentication - H04L 63/0838: {using one-time-passwords} - H04W 12/08: Access security - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A computer-implemented method for automatically registering an application with an enterprise system is disclosed. The method accesses an application utilizable with the enterprise system. Generates an application access template for the application, including: generating information specific to the application that is able to be utilized with the enterprise system, and generating parameters specific to the application that is able to be utilized with the enterprise system. The method defines, in the application access template, a basic authorization protocol information; and utilizes the application access template for a subsequent dynamic registration of the application with the enterprise system. ## Claims ### Claim 1 A computer-implemented method for enabling dynamic registration of an application with an enterprise system, said computer-implemented method comprising: accessing an application utilizable with the enterprise system; generating an application access template for the application, the generating comprising: generating information specific to the application that is able to be utilized with the enterprise system, and generating parameters specific to the application that is able to be utilized with the enterprise system; defining, in the application access template, a basic authorization protocol information; and utilizing the application access template for a subsequent dynamic registration of the application with the enterprise system. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, further comprising: storing the application access template at an authorization server. ### Claim 3 (depends on 2) The computer-implemented method of claim 2, further comprising: generating a different application access template for each different application that is utilized with the enterprise system; and storing each different application access template at the authorization server. ### Claim 4 (depends on 2) The computer-implemented method of claim 2, further comprising: pre-approving the application for registration with the enterprise system when the application has a corresponding application access template stored at the authorization server, the pre-approving the application allowing the application to access a resource server within the enterprise system. ### Claim 5 (depends on 2) The computer-implemented method of claim 2, further comprising: denying the application for registration with the enterprise system when the application does not have a corresponding application access template stored at the authorization server, the denying stopping the application from accessing a resource server within the enterprise system. ### Claim 6 (depends on 1) The computer-implemented method of claim 1, wherein generating the application access template further comprises: generating information that facilitates in registering the application with the enterprise system; and generating information that facilitates in authorizing the application with the enterprise system. ### Claim 7 (depends on 1) The computer-implemented method of claim 1, further comprising: utilizing an open source authorization protocol that enables a third-party application to obtain access to a Hypertext Transfer Protocol (HTTP) service to define the basic authorization protocol information. ### Claim 8 (depends on 7) The computer-implemented method of claim 7, wherein the open source authorization protocol is OAuth 2.0. ### Claim 9 (depends on 1) The computer-implemented method of claim 1, wherein the application access template includes features selected from the group consisting of: an application ID, an application name, an application icon, a redirect URL, a resource access scope, and one or more attributes. ### Claim 10 (depends on 9) The computer-implemented method of claim 9, further comprising: utilizing a unique application ID for the application; utilizing the redirect URL to identify an endpoint that the application is listening on for receiving responses from the enterprise system; and utilizing the resource access scope to define a unique access scope for the application. ### Claim 11 (depends on 9) The computer-implemented method of claim 9, wherein the one or more attributes are selected from the group consisting of: whether to issue a refresh token, whether to access token time to live (TTL), and whether to refresh token TTL. ### Claim 12 (depends on 1) The computer-implemented method of claim 1, further comprising: utilizing the application access template for a subsequent authorization of the application with the enterprise system. ### Claim 13 (depends on 1) The computer-implemented method of claim 1, further comprising: utilizing the application access template for a subsequent management of the enterprise system. ### Claim 14 A computer-implemented method for enabling dynamic registration of an application on a mobile device with an enterprise system, said computer-implemented method comprising: accessing an application utilizable with the enterprise system generating an application access template for the application, the generating comprising: generating information specific to the application that is able to be utilized with the enterprise system, and generating parameters specific to the application that is able to be utilized with the enterprise system, defining, in the application access template, a basic authorization protocol information, and utilizing the application access template for a subsequent dynamic registration, authorization, and enterprise management; downloading, to the mobile device, the application from an enterprise application store, the mobile device being a non-enterprise device; automatically providing, by the mobile device, a registration request to the enterprise system; and dynamically registering the mobile device with the enterprise system when aspects of the application access template match aspects of the application. ### Claim 15 (depends on 14) The computer-implemented method of claim 14, further comprising: storing the application access template at an authorization server. ### Claim 16 (depends on 15) The computer-implemented method of claim 15, further comprising: generating a different application access template for each different application that is utilized with the enterprise system; and storing each different application access template at the authorization server. ### Claim 17 (depends on 15) The computer-implemented method of claim 15, further comprising: pre-approving the application for registration with the enterprise system when the application has a corresponding application access template stored at the authorization server, the pre-approving the application allowing the application to access a resource server within the enterprise system. ### Claim 18 (depends on 15) The computer-implemented method of claim 15, further comprising: denying the application for registration with the enterprise system when the application does not have a corresponding application access template stored at the authorization server, the denying stopping the application from accessing a resource server within the enterprise system. ### Claim 19 (depends on 14) The computer-implemented method of claim 14, wherein generating the application access template further comprises: generating information that facilitates in registering the application with the enterprise system; and generating information that facilitates in authorizing the application with the enterprise system. ### Claim 20 (depends on 14) The computer-implemented method of claim 14, further comprising: utilizing an open source authorization protocol that enables a third-party application to obtain access to a Hypertext Transfer Protocol (HTTP) service to define the basic authorization protocol information. ### Claim 21 (depends on 20) The computer-implemented method of claim 20, wherein the open source authorization protocol is OAuth 2.0. ### Claim 22 (depends on 14) The computer-implemented method of claim 14, wherein the application access template includes features selected from the group consisting of: an application ID, an application name, an application icon, a redirect URL, a resource access scope, and one or more attributes. ### Claim 23 (depends on 22) The computer-implemented method of claim 22, further comprising: utilizing a unique application ID for the application; utilizing the redirect URL to identify an endpoint that the application is listening on for receiving responses from the enterprise system; and utilizing the resource access scope to define a unique access scope for the application. ### Claim 24 (depends on 22) The computer-implemented method of claim 22, further comprising: dynamically registering the mobile device with the enterprise system when a redirect URL of the application access template matches a redirect URL of the application; and denying the registering of the mobile device with the enterprise system when the redirect URL of the application access template does not match the redirect URL of the application. ### Claim 25 (depends on 22) The computer-implemented method of claim 22, wherein the one or more attributes are selected from the group consisting of: whether to issue a refresh token, whether to access token time to live (TTL), and whether to refresh token TTL. ### Claim 26 (depends on 25) The computer-implemented method of claim 25, further comprising: dynamically registering the mobile device with the enterprise system when the attributes of the application access template match, at least in part, the attributes provided in the registration request. ### Claim 27 (depends on 14) The computer-implemented method of claim 14, wherein automatically requesting registration with the enterprise system is performed in conjunction with an installing of the application on the mobile device. ### Claim 28 (depends on 14) The computer-implemented method of claim 14, wherein automatically requesting registration with the enterprise system is performed in response to an initial execution of the application on the mobile device. ### Claim 29 (depends on 14) The computer-implemented method of claim 14, further comprising: redirecting a browser on the mobile device to a user login after the dynamic registration. ### Claim 30 (depends on 29) The computer-implemented method of claim 29, further comprising: redirecting a browser on the mobile device to an application permission page after a successful user login.