Multi-tenant secondary domain name management method and device, electronic equipment and storage medium

Abstract

The invention discloses a multi-tenant secondary domain name management method and device, electronic equipment and a storage medium, and belongs to the technical field of the Internet, and the method comprises the steps: obtaining tenant creation information in response to newly-added tenant creation information in a monitored information queue; analyzing the tenant creation information, and obtaining secondary domain name data and website homepage design data corresponding to the tenant creation information; storing the second-level domain name data and the website homepage design data into a storage database; wherein the second-level domain name data is obtained by calling a cloud API interface to add second-level domain name resolution by the back-end server; the website homepage design data is determined and obtained by the back-end server according to the tenant creation request. According to the method, the second-level domain name applied by the tenant is dynamically added by calling the cloud API interface, manual adding operation of software, namely a service platform administrator, is not needed, full-automatic adding of the second-level domain name can be achieved, and good user experience is provided for a user.

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a multi-tenant secondary domain name management method, device, electronic device and storage medium. Background Art

[0002] Currently, with the development and application of Software as a Service, or SaaS, more and more enterprises and individuals are adopting this service of accessing software through the Internet without having to install and run applications locally.

[0003] In the related technology, users need to apply to the cloud service provider to create tenant account information. However, in actual applications, it is found that the DNS administrator is currently required to add the secondary domain name applied by the tenant to the domain name resolution. Each time a new tenant is created, the DNS administrator needs to perform an addition operation, which is cumbersome and requires high manpower and time costs.

[0004] In summary, the technical problems existing in the relevant technologies need to be improved. Summary of the invention

[0005] The embodiments of the present application provide a multi-tenant secondary domain name management method, device, electronic device and storage medium, which can realize fully automated addition of secondary domain names and provide users with a good user experience.

[0006] On the one hand, an embodiment of the present application provides a multi-tenant secondary domain name management method, comprising the following steps:

[0007] In response to newly added tenant creation information in the monitored information queue, obtain the tenant creation information;

[0008] Parsing the tenant creation information, and acquiring secondary domain name data and website homepage design data corresponding to the tenant creation information;

[0009] The secondary domain name data and the website homepage design data are stored in a storage database;

[0010] Among them, the tenant creation information is created and sent to the information queue by the back-end server in response to the tenant creation request; the tenant creation information includes the second-level domain name data and the website homepage design data; the second-level domain name data is obtained by the back-end server calling the cloud API interface to add the second-level domain name resolution; the website homepage design data is determined by the back-end server according to the tenant creation request.

[0011] Optionally, after storing the secondary domain name data and the website homepage design data in a storage database, the method further includes:

[0012] In response to the network connection access request, obtaining the network connection access request;

[0013] Parsing the network connection access request to obtain a target secondary domain name;

[0014] Retrieving the secondary domain name data stored in the storage database;

[0015] When the second-level domain name data stored in the storage database matches the second-level domain name data that is consistent with the target second-level domain name, the website homepage design data corresponding to the second-level domain name data is read, and the tenant identity corresponding to the network connection access request is determined.

[0016] Optionally, the method further comprises:

[0017] When the second-level domain name data stored in the storage database does not match the second-level domain name data that is consistent with the target second-level domain name, network connection access request rejection information is returned.

[0018] Optionally, when the second-level domain name data stored in the storage database matches the second-level domain name data that is consistent with the target second-level domain name, after reading the website homepage design data corresponding to the second-level domain name data and determining the tenant identity corresponding to the network connection access request, it also includes:

[0019] Receive a login request initiated by a tenant, and add the tenant identity identifier to a header field of the login request;

[0020] Sending a login request with a header field containing the tenant identity to the backend server.

[0021] Optionally, storing the secondary domain name data and the website homepage design data in a storage database includes:

[0022] Add the secondary domain name data to the allowed access path list;

[0023] Add the website homepage design data to the reverse proxy webpage directory.

