Domain name authorization method and device among multiple platforms, storage medium and computer equipment

Abstract

According to the domain name authorization method and device among the multiple platforms, the storage medium and the computer equipment provided by the invention, during domain name authorization, the server domain name of the proxy server and the authorization path of the settled application are firstly obtained, so that the authorization address of the settled application is generated in the proxy server; recording the authorization path into a positioning identifier based on the authorization address, generating an identity file according to the positioning identifier, redirecting back to the proxy server to erase a secondary path in the authorization address to obtain a root path, and reading the positioning identifier of the settled application from the identity file based on the root path, and determining a site domain name corresponding to the positioning identifier so as to forward the user request to the site domain name by using the proxy server. In general, the proxy server flexibly sets the identity identification and redirection of the settled application, the intention of the user request can be automatically identified, and the user request is correctly forwarded to the site domain name of the settled application while high efficiency and fluency of the domain name authorization process are ensured.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, device, storage medium and computer equipment for multi-platform domain name authorization. Background Art

[0002] With the rapid development of information technology, open platforms usually gather a large number of application resident parties, and these resident applications have unique resources and advantages in their respective fields. In this context, open platforms can provide users with more diversified and personalized service experiences, while resident applications can reach more potential users and provide more accurate and high-quality services based on user needs.

[0003] In order to facilitate the smooth access of the resident applications, the open platform authorizes the resident applications through the accessible whitelist management mechanism. However, due to the strict restrictions of the carrier platform's whitelist system, when trying to jump to an external link, any change in the domain name will be blocked by the system, resulting in the inability to directly redirect to the application interface of the resident application. Therefore, the open platform needs to add the domain name of the resident site to the carrier platform's domain name whitelist, resulting in a complicated domain name authorization process. Summary of the invention

[0004] The purpose of this application is to solve at least one of the above-mentioned technical defects, especially the technical defect in the prior art that the open platform needs to add the domain name of the site to be settled to the domain name whitelist of the carrier platform, resulting in a complicated domain name authorization process.

[0005] The present application provides a method for domain name authorization between multiple platforms, the method comprising:

[0006] Obtaining a server domain name of a proxy server, and determining an authorization path of a resident application to be authorized, and generating an authorization address of the resident application in the open platform in the proxy server according to the server domain name and the authorization path;

[0007] Based on the authorized address, the authorized path is recorded in the location identifier, and after the identity file of the resident application is generated according to the location identifier, it is redirected back to the proxy server to delete the secondary path in the authorized address to obtain the root path;

[0008] The location identifier of the resident application is read from the identity file based on the root path, and the site domain name of the resident application is determined based on the location identifier, so as to forward the user request to the site domain name by using the proxy server.

[0009] Optionally, determining the authorization path of the resident application to be authorized includes:

[0010] Acquire the registration information of the registered application to be authorized, and update the configuration of the proxy server according to the registration information, so as to read the authorization path of the registered application from the proxy server after the configuration update.

[0011] Optionally, generating, in the proxy server according to the server domain name and the authorization path, an authorized address of the resident application in the open platform includes:

[0012] An access address is generated with the server domain name as the root path and the authorized path as the secondary path, and a path agreement is performed in the proxy server according to the access address as the authorized address of the resident application in the open platform.

[0013] Optionally, recording the authorized path into a location identifier based on the authorized address includes:

[0014] A first access request for the authorized address is generated, and a positioning characteristic is identified for the first access request, so as to record the authorized path into a positioning identifier based on the identification result.

[0015] Optionally, the reading the location identifier of the resident application from the identity file based on the root path includes:

[0016] generating a second access request for the root path, and performing positioning characteristic identification on the second access request to obtain an identification result;

[0017] The identity file of the resident application is determined according to the recognition result, and the location identifier in the identity file is read.

[0018] Optionally, the determining the site domain name of the resident application based on the location identifier includes:

[0019] Using the proxy server to read the path of the location identifier to obtain the authorized path of the resident application;

[0020] Determine the site domain name corresponding to the authorized path based on the entry information pre-configured in the proxy server;

[0021] The entry information records the mapping relationship between the site domain name and the authorized path of the entry application.

[0022] Optionally, the using the proxy server to forward the user request to the site domain name includes:

[0023] After receiving a user request initiated by a user corresponding to the resident application, the proxy server is used to determine the site domain name corresponding to the resident application, and the user request is forwarded to the site domain name.

[0024] The present application also provides a multi-platform domain name authorization device, including:

[0025] An authorization address generation module is used to obtain a server domain name of a proxy server, determine an authorization path of a resident application to be authorized, and generate an authorization address of the resident application in the open platform in the proxy server according to the server domain name and the authorization path;

[0026] A path redirection module, configured to record the authorized path into a location identifier based on the authorized address, and after generating an identity file of the resident application according to the location identifier, redirect the path back to the proxy server to delete the secondary path in the authorized address, so as to obtain a root path;

[0027] A request forwarding module is used to read the location identifier of the resident application from the identity file based on the root path, and determine the site domain name of the resident application based on the location identifier, so as to use the proxy server to forward the user request to the site domain name.

[0028] The present application also provides a storage medium, in which computer-readable instructions are stored. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the multi-platform domain name authorization method as described in any of the above embodiments.

[0029] The present application also provides a computer device, comprising: one or more processors, and a memory;

[0030] The memory stores computer-readable instructions, and when the computer-readable instructions are executed by the one or more processors, the steps of the domain name authorization method between multiple platforms as described in any one of the above embodiments are performed.

[0031] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0032] The domain name authorization method, device, storage medium and computer equipment between multiple platforms provided by the present application can first obtain the server domain name of the proxy server and determine the authorization path of the resident application when authorizing the site domain name of the resident application, so that the authorization address of the resident application in the open platform can be generated in the proxy server according to the server domain name and the authorization path, so as to distinguish different resident applications; then the authorization path can be recorded in the positioning identifier based on the authorization address, and after the identity file of the resident application is generated according to the positioning identifier, it is redirected back to the proxy server to erase the secondary path in the authorization address to obtain the root path, and then the positioning identifier of the resident application is read from the identity file based on the root path, and the site domain name of the resident application is determined based on the positioning identifier, so as to use the proxy server to forward the user request to the site domain name, thereby avoiding the whitelist operation and realizing the automatic authorization of domain names between multiple platforms. In summary, the present application flexibly sets the identity identifier and redirection of the resident application through the proxy server, can automatically identify the intention of the user request, and correctly forward the user request to the site domain name of the resident application while ensuring the high efficiency and fluency of the domain name authorization process. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0034] Figure 1 A flowchart of a method for multi-platform domain name authorization provided in an embodiment of the present application;

[0035] Figure 2 A schematic diagram of the structure of a multi-platform domain name authorization device provided in an embodiment of the present application;

[0036] Figure 3 A schematic diagram of the internal structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0037] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0038] In order to facilitate the smooth access of the resident applications, the open platform authorizes the resident applications through the accessible whitelist management mechanism. However, due to the strict restrictions of the open platform's whitelist system, when trying to jump to an external link, any change in the domain name will be blocked by the system, resulting in the inability to directly redirect to the application interface of the resident application. Therefore, the open platform needs to add the domain name of the resident site to the open platform's domain name whitelist, resulting in a complicated domain name authorization process.

[0039] Based on this, this application proposes the following technical solutions, see below for details:

[0040] In one embodiment, Figure 1 As shown, Figure 1 A flowchart of a domain name authorization method between multiple platforms provided in an embodiment of the present application; the present application provides a domain name authorization method between multiple platforms, which specifically includes the following:

[0041] S110: Obtain the server domain name of the proxy server, determine the authorization path of the resident application to be authorized, and generate the authorization address of the resident application in the open platform in the proxy server according to the server domain name and the authorization path.