[0024] Optionally, the method further comprises:

[0025] In response to the triggered tenant deregistration request, the secondary domain name data and website homepage design data corresponding to the tenant deregistration request are deleted from the storage database.

[0026] Optionally, the method further comprises:

[0027] In response to the triggered tenant update request, the secondary domain name data and website homepage design data corresponding to the tenant update request are updated from the storage database.

[0028] On the other hand, an embodiment of the present application provides a multi-tenant secondary domain name management device, the device comprising:

[0029] An information monitoring module, configured to obtain the tenant creation information in response to the newly added tenant creation information in the monitored information queue;

[0030] A data parsing module, used to parse the tenant creation information, and obtain the secondary domain name data and website homepage design data corresponding to the tenant creation information;

[0031] A data storage module, used to store the secondary domain name data and the website homepage design data in a storage database;

[0032] Among them, the tenant creation information is created and sent to the information queue by the back-end server in response to the tenant creation request; the tenant creation information includes the second-level domain name data and the website homepage design data; the second-level domain name data is obtained by the back-end server calling the cloud API interface to add the second-level domain name resolution; the website homepage design data is determined by the back-end server according to the tenant creation request.

[0033] On the other hand, an embodiment of the present application provides an electronic device, which includes a memory and a processor, the memory stores a computer program, and the processor implements the above-mentioned multi-tenant secondary domain name management method when executing the computer program.

[0034] On the other hand, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned multi-tenant secondary domain name management method is implemented.

[0035] The embodiment of the present application dynamically adds the second-level domain name applied for by the tenant by calling the cloud API interface, without the need for manual addition operations by the software as a service platform administrator, and can achieve fully automated addition of the second-level domain name, providing users with a good user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 It is a schematic diagram of an implementation environment of a multi-tenant secondary domain name management method provided in an embodiment of the present application;

[0037] Figure 2 It is a flowchart of a multi-tenant secondary domain name management method provided in an embodiment of the present application;

[0038] Figure 3It is a flowchart of responding to a network connection access request provided by an embodiment of the present application;

[0039] Figure 4 This is a schematic diagram of a tenant login authentication process provided by an embodiment of the present application;

[0040] Figure 5 It is a structural diagram of a multi-tenant secondary domain name management device provided in an embodiment of the present application;

[0041] Figure 6 It is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is further described in detail below in conjunction with the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the embodiments of the present application. They are only examples of devices and methods consistent with some aspects of the embodiments of the present application as detailed in the attached claims.

[0043] It is understood that the terms "first", "second", etc. used in this application can be used to describe various concepts in this article, but unless otherwise specified, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another concept. For example, without departing from the scope of the embodiment of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the words "if" and "if" as used herein can be interpreted as "at the time of" or "when" or "in response to determination".

[0044] The terms "at least one", "multiple", "each", "any", etc. used in this application, at least one includes one, two or more, multiple includes two or more, each refers to each of the corresponding multiple, and any refers to any one of the multiple.

[0045] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0046] Currently, with the development and application of Software as a Service, or SaaS, more and more enterprises and individuals are adopting this service of accessing software through the Internet without having to install and run applications locally.

[0047] In the related technology, users need to apply to the cloud service provider to create tenant account information. However, in actual applications, it is found that the DNS administrator is currently required to add the second-level domain name applied by the tenant to the domain name resolution. Each time a new tenant is created, the DNS administrator needs to perform an addition operation, which is cumbersome and requires high manpower and time costs.

[0048] In view of this, the embodiments of the present application provide a multi-tenant second-level domain name management method, device, electronic device and storage medium, which dynamically add the second-level domain name applied for by the tenant by calling the cloud API interface, without the need for manual addition operations by the software as a service platform administrator, and can achieve fully automated addition of second-level domain names, providing users with a good user experience.

[0049] It should be noted that in each specific implementation of the present application, when it comes to the need to perform relevant processing based on data related to user identity or characteristics such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first, and the collection, use, and processing of these data will comply with relevant laws, regulations, and standards. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the embodiment of the present application will be obtained.

[0050] The specific implementation of the embodiment of the present application is described in detail below in conjunction with the accompanying drawings. First, a multi-tenant secondary domain name management method provided in the embodiment of the present application is described in conjunction with the accompanying drawings.

[0051] Please refer to Figure 1 , Figure 1 The schematic diagram of the implementation environment of a multi-tenant secondary domain name management method provided by the embodiment of the present application is shown. In the implementation environment, the main hardware and software entities involved include a processor 110 and a backend server 120.

[0052] Specifically, the processor 110 may be installed with a related multi-tenant secondary domain name management control program, and the backend server 120 is the background server of the control program. The processor 110 and the backend server 120 are connected in communication. The multi-tenant secondary domain name management method provided in the embodiment of the present application may be executed on the processor 110 side.

[0053] The back-end server 120 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), as well as big data and artificial intelligence platforms.

[0054] In addition, the backend server 120 can also be a node server in the blockchain network.

[0055] The processor 110 and the back-end server 120 may establish a communication connection through a wireless network. The wireless network uses standard communication technology and / or protocols, and the network may be set to the Internet, or any other network, such as but not limited to a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a mobile, or any combination of a wireless network, a private network, or a virtual private network. Moreover, the above-mentioned hardware and software entities may use the same communication connection mode or different communication connection modes, and this application does not impose any specific restrictions on this.

[0056] Of course, it is understandable that Figure 1 The implementation environment in the embodiment of the present application is only some optional application scenarios of the multi-tenant secondary domain name management method provided in the embodiment of the present application, and the actual application is not fixed. Figure 1 The software and hardware environment shown is not specifically limited in this application.

[0057] like Figure 2 As shown, Figure 2 It is a flow chart of a multi-tenant secondary domain name management method provided in an embodiment of the present application, which specifically includes but is not limited to steps S100 to S300.

[0058] Step S100: In response to the tenant creation information newly added in the monitored information queue, the tenant creation information is obtained.

[0059] Among them, the tenant creation information is created and sent to the information queue by the back-end server in response to the tenant creation request; the tenant creation information includes the second-level domain name data and the website homepage design data; the second-level domain name data is obtained by the back-end server calling the cloud API interface to add the second-level domain name resolution; the website homepage design data is determined by the back-end server according to the tenant creation request.

[0060] In an embodiment of the present application, the execution entity may be a reverse proxy server in a SaaS (Software as a Service) platform. The reverse proxy server is an intermediary server located between a client and a back-end server. Its main function is to receive requests from the client and forward them to the corresponding back-end server, thereby enhancing system security and preventing the back-end server from being directly attacked.

[0061] It is understandable that when any user sends a request to create a tenant to the SaaS platform, it is understandable that the user can be either a corporate unit or an individual user. The back-end server of the SaaS platform can respond to the tenant creation request, create tenant creation information and send it to the information queue.

[0062] Optionally, when a user sends a request to the SaaS platform to create a tenant, the user can customize the tenant's second-level domain name, such as companyA, and can also customize the appearance design of the tenant's website homepage login interface. Therefore, when the back-end server responds to the tenant creation request, it can read the tenant's customized second-level domain name and the customized website homepage login interface design to obtain the website homepage design data, and can also verify whether the tenant's customized second-level domain name meets the conditions, such as whether it has been registered and occupied, and whether it contains illegal characters.

[0063] Furthermore, the backend server can also call the cloud vendor API interface to dynamically add the custom second-level domain name CNAME proposed by the tenant to obtain the second-level domain name data through second-level domain name resolution, where the CNAME (Canonical Name) record is a DNS record used to map one domain name to another domain name without the need for the administrator to add it manually. Furthermore, the tenant creation information containing the second-level domain name data corresponding to the second-level domain name data and the website homepage design data is sent to the information queue, and the reverse proxy server can quickly obtain the newly added tenant creation information in the information queue by monitoring the information queue.