[0042] In this step, when the computer device authorizes the domain name of other resident applications in the open platform, it can first obtain the server domain name of the proxy server, and at the same time determine the authorization path of the resident application to be authorized, and then generate the authorized address of the resident application in the open platform in the proxy server according to the proxy server domain name and authorization path, so that users can access the resident application through the authorized address in the open platform.

[0043] Among them, the server domain name refers to the unique network identifier used by the proxy server, which is used to identify the entrance of the proxy server; the authorization path refers to the specific path used by the resident application for authorization in the open platform; the authorization address is the complete access address generated based on the server domain name and the authorization path. Users can use the authorization address to access the resident application across platform domain names in the carrier platform.

[0044] It is understandable that when authorizing domain names on multiple platforms, the computer device needs to first obtain the server domain name of the proxy server, and then determine the authorization path of the resident application as the key channel for authentication and authorization between the open platform and the resident application. Next, the computer device can generate the complete authorization address of the resident application in the open platform based on the server domain name and the authorization path. The authorization address is a specific URL, which usually includes the server domain name of the open platform, the authorization path of the resident application, and other related parameters, such as the application identifier, redirection URL, etc., which can be used as the entry point for users to access the resident application.

[0045] For example, when a user clicks or accesses the authorized address in the open platform, the computer device will perform necessary authentication and authorization operations on the resident application in the open platform. Once the authorization is successful, the open platform will allow the user to access and use the corresponding resident application. In this way, the computer device can ensure the security and efficiency of the domain name authorization process, so that users can successfully complete the request to access the resident application in the open platform.

[0046] Furthermore, the proxy server of the present application may adopt Nginx server, which refers to a high-performance reverse proxy and HTTP proxy server that can be used as the entry point for domain name resolution. It can route requests to the corresponding back-end server or application according to the requested domain name or path, and can also use its reverse proxy function to hide the real IP address of the back-end server to improve security. Other proxy servers with the same functions can all be used as proxy servers for domain name authorization between multiple platforms of the present application, without limitation here.

[0047] S120: Record the authorized path into the location identifier based on the authorized address, and after generating the identity file of the resident application according to the location identifier, redirect back to the proxy server to delete the secondary path in the authorized address to obtain the root path.

[0048] In this step, after obtaining the authorized address of the resident application through step S110, the computer device can record the authorized path into the location identifier based on the authorized address, and after generating the identity file of the resident application according to the location identifier, redirect back to the proxy server to erase the secondary path in the authorized address and obtain the root path. Finally, the computer device can access the application through the root path to prevent access failure caused by the presence of special secondary paths in the access path.

[0049] Among them, the location identifier refers to an identifier used to identify the authorized path of the user's request. It can track and record the path information during the user's request process as a basis for subsequent decision-making on processing the user's request. The identity file is a small text file generated by a computer device, which records the relevant data of the resident application that the user needs to access. Through the identity file, the computer device can identify the resident application requested by the user when the user accesses it subsequently, and then provide corresponding services and request forwarding.

[0050] Specifically, after obtaining the authorized address of the resident application, the computer device can record the authorization path of the authorized address into a location identifier. The location identifier serves as an association mark between the user and the resident application, and stores the relevant information of the authorized address to ensure that the computer device can accurately reference and track the authorization process during subsequent operations. Through the location identifier, the computer device can generate an identity file of the resident application to act as a bridge between the user and the resident application, thereby maintaining the consistency of the user session between different requests, avoiding repeated authorization of the resident application, and ensuring that the user can easily access the resident application in the open platform.

[0051] Furthermore, after generating the identity file, the computer device can redirect back to the proxy server so that the proxy server processes the path information in the authorization address and removes the secondary path therein, thereby simplifying the authorization address and retaining its root path, ensuring that users can bypass potential access errors caused by complex paths or special path formats, and achieve smooth access to resident applications, thereby improving the security of domain name authorization between multiple platforms and the smoothness of access, and enhancing the user experience of open platforms.

[0052] For example, in a domain name authorization scenario, the authorized address of the resident application is https: / / openplatform.example.com / auth / , where https: / / openplatform.example.com / is the root path and auth / is the secondary path. Therefore, after the computer device redirects the proxy server and removes the secondary path auth / , the root path https: / / openplatform.example.com / can be obtained.

[0053] S130: Reading the location identifier of the resident application from the identity file based on the root path, and determining the site domain name of the resident application based on the location identifier, so as to forward the user request to the site domain name by using a proxy server.

[0054] In this step, after the root path is generated through step S120, the computer device can read the location identifier of the resident application from the identity file based on the root path, and determine the site domain name of the resident application based on the location identifier, so as to automatically identify the intention of the user request, and then use the proxy server to forward the user request to the site domain name, thereby realizing the authorization of domain names and user request access between multiple platforms.

[0055] It should be noted that the site domain name of the present application refers to the unique network identifier used by the resident application, which is used to identify the entrance of the resident application.

[0056] Specifically, when processing a user request, the computer device will first read the location identifier associated with the resident application from the identity file based on the root path. Since the location identifier contains the authorization information between the user and the resident application, as well as the associated data of the resident application, by reading the location identifier, the computer device can accurately determine the resident application that the user currently wants to access. Then, the computer device can determine the site domain name of the resident application based on the location identifier. Through the site domain name, the computer device can understand the user's access intention and know which resident application the user needs to interact with.

[0057] Furthermore, in order to achieve smooth access to user requests, the computer device can use the function of the proxy server to automatically forward the user's request to the corresponding site domain name. The proxy server acts as an intermediate bridge to ensure that the user's request can be correctly routed to the resident application without the user having to manually enter different domain names or paths. Through this mechanism, while ensuring the high efficiency and smoothness of the domain name authorization process, the computer device can correctly forward the user's request to the site domain name of the resident application, realizing rapid authorization and access control across multiple platforms.

[0058] In the above embodiment, when authorizing the site domain name of the resident application, the server domain name of the proxy server can be obtained first, and the authorization path of the resident application can be determined, so that the authorization address of the resident application in the open platform can be generated in the proxy server according to the server domain name and the authorization path, so as to distinguish different resident applications; then the authorization path can be recorded in the positioning identifier based on the authorization address, and after the identity file of the resident application is generated according to the positioning identifier, it is redirected back to the proxy server to erase the secondary path in the authorization address, and obtain the root path, and then the positioning identifier of the resident application is read from the identity file based on the root path, and the site domain name of the resident application is determined based on the positioning identifier, so as to use the proxy server to forward the user request to the site domain name, thereby avoiding the whitelist operation of the carrier platform and realizing the automatic authorization of domain names between multiple platforms. In summary, the present application flexibly sets the identity identifier and redirection of the resident application through the proxy server, can automatically identify the intention of the user request, and correctly forward the user request to the site domain name of the resident application while ensuring the high efficiency and fluency of the domain name authorization process.

[0059] In one embodiment, determining the authorization path of the resident application to be authorized in step S110 may include:

[0060] S111: Acquire the registration information of the registered application to be authorized, and update the configuration of the proxy server according to the registration information, so as to read the authorization path of the registered application from the proxy server after the configuration update.

[0061] In this embodiment, when determining the entry information of the resident application, the computer device can first obtain the entry information of the resident application to be authorized, and then update the configuration of the proxy server according to the entry information. In this way, the computer device can read the authorized path of the resident application from the proxy server after the configuration update.