[0064] It is understandable that the multi-tenant secondary domain name management method provided by this application can allow tenants to customize the secondary domain name. For example, they can use the secondary domain name "CompanyA.saas.com" to access. Compared with the login method of www.saas.com / companyA, it is simpler and easier for users to accept. It can not only reduce the characters required to be entered, reduce the user's operating costs, but also prevent users from entering incorrect characters. In addition, tenants can also be allowed to customize the appearance design of the login interface, thereby greatly improving the user experience.

[0065] Step S200: parse the tenant creation information, and obtain the secondary domain name data and website homepage design data corresponding to the tenant creation information.

[0066] In an embodiment of the present application, after the reverse proxy server obtains the newly added tenant creation information in the information queue, it can parse the tenant creation information and read the secondary domain name data and website homepage design data corresponding to the tenant creation information.

[0067] Optionally, the website homepage design data may include information such as page layout, content, and style.

[0068] Step S300: storing the secondary domain name data and the website homepage design data in a storage database.

[0069] In an embodiment of the present application, when the reverse proxy server parses and obtains the second-level domain name data and the website homepage design data from the tenant creation information, the second-level domain name data and the website homepage design data can be associated and stored in a storage database, thereby becoming the exclusive resources of the tenant.

[0070] It is understandable that by storing each tenant's exclusive second-level domain name data and website homepage design data, the SaaS platform can enable each tenant to have its own data, configuration and settings when providing software services to multiple tenants. In addition, the multi-tenant second-level domain name management method provided in the embodiment of the present application can automatically respond to tenant creation requests made by tenants, and dynamically add CNAME second-level domain name resolution by calling the cloud vendor API interface, without the need for additional manual operations, which can reduce manpower and time costs.

[0071] Specifically, as an optional implementation, storing the secondary domain name data and the website homepage design data in a storage database includes:

[0072] Add the secondary domain name data to the allowed access path list;

[0073] Add the website homepage design data to the reverse proxy webpage directory.

[0074] In an embodiment of the present application, the reverse proxy server can add the second-level domain name data to the allowed access path list, thereby limiting access to only the second-level domain names of activated tenants, and any other unactivated second-level domain names will not be resolved.

[0075] Furthermore, adding the website homepage design data to the reverse proxy web page directory can help the reverse proxy server quickly read the corresponding website homepage design data based on the relevant tenant information when receiving a tenant login request, and provide it to the browser to display the tenant's customized website homepage.

[0076] Specifically, as an optional implementation, please refer to Figure 3 , Figure 3 is a flow chart of responding to a network connection access request provided by an embodiment of the present application. After storing the secondary domain name data and the website homepage design data in a storage database, the method further includes:

[0077] In response to the network connection access request, obtaining the network connection access request;

[0078] Parsing the network connection access request to obtain a target secondary domain name;

[0079] Retrieving the secondary domain name data stored in the storage database;

[0080] When the second-level domain name data stored in the storage database matches the second-level domain name data that is consistent with the target second-level domain name, the website homepage design data corresponding to the second-level domain name data is read, and the tenant identity corresponding to the network connection access request is determined.

[0081] In an embodiment of the present application, when a tenant accesses the SaaS platform through a second-level domain name, for example, CompanyA tenant accesses it through a custom second-level domain name CompanyA.saas.com, the reverse proxy server can respond to the network connection access request (i.e., URL access request), obtain the URL access request, and parse the URL access request, and resolve the target second-level domain name CompanyA from the accessed URL path.

[0082] Furthermore, the second-level domain name data stored in the current storage database is retrieved to confirm whether there is data corresponding to the target second-level domain name.