[0062] It is understandable that in order to ensure that the proxy server has the right to forward and process relevant requests from the open platform, the computer device can first authorize the platform domain name of the open platform in the proxy server, such as DNS settings, SSL certificate configuration, API key or token exchange. When the resident application needs to be settled in the open platform, it can provide its corresponding settlement information, including the authorization path to be used in the open platform. After receiving the settlement information of the resident application, the computer device can update the configuration of the proxy server based on the settlement information, such as modifying the configuration file of the proxy server to add a new location block to process the authorization path of the resident application. Therefore, the computer device can read the authorization path of the resident application from the proxy server after the configuration is updated, thereby realizing the automation of the path information processing configuration.

[0063] In one embodiment, generating the authorized address of the resident application in the open platform in the proxy server according to the server domain name and the authorized path in step S110 may include:

[0064] S112: Generate an access address with the server domain name as the root path and the authorized path as the secondary path, and perform path agreement in the proxy server according to the access address as the authorized address of the application in the open platform.

[0065] In this embodiment, when generating the authorized address of the resident application, the computer device can use the server domain name as the root path and the authorized path as the secondary path to generate an access address, and perform path agreement in the proxy server according to the access address as the authorized address of the resident application in the open platform, so that users can access the resident application from the open platform through the authorized address.

[0066] For example, in a domain name authorization scenario, the server domain name of the proxy server is https: / / openplatform.example.com, and the authorization path of the resident application can be auth. By combining the two, the computer device can generate a complete access address, that is, the authorization address of the resident application in the open platform, such as https: / / openplatform.example.com / auth / . This address is the entry point used by users to access the resident application and complete the authorization operation.

[0067] It is understandable that since the path agreement means that the proxy server knows which paths correspond to which resident applications, all user requests sent from the open platform can accurately find their target applications. Therefore, after generating the access address, the computer device can use this access address as the only authorized address of the resident application in the open platform and perform path agreement in the proxy server. In this process, the proxy server can act as a transit and routing role to ensure that all requests directed to the authorized address can be safely and quickly forwarded to the server where the resident application is located.

[0068] In one embodiment, recording the authorized path into the location identifier based on the authorized address in step S120 may include:

[0069] S121: Generate a first access request for an authorized address, and perform location feature identification on the first access request, so as to record the authorized path into a location identifier based on the identification result.

[0070] In this embodiment, when recording the location identifier of the resident application, the computer device can first generate a first access request for the authorized address, and then perform location feature recognition on the first access request, such as location feature recognition of the Nginx server, and then record the authorized path in the location identifier based on the recognition result.

[0071] Among them, location feature recognition refers to the mechanism of matching and processing specific rules for HTTP request paths when using Nginx server. These rules are usually defined by location instructions. This application uses location feature recognition to enable the computer device to identify whether the specific path of the request matches the location matching rule on the Nginx server, thereby providing a basis for subsequent operations, such as recording the authorized path.

[0072] It should be noted that in the Nginx server, the location directive allows the Nginx server to match rules based on the URL path and define how to handle these matched paths. Through this location feature recognition, the Nginx server can determine whether a specific path segment in the authorized address matches the established rules, thereby determining how to handle the request. If the request path matches a specific location rule, the Nginx server will route it to the corresponding service or function module.

[0073] Specifically, the first access request is the initial request issued by a user or system when trying to access a resident application, and usually contains information such as the authorized path and server domain name of the resident application. After generating the first access request, the computer device can use the location feature of the Nginx server to locate and identify the request path in the first access request, so that it can accurately identify the authorized path in the authorized address, and determine how the request should be processed or forwarded based on the specific characteristics of the authorized path. In this application, it can record the authorized path in the location identifier based on the identification result. The location identifier here can be used to store key information associated with the resident application, including the authorized path, server domain name, identity identifier, etc., to ensure that subsequent access and authorization operations can proceed smoothly.

[0074] In one embodiment, in step S130, reading the location identifier of the resident application from the identity file based on the root path may include:

[0075] S131: Generate a second access request for the root path, and perform positioning feature recognition on the second access request to obtain a recognition result.