[0083] It is understandable that when the second-level domain name data stored in the storage database matches the target second-level domain name, the website homepage design data corresponding to the second-level domain name data is read, and the tenant identity corresponding to the network connection access request is determined.

[0084] Among them, the read website homepage design data can enable the browser to display the tenant's customized website homepage, and determine the tenant identity X-TENANT-ID corresponding to the network connection access request, and can further add the X-TENANT-ID field in the HTTP response header to identify the tenant's identity ID.

[0085] Specifically, as an optional implementation, please refer to Figure 3 , the method further comprises:

[0086] When the second-level domain name data stored in the storage database does not match the second-level domain name data that is consistent with the target second-level domain name, network connection access request rejection information is returned.

[0087] In an embodiment of the present application, when it is confirmed after searching through the entire storage database that there is no second-level domain name data stored in the storage database that matches the target second-level domain name, it indicates that the target second-level domain name has not been registered and is not allowed to be accessed. It can further return information rejecting the network connection access request, such as returning a 404 not found status code, or returning to the homepage of the SaaS platform to inform the user who has made the network connection access request that the current access has been denied.

[0088] Therefore, the multi-tenant second-level domain name management method provided in this application can limit access to only the second-level domain names of activated tenants, and any other unactivated second-level domain names will not be resolved, which can better ensure the service security and stability of multiple tenants.

[0089] Specifically, as an optional implementation, please refer to Figure 4 , Figure 4 It is a flow chart of a tenant login authentication provided by an embodiment of the present application, when the second-level domain name data stored in the storage database matches the second-level domain name data consistent with the target second-level domain name, the website homepage design data corresponding to the second-level domain name data is read, and the tenant identity corresponding to the network connection access request is determined, and it also includes:

[0090] Receive a login request initiated by a tenant, and add the tenant identity identifier to a header field of the login request;

[0091] Sending a login request with a header field containing the tenant identity to the backend server.

[0092] In an embodiment of the present application, after confirming that consistent second-level domain name data is retrieved in the current database and the relevant website homepage design data is read, the browser can display the tenant's customized homepage and wait for the tenant to log in for verification.

[0093] When the tenant has entered the account secret information, the reverse proxy server receives the login request (i.e., HTTP Request) initiated by the tenant, and then adds the tenant identity X-TENANT-ID corresponding to the network connection access request to the header field of the login request, and sends the login request with the tenant identity header field to the back-end server. The API gateway of the back-end server parses the tenant identity in the login request, and then the back-end server can perform login information authentication based on the account secret information and tenant identity entered by the tenant. If the account password meets the requirements, exclusive resource access can be opened to provide software services to the tenant. If the account password is incorrect, the tenant access can be denied, and the tenant can be required to re-enter the account password information.

[0094] Specifically, as an optional implementation, the method further includes:

[0095] In response to the triggered tenant deregistration request, the secondary domain name data and website homepage design data corresponding to the tenant deregistration request are deleted from the storage database.

[0096] In an embodiment of the present application, after the reverse proxy server responds to the triggered tenant logout request, when it needs to receive and process the tenant logout request, it can read the tenant identity identifier corresponding to the tenant logout request, and can verify the legitimacy of the tenant logout request before performing the data deletion operation, ensuring that the tenant logout request comes from a valid user and has the authority to perform the logout operation.

[0097] Furthermore, according to the tenant identity, relevant second-level domain name data and website homepage design data are retrieved from the storage database to confirm the existence of the second-level domain name.

[0098] It is understandable that when performing data deletion operations, it is necessary to ensure that the deletion operations of two types of data (secondary domain name data and website homepage design data) are performed in one transaction to ensure data consistency. If any data deletion fails, the operation should be rolled back to ensure data integrity.

[0099] In actual applications, the reverse proxy server can also send the relevant tenant cancellation request to the back-end server, so that the back-end server can call the cloud API interface to delete the secondary domain name resolution operation, and after completing the deletion of the secondary domain name resolution operation, the processing result of the deletion operation can be returned to the reverse proxy server.