[0076] S132: Determine the identity file of the resident application according to the recognition result, and read the location identifier in the identity file.

[0077] In this embodiment, after obtaining the root path, the computer device can first generate a second access request for the root path, and perform positioning characteristic identification on the second access request to obtain an identification result, and then determine the identity file of the resident application based on the identification result, and read the positioning identifier in the identity file, so that subsequent users can quickly and conveniently access the resident application in the open platform based on the positioning identifier.

[0078] It should be noted that the process of identifying the positioning characteristics of the second access request is consistent with the process of identifying the positioning characteristics of the first access request, and will not be described in detail here.

[0079] Specifically, the identification result of the second access request may include a specific matching method, a processing rule, and specific instructions on how to process the request. Therefore, based on the identification result, the computer device can determine the identity file of the resident application, and then read the location identifier of the resident application from the identity file. The location identifier is a unique identifier associated with the resident application. Through the location identifier, the computer device can quickly identify the resident application that the user needs to access, and quickly authorize and correctly forward its user request to the corresponding resident application through the proxy server.

[0080] In one embodiment, determining the site domain name of the application based on the location identifier in step S130 may include:

[0081] S133: Use the proxy server to read the path of the location identifier to obtain the authorized path of the installed application.

[0082] S134: Determine the site domain name corresponding to the authorized path based on the entry information pre-configured in the proxy server.

[0083] In this embodiment, when the computer device determines the site domain name of the resident application, it can first use the proxy server to read the path of the location identifier to obtain the authorized path of the resident application, and then determine the site domain name corresponding to the authorized path based on the resident information pre-configured in the proxy server, thereby realizing the forwarding of user requests.

[0084] It is understandable that the pre-configured entry information in the proxy server includes key data of the entry application, such as the authorization path, site domain name, and other related parameters; its main core is to establish a mapping relationship between the authorization path and the site domain name, that is, each authorization path corresponds to a specific site domain name. Through this mapping relationship, the computer device can ensure that the authorization path of different entry applications can be accurately resolved into the corresponding site domain name, thereby realizing the domain name authorization and request forwarding process between multiple platforms.

[0085] In one embodiment, forwarding the user request to the site domain name by using a proxy server in step S130 may include:

[0086] S135: After receiving a user request initiated by a user corresponding to the resident application, determine the site domain name corresponding to the resident application using a proxy server, and forward the user request to the site domain name.

[0087] In this embodiment, there are multiple resident applications in the open platform. Therefore, after the computer device receives a user request initiated by a user, it can parse the user request through the proxy server, and then obtain the resident application and its site domain name corresponding to the user request, and forward the user request to the site domain name. Based on this, the computer device can efficiently and accurately process the user request, ensure that the site domain name of the corresponding resident application can be quickly accessed according to the user request, and automatically complete the domain name authorization and request forwarding process between multiple platforms.

[0088] The following is a description of a multi-platform domain name authorization device provided in an embodiment of the present application. The multi-platform domain name authorization device described below and the multi-platform domain name authorization method described above can be referenced to each other.

[0089] In one embodiment, Figure 2 As shown, Figure 2A schematic diagram of the structure of a multi-platform domain name authorization device provided in an embodiment of the present application; the present application also provides a multi-platform domain name authorization device, including an authorization address generation module 210, a path redirection module 220 and a request forwarding module 230, which specifically include the following:

[0090] The authorization address generation module 210 is used to obtain the server domain name of the proxy server, determine the authorization path of the resident application to be authorized, and generate the authorization address of the resident application in the open platform in the proxy server according to the server domain name and the authorization path.

[0091] The path redirection module 220 is used to record the authorized path into the location identifier based on the authorized address, and after generating the identity file of the resident application according to the location identifier, redirect back to the proxy server to delete the secondary path in the authorized address to obtain the root path.