[0100] Finally, the result of the logout operation may also be returned to the user, so that the user can confirm that the operation of the tenant logout request has been completed.

[0101] Specifically, as an optional implementation, the method further includes:

[0102] The method further comprises:

[0103] In response to the triggered tenant update request, the secondary domain name data and website homepage design data corresponding to the tenant update request are updated from the storage database.

[0104] In an embodiment of the present application, after the reverse proxy server responds to the triggered tenant update request, when it needs to receive and process the tenant update request, it can read the tenant identity identifier corresponding to the tenant update request, and can verify the legitimacy of the tenant update request before performing the data update operation, ensuring that the tenant update request comes from a valid user and has the authority to perform the update operation.

[0105] Furthermore, according to the tenant identity, relevant second-level domain name data and website homepage design data are retrieved from the storage database to confirm the existence of the second-level domain name.

[0106] In actual applications, the reverse proxy server can also send relevant tenant update requests to the back-end server, so that the back-end server can call the cloud API interface to update the secondary domain name resolution operation, and after completing the update of the secondary domain name resolution operation, the processing result of the update operation can be returned to the reverse proxy server.

[0107] Finally, the result of the update operation may also be returned to the user, so that the user can confirm that the tenant update request operation has been completed.

[0108] Next, in conjunction with a specific application implementation process, the multi-tenant secondary domain name management method provided in the present invention is described and explained in detail:

[0109] In an embodiment of the present application, a multi-tenant secondary domain name management method is provided. The method can be applied to the management scenario of multi-tenant secondary domain names of a SaaS platform. By calling a cloud API interface to dynamically add secondary domain names applied for by tenants, there is no need for manual addition operations by the administrator of the software as a service platform. The secondary domain names can be added fully automatically, providing users with a good user experience.

[0110] Specifically, when any user sends a request to the SaaS platform to create a tenant, the tenant's second-level domain name can be customized, and the login interface design of the tenant's website homepage can also be customized. Therefore, when the back-end server responds to the tenant's creation request, it can read the customized second-level domain name and customized website homepage login interface design proposed by the tenant to obtain the website homepage design data, and can also verify whether the customized second-level domain name proposed by the tenant meets the requirements.

[0111] Furthermore, the backend server can also call the cloud vendor API interface to dynamically add the custom second-level domain name CNAME proposed by the tenant to obtain the second-level domain name data through second-level domain name resolution without the need for manual addition by the administrator.

[0112] Furthermore, the tenant creation information including the second-level domain name data and the website homepage design data corresponding to the second-level domain name data is sent to the information queue. The reverse proxy server can quickly obtain the newly added tenant creation information in the information queue by monitoring the information queue, and can further parse the tenant creation information to read the second-level domain name data and the website homepage design data corresponding to the tenant creation information.

[0113] Furthermore, when the reverse proxy server parses and obtains the second-level domain name data and the website homepage design data from the tenant creation information, it can associate the second-level domain name data and the website homepage design data, add the second-level domain name data to the allowed access path list, and add the website homepage design data to the reverse proxy web page directory, thereby becoming an exclusive resource for the tenant.

[0114] It is understandable that when a tenant accesses the SaaS platform through a second-level domain name, the reverse proxy server can respond to the URL access request and parse the URL access request to resolve the target second-level domain name from the accessed URL path, retrieve the second-level domain name data stored in the current storage database, and confirm whether there is data corresponding to the target second-level domain name.

[0115] When the second-level domain name data stored in the storage database matches the target second-level domain name, the website homepage design data corresponding to the second-level domain name data is read, and the tenant identity X-TENANT-ID corresponding to the network connection access request is determined, and the X-TENANT-ID field can be added to the header of the HTTP response to identify the tenant's identity ID.