[0092] The request forwarding module 230 is used to read the location identifier of the resident application from the identity file based on the root path, and determine the site domain name of the resident application based on the location identifier, so as to forward the user request to the site domain name using the proxy server.

[0093] In the above embodiment, when authorizing the site domain name of the resident application, the server domain name of the proxy server can be obtained first, and the authorization path of the resident application can be determined, so that the authorization address of the resident application in the open platform can be generated in the proxy server according to the server domain name and the authorization path, so as to distinguish different resident applications; then the authorization path can be recorded in the positioning identifier based on the authorization address, and after the identity file of the resident application is generated according to the positioning identifier, it is redirected back to the proxy server to erase the secondary path in the authorization address, and obtain the root path, and then the positioning identifier of the resident application is read from the identity file based on the root path, and the site domain name of the resident application is determined based on the positioning identifier, so as to use the proxy server to forward the user request to the site domain name, thereby avoiding the whitelist operation and realizing the automatic authorization of domain names between multiple platforms. In summary, the present application flexibly sets the identity identifier and redirection of the resident application through the proxy server, can automatically identify the intention of the user request, and correctly forward the user request to the site domain name of the resident application while ensuring the high efficiency and fluency of the domain name authorization process.

[0094] In one embodiment, the authorized address generation module 210 may include:

[0095] The configuration update submodule is used to obtain the registration information of the registered application to be authorized, and update the configuration of the proxy server according to the registration information, so as to read the authorization path of the registered application from the proxy server after the configuration update.

[0096] In one embodiment, the authorized address generation module 210 may further include:

[0097] The path convention submodule is used to generate an access address with the server domain name as the root path and the authorized path as the secondary path, and perform path convention in the proxy server according to the access address as the authorized address for the application in the open platform.

[0098] In one embodiment, the path redirection module 220 may include:

[0099] The first characteristic identification submodule is used to generate a first access request for an authorized address and perform positioning characteristic identification on the first access request, so as to record the authorized path into the positioning identifier based on the identification result.

[0100] In one embodiment, the request forwarding module 230 may include:

[0101] The second characteristic identification submodule is used to generate a second access request of the root path, and perform positioning characteristic identification on the second access request to obtain an identification result.

[0102] The identification reading submodule is used to determine the identity file of the resident application according to the recognition result and read the positioning identification in the identity file.

[0103] In one embodiment, the request forwarding module 230 may further include:

[0104] The path reading submodule is used to use the proxy server to read the path of the location identifier to obtain the authorized path of the resident application.

[0105] The site domain name determination submodule is used to determine the site domain name corresponding to the authorized path based on the pre-configured entry information in the proxy server.

[0106] The entry information records the mapping relationship between the site domain name and the authorized path of the entry application.

[0107] In one embodiment, the request forwarding module 230 may further include:

[0108] The domain name authorization submodule is used to determine the site domain name corresponding to the resident application using the proxy server after receiving a user request initiated by the user corresponding to the resident application, and forward the user request to the site domain name.

[0109] In one embodiment, the present application further provides a storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the multi-platform domain name authorization method as described in any of the above embodiments.

[0110] In one embodiment, the present application also provides a computer device having computer-readable instructions stored therein. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the multi-platform domain name authorization method as described in any one of the above embodiments.

[0111] Indicatively, Figure 3 As shown, Figure 3 This is a schematic diagram of the internal structure of a computer device provided in an embodiment of the present application. The computer device 300 may be provided as a server. Figure 3 The computer device 300 includes a processing component 302, which further includes one or more processors, and a memory resource represented by a memory 301 for storing instructions executable by the processing component 302, such as an application. The application stored in the memory 301 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 302 is configured to execute instructions to perform the multi-platform domain name authorization method of any of the above embodiments.

[0112] The computer device 300 may further include a power supply component 303 configured to perform power management of the computer device 300, a wired or wireless network interface 304 configured to connect the computer device 300 to a network, and an input / output (I / O) interface 305. The computer device 300 may operate based on an operating system stored in the memory 301, such as Windows Server TM, Mac OS X TM, Unix TM, Linux TM, Free BSD TM, or the like.