[0116] When the search traverses the entire storage database and confirms that there is no second-level domain name data stored in the storage database that matches the target second-level domain name, it indicates that the target second-level domain name has not been opened for registration and is not allowed to be accessed. It can further return information rejecting the network connection access request, such as returning a 404 not found status code, or returning to the homepage of the SaaS platform to inform the user who has made the network connection access request that the current access has been denied.

[0117] Finally, when the tenant has finished entering the account secret information, the reverse proxy server receives the login request (i.e., HTTP Request) initiated by the tenant, and then adds the tenant identity X-TENANT-ID corresponding to the network connection access request to the header field of the login request, and sends the login request with the tenant identity header field to the back-end server. The API gateway of the back-end server parses the tenant identity in the login request, and then the back-end server can perform login information authentication based on the account secret information and tenant identity entered by the tenant. If the account password meets the requirements, exclusive resource access can be opened to provide software services to the tenant. If the account password is incorrect, the tenant access can be denied, and the tenant can be required to re-enter the account password information.

[0118] See also Figure 5 , Figure 5 : is a structural diagram of a multi-tenant secondary domain name management device provided in an embodiment of the present application. The embodiment of the present application also provides a multi-tenant secondary domain name management device, which includes:

[0119] The information monitoring module 510 is used to obtain the tenant creation information in response to the newly added tenant creation information in the monitored information queue;

[0120] The data parsing module 520 is used to parse the tenant creation information and obtain the secondary domain name data and website homepage design data corresponding to the tenant creation information;

[0121] The data storage module 530 is used to store the secondary domain name data and the website homepage design data in a storage database;

[0122] Among them, the tenant creation information is created and sent to the information queue by the back-end server in response to the tenant creation request; the tenant creation information includes the second-level domain name data and the website homepage design data; the second-level domain name data is obtained by the back-end server calling the cloud API interface to add the second-level domain name resolution; the website homepage design data is determined by the back-end server according to the tenant creation request.

[0123] It can be understood that the contents of the above method embodiments are all applicable to the present device embodiments, the functions specifically implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0124] Please refer to Figure 6 , Figure 6 The hardware structure of the electronic device provided in the embodiment of the present application is illustrated, and the electronic device includes:

[0125] The processor 601 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of the present application;

[0126] The memory 602 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 602 can store an operating system and other applications. When the technical solution provided in the embodiment of this specification is implemented by software or firmware, the relevant program code is stored in the memory 602, and the processor 601 calls and executes the multi-tenant secondary domain name management method of the embodiment of this application;

[0127] Input / output interface 603, used to implement information input and output;

[0128] Communication interface 604, used to realize communication interaction between the device and other devices, which can be realized by wired mode (such as USB, network cable, etc.) or wireless mode (such as mobile network, WIFI, Bluetooth, etc.);

[0129] Bus 605 , which transmits information between various components of the device (e.g., processor 601 , memory 602 , input / output interface 603 , and communication interface 604 );

[0130] The processor 601 , the memory 602 , the input / output interface 603 and the communication interface 604 are connected to each other in communication within the device via a bus 605 .

[0131] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the above-mentioned multi-tenant secondary domain name management method is implemented.

[0132] It can be understood that the contents of the above method embodiments are all applicable to the present storage medium embodiments, the functions specifically implemented by the present storage medium embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0133] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0134] The embodiments of the present application provide a multi-tenant second-level domain name management method, device, electronic device and storage medium, which dynamically add the second-level domain name applied for by the tenant by calling the cloud API interface, without the need for manual addition operations by the software as a service platform administrator, and can achieve fully automated addition of the second-level domain name, providing users with a good user experience.

[0135] The embodiments described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0136] Those skilled in the art will appreciate that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present application, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.

[0137] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0138] Those skilled in the art will appreciate that all or some of the steps in the methods disclosed above, and the functional modules / units in the systems and devices may be implemented as software, firmware, hardware, or a suitable combination thereof.

[0139] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0140] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0141] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0142] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0143] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0144] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including multiple instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store programs.