[0113] Those skilled in the art will understand that Figure 3 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0114] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0115] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The various embodiments can be combined as needed, and the same or similar parts can refer to each other.

[0116] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for multi-platform domain name authorization, characterized in that: The method comprises: Obtaining a server domain name of a proxy server, and determining an authorization path of a resident application to be authorized, and generating an authorization address of the resident application in the open platform in the proxy server according to the server domain name and the authorization path; Based on the authorized address, the authorized path is recorded in the location identifier, and after the identity file of the resident application is generated according to the location identifier, it is redirected back to the proxy server to delete the secondary path in the authorized address to obtain the root path; The location identifier of the resident application is read from the identity file based on the root path, and the site domain name of the resident application is determined based on the location identifier, so as to forward the user request to the site domain name by using the proxy server.

2. The multi-platform domain name authorization method according to claim 1, characterized in that: The step of determining the authorization path of the resident application to be authorized includes: Acquire the registration information of the registered application to be authorized, and update the configuration of the proxy server according to the registration information, so as to read the authorization path of the registered application from the proxy server after the configuration update.

3. The multi-platform domain name authorization method according to claim 1, characterized in that: Generating the authorized address of the resident application in the open platform in the proxy server according to the server domain name and the authorized path includes: An access address is generated with the server domain name as the root path and the authorized path as the secondary path, and a path agreement is performed in the proxy server according to the access address as the authorized address of the resident application in the open platform.

4. The method for multi-platform domain name authorization according to claim 1, characterized in that: The step of recording the authorized path into a location identifier based on the authorized address includes: A first access request for the authorized address is generated, and a positioning characteristic is identified for the first access request, so as to record the authorized path into a positioning identifier based on the identification result.

5. The method for multi-platform domain name authorization according to claim 1, characterized in that: The reading the location identifier of the resident application from the identity file based on the root path includes: generating a second access request for the root path, and performing positioning characteristic identification on the second access request to obtain an identification result; The identity file of the resident application is determined according to the recognition result, and the location identifier in the identity file is read.

6. The method for multi-platform domain name authorization according to claim 1, characterized in that: The determining the site domain name of the resident application based on the location identifier includes: Using the proxy server to read the path of the location identifier to obtain the authorized path of the resident application; Determine the site domain name corresponding to the authorized path based on the entry information pre-configured in the proxy server; The entry information records the mapping relationship between the site domain name and the authorized path of the entry application.

7. The method for multi-platform domain name authorization according to claim 1, characterized in that: The step of forwarding the user request to the site domain name by using the proxy server includes: After receiving a user request initiated by a user corresponding to the resident application, the proxy server is used to determine the site domain name corresponding to the resident application, and the user request is forwarded to the site domain name.

8. A domain name authorization device between multiple platforms, characterized in that: include: An authorization address generation module is used to obtain a server domain name of a proxy server, determine an authorization path of a resident application to be authorized, and generate an authorization address of the resident application in the open platform in the proxy server according to the server domain name and the authorization path; A path redirection module, configured to record the authorized path into a location identifier based on the authorized address, and after generating an identity file of the resident application according to the location identifier, redirect the path back to the proxy server to delete the secondary path in the authorized address, so as to obtain a root path; The request forwarding module is used to read the location identifier of the resident application from the identity file based on the root path, and determine the site domain name of the resident application based on the location identifier, so as to use the proxy server to forward the user request to the site domain name.

9. A storage medium, characterized in that: The storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the multi-platform domain name authorization method as described in any one of claims 1 to 7.

10. A computer device, characterized in that: include: one or more processors, and memory; The memory stores computer-readable instructions, and when the computer-readable instructions are executed by the one or more processors, the steps of the domain name authorization method between multiple platforms are performed.

Images