[0145] The preferred embodiments of the present invention are described above with reference to the accompanying drawings, but the scope of the rights of the present invention is not limited thereto. Any modification, equivalent substitution and improvement made by a person skilled in the art without departing from the scope and essence of the present invention should be within the scope of the rights of the present invention.

Claims

1. A multi-tenant secondary domain name management method, characterized in that: The method comprises the following steps: In response to newly added tenant creation information in the monitored information queue, obtain the tenant creation information; Parsing the tenant creation information, and acquiring secondary domain name data and website homepage design data corresponding to the tenant creation information; The secondary domain name data and the website homepage design data are stored in a storage database; Among them, the tenant creation information is created and sent to the information queue by the back-end server in response to the tenant creation request; the tenant creation information includes the second-level domain name data and the website homepage design data; the second-level domain name data is obtained by the back-end server calling the cloud API interface to add the second-level domain name resolution; the website homepage design data is determined by the back-end server according to the tenant creation request.

2. The multi-tenant secondary domain name management method according to claim 1, characterized in that: After storing the secondary domain name data and the website homepage design data in a storage database, the method further includes: In response to the network connection access request, obtaining the network connection access request; Parsing the network connection access request to obtain a target secondary domain name; Retrieving the secondary domain name data stored in the storage database; When the second-level domain name data stored in the storage database matches the second-level domain name data that is consistent with the target second-level domain name, the website homepage design data corresponding to the second-level domain name data is read, and the tenant identity corresponding to the network connection access request is determined.

3. The multi-tenant secondary domain name management method according to claim 2, characterized in that: The method further comprises: When the second-level domain name data stored in the storage database does not match the second-level domain name data that is consistent with the target second-level domain name, network connection access request rejection information is returned.

4. The multi-tenant secondary domain name management method according to claim 2, characterized in that: When the second-level domain name data stored in the storage database matches the second-level domain name data that is consistent with the target second-level domain name, after reading the website homepage design data corresponding to the second-level domain name data and determining the tenant identity corresponding to the network connection access request, the method further includes: Receive a login request initiated by a tenant, and add the tenant identity identifier to a header field of the login request; Sending a login request with a header field containing the tenant identity to the backend server.

5. The multi-tenant secondary domain name management method according to claim 1, characterized in that: The storing of the secondary domain name data and the website homepage design data into a storage database includes: Add the secondary domain name data to the allowed access path list; Add the website homepage design data to the reverse proxy webpage directory.

6. The multi-tenant secondary domain name management method according to claim 1, characterized in that: The method further comprises: In response to the triggered tenant deregistration request, the secondary domain name data and website homepage design data corresponding to the tenant deregistration request are deleted from the storage database.

7. The multi-tenant secondary domain name management method according to claim 1, characterized in that: The method further comprises: In response to the triggered tenant update request, the secondary domain name data and website homepage design data corresponding to the tenant update request are updated from the storage database.

8. A multi-tenant secondary domain name management device, characterized in that: The device comprises: An information monitoring module, configured to obtain the tenant creation information in response to the newly added tenant creation information in the monitored information queue; A data parsing module, used to parse the tenant creation information, and obtain the secondary domain name data and website homepage design data corresponding to the tenant creation information; A data storage module, used to store the secondary domain name data and the website homepage design data in a storage database; Among them, the tenant creation information is created and sent to the information queue by the back-end server in response to the tenant creation request; the tenant creation information includes the second-level domain name data and the website homepage design data; the second-level domain name data is obtained by the back-end server calling the cloud API interface to add the second-level domain name resolution; the website homepage design data is determined by the back-end server according to the tenant creation request.

9. An electronic device, characterized in that: The electronic device includes a memory and a processor, the memory stores a computer program, and the processor implements the multi-tenant secondary domain name management method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the multi-tenant secondary domain name management method described in any one of claims 1 to 7 is implemented.

Images