A method for resource access, related apparatus, device and storage medium

Abstract

This application discloses a method for accessing resources, applicable to cloud servers, and applicable scenarios including but not limited to cloud technology, artificial intelligence, smart transportation, and assisted driving. The method includes: responding to a first access request; if a target login mode is already enabled, obtaining first access information of the first accessing party, wherein the first access information is pre-stored on a server, or the first access information is information carried by a terminal device in a first small text file cookie and transmitted to the server; generating a first resource request based on the first access request and the first access information; responding to the first resource request, obtaining a first target resource associated with first domain name information; and sending the first target resource to the terminal device. This application also provides an apparatus, device, and storage medium. For the accessing party, this application allows access to resources corresponding to the appropriate permissions without entering a login environment, thereby improving resource access efficiency.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular to a method, related apparatus, device and storage medium for resource access. Background Technology

[0002] With the rapid development of information technology, cloud technology has been widely applied to all sectors of society. Based on cloud technology, hardware computing resources are virtualized to form a vast virtual resource pool, which is provided to users through a dynamically scalable deployment. Users can access this virtual resource pool via the network to obtain the cloud resources they need, according to their own requirements.

[0003] Currently, users need to log in to a cloud system (e.g., a public cloud system, a private cloud system, or a hybrid cloud system) before accessing cloud resources. Login methods include, but are not limited to, using a username and password, SMS verification code, or multi-factor authentication (MFA) tokens.

[0004] However, the inventors discovered that existing solutions have at least the following problems: regardless of the method used to log in to the cloud system, a certain amount of time is required for the corresponding operations, making the login process cumbersome and reducing resource access efficiency. Currently, no effective solution has been proposed to address these issues. Summary of the Invention

[0005] This application provides a method, related apparatus, device, and storage medium for resource access. As can be seen, the accessing party can access resources corresponding to their permissions without needing to enter a login environment, thereby improving resource access efficiency.

[0006] In view of this, this application provides a method for accessing resources, including:

[0007] Receive a first access request sent by a terminal device, wherein the first access request carries first domain name information;

[0008] In response to the first access request, if the target login mode has been enabled, the first access information of the first access party is obtained, wherein the first access information is information pre-stored in the server, or the first access information is information carried by the terminal device in a first small text file cookie and transmitted to the server.

[0009] Based on the first access request and the first access information, generate a first resource request;

[0010] In response to the first resource request, obtain the first target resource associated with the first domain name information;

[0011] Send the first target resource to the terminal device.

[0012] This application also provides a method for accessing resources, including:

[0013] In response to a domain name input operation, a first access request is sent to the server so that the server, when the target login mode is enabled, can obtain the first target resource associated with the first domain name information according to the first resource request. The first access request carries the first domain name information, and the first resource request is generated based on the first access request and the first access information. The first access information is information pre-stored on the server, or the first access information is information carried by the terminal device in a first small text file cookie and transmitted to the server.

[0014] Receive the first target resource sent by the server;

[0015] Render and display the first target resource.

[0016] This application also provides a resource access device, comprising:

[0017] The receiving module is used to receive a first access request sent by the terminal device, wherein the first access request carries first domain name information;

[0018] The acquisition module is used to respond to the first access request. If the target login mode has been enabled, the module acquires the first access information of the first access party. The first access information is either pre-stored in the server or is information carried by the terminal device in a first small text file cookie and transmitted to the server.

[0019] The generation module is used to generate a first resource request based on the first access request and the first access information;

[0020] The acquisition module is also used to respond to the first resource request and acquire the first target resource associated with the first domain name information;

[0021] The sending module is used to send the first target resource to the terminal device.

[0022] In one possible design, in another implementation of another aspect of the embodiments of this application, the resource access device further includes a determining module;

[0023] The determination module is used to determine that the target login mode has been enabled if the first access request sent by the terminal device also carries target field information after receiving the first access request. The target field information and the first domain name information are used to form the target domain name information.

[0024] The determination module is also used to determine that the target login mode has not been enabled if the first access request does not carry target field information after receiving the first access request sent by the terminal device.

[0025] or,

[0026] The determination module is also used to determine that the target login mode has been enabled if the value of the variable corresponding to the login mode variable is the first variable value after receiving the first access request sent by the terminal device.

[0027] The determination module is also used to determine that the target login mode is not enabled if the value of the variable corresponding to the login mode variable is the second variable value after receiving the first access request sent by the terminal device.

[0028] In one possible design, in another implementation of another aspect of the embodiments of this application,

[0029] The determination module is also used to determine that the target login mode has been enabled if, after receiving the first access request sent by the terminal device, the first access request also carries target field information and the value of the variable corresponding to the login mode variable is the first variable value.

[0030] The determination module is also used to determine that the target login mode is not enabled if, after receiving the first access request sent by the terminal device, the first access request also carries target field information and the value of the variable corresponding to the login mode variable is the value of the second variable.

[0031] The determination module is also used to determine that the target login mode has been enabled if, after receiving the first access request sent by the terminal device, the first access request does not carry target field information and the value of the variable corresponding to the login mode variable is the first variable value.

[0032] The determination module is also used to determine that the target login mode is not enabled if, after receiving the first access request sent by the terminal device, the first access request does not carry target field information and the value of the variable corresponding to the login mode variable is the value of the second variable.

[0033] In one possible design, in another implementation of another aspect of the embodiments of this application,

[0034] The acquisition module is specifically used to obtain first access information from the server, wherein the first access information includes the identity information and key information of the first accessing party.

[0035] In one possible design, in another implementation of another aspect of the embodiments of this application,

[0036] The acquisition module is specifically used to receive a first cookie sent by the terminal device, wherein the first cookie carries first access information, which includes the identity information and key information of the first accessing party;

[0037] Retrieve the first access information from the first cookie.

[0038] In one possible design, in another implementation of another aspect of the embodiments of this application,

[0039] The receiving module is also configured to receive a second access request sent by the terminal device after sending the first target resource to the terminal device, wherein the second access request carries second domain name information;

[0040] The receiving module is also used to respond to the second access request. If the target login mode has been enabled, it receives the second cookie sent by the terminal device. The second cookie carries the first access information, which includes the identity information and key information of the first accessing party.

[0041] The generation module is also used to generate a second resource request based on the second access request and the first access information;

[0042] The acquisition module is also used to respond to a second resource request and acquire a second target resource associated with the second domain name information;

[0043] The sending module is also used to send a second target resource to the terminal device.

[0044] In one possible design, in another implementation of another aspect of the embodiments of this application,

[0045] The receiving module is also configured to, after sending the first target resource to the terminal device, if the terminal device responds to the access switching request, receive the third cookie sent by the terminal device if the target login mode has been enabled, wherein the third cookie carries the second access information, wherein the second access information includes the identity information and key information of the second accessing party.

[0046] The generation module is also used to generate a third resource request based on the first access request and the second access information;

[0047] The acquisition module is also used to respond to a third resource request and acquire a third target resource associated with the first domain name information;

[0048] The sending module is also used to send third target resources to the terminal device.

[0049] In one possible design, in another implementation of another aspect of the embodiments of this application,

[0050] The generation module is specifically used to generate an interface call request based on the first access request, wherein the interface call request is used to request the invocation of the application programming interface (API).

[0051] Based on the API call request and the first access information, generate the first resource request;

[0052] The acquisition module is specifically used to call the API to retrieve the first target resource associated with the first domain name information.

[0053] In one possible design, in another implementation of another aspect of the embodiments of this application,

[0054] The generation module is specifically used to encapsulate the interface call request and the first access information to obtain the first resource request;

[0055] The acquisition module is specifically used to call the API to parse the first resource request and obtain the first access information to be verified, which includes the identity information to be verified and the key information to be verified.

[0056] If the identity information to be verified matches the pre-stored identity information, and the key information to be verified matches the pre-stored key information, and the identity information to be verified and the key information to be verified are successfully matched, then the first target resource associated with the first domain name information is obtained.

[0057] In one possible design, in another implementation of another aspect of the embodiments of this application,

[0058] The generation module is specifically used to obtain the key information of the first accessing party from the first access information;

[0059] The API call request is encrypted using the key information of the first access party to obtain the encrypted API call request;

[0060] The encrypted interface call request and the identity information of the first accessing party are encapsulated to obtain the first resource request;

[0061] The acquisition module is specifically used to call the API to parse the first resource request and obtain the encrypted interface call request and the identity information of the first access party;

[0062] Call the API to obtain the key information of the first accessing party based on the identity information of the first accessing party;

[0063] If the encrypted interface call request is successfully decrypted using the key information of the first access party, the first target resource associated with the first domain name information is obtained.

[0064] This application also provides a resource access device, comprising:

[0065] The sending module is used to send a first access request to the server in response to the domain name input operation, so that the server can obtain the first target resource associated with the first domain name information according to the first resource request when the target login mode is enabled. The first access request carries the first domain name information, the first resource request is generated based on the first access request and the first access information, the first access information is information pre-stored in the server, or the first access information is information carried by the terminal device in a first small text file cookie and transmitted to the server.

[0066] The receiving module is used to receive the first target resource sent by the server;

[0067] The display module is used to render and display the first target resource.

[0068] In one possible design, in another implementation of another aspect of the embodiments of this application,

[0069] The sending module is also used to respond to the domain name input operation and send a second access request to the server so that the server can obtain the second target resource associated with the second domain name information according to the second resource request when the target login mode has been enabled. The second access request carries the second domain name information, and the second resource request is generated based on the second access request and the first access information. The first access information is the information carried by the terminal device in the second cookie and transmitted to the server.

[0070] The receiving module is also used to receive a second target resource sent by the server;

[0071] The display module is also used to render and display the second target resource.

[0072] In one possible design, in another implementation of another aspect of the embodiments of this application,

[0073] The display module is also used to respond to the selection operation of the information viewing control, display account information and the corresponding switching control of the account information, wherein the account information is bound to the second access information, and the second access information includes the identity information and key information of the second access party;

[0074] The sending module is also used to respond to the selection operation for the switching control and send a third cookie to the server so that the server can obtain the third target resource associated with the first domain name information according to the third resource request when the target login mode is enabled. The third cookie carries the second access information, and the third resource request is generated based on the first access request and the second access information.

[0075] The receiving module is also used to receive third-party target resources sent by the server;

[0076] The display module is also used to render and display third-party target resources.

[0077] In one possible design, in another implementation of another aspect of the embodiments of this application, the resource access device further includes a processing module;

[0078] The display module is also used to display the information entry area in response to information addition operations;

[0079] The processing module is used to respond to input operations in the information entry area and save the accessor's account information, identity information, and key information to local storage.

[0080] In one possible design, in another implementation of another aspect of the embodiments of this application,

[0081] The processing module is also used to delete the visitor's account information, identity information, and key information from the browser's local storage in response to information deletion operations.

[0082] In another aspect, this application provides a computer device including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the methods described above.

[0083] Another aspect of this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the methods described above.

[0084] Another aspect of this application provides a computer program product, including a computer program that, when executed by a processor, implements the methods described above.

[0085] As can be seen from the above technical solutions, the embodiments of this application have the following advantages:

[0086] This application provides a method for resource access. In response to a first access request sent by a terminal device, if a target login mode is enabled, the server obtains the first access information of the first accessing party. The first access information may be information pre-stored on the server or sent by the terminal device via a cookie. Based on this, the server generates a first resource request according to the first access request and the first access information, and then obtains a first target resource associated with the first domain name information according to the first resource request. The server then sends the first target resource to the terminal device. Through this method, when the target login mode is enabled, the server can obtain the user's access information locally, or the server can receive access information sent by the terminal device via a cookie. The cookie can store the access information of the most recent accessing party. Therefore, for the accessing party, resources corresponding to the appropriate permissions can be accessed without entering a login environment, thereby improving resource access efficiency. Attached Figure Description

[0087] Figure 1 This is a schematic diagram of an implementation environment for the resource access method in the embodiments of this application;

[0088] Figure 2 This is a schematic diagram of another implementation environment of the resource access method in the embodiments of this application;

[0089] Figure 3 This is a flowchart illustrating a resource access method in an embodiment of this application;

[0090] Figure 4 This is a schematic diagram of an interaction process based on a target login mode in an embodiment of this application;

[0091] Figure 5 This is another flowchart illustrating the resource access method in this application embodiment;

[0092] Figure 6 This is a schematic diagram of a resource access page in an embodiment of this application;

[0093] Figure 7 This is another schematic diagram of the resource access page in the embodiments of this application;

[0094] Figure 8 This is another schematic diagram of the resource access page in the embodiments of this application;

[0095] Figure 9 This is another schematic diagram of the resource access page in the embodiments of this application;

[0096] Figure 10 This is a schematic diagram of a resource access device in an embodiment of this application;

[0097] Figure 11 This is another schematic diagram of the resource access device in the embodiments of this application;

[0098] Figure 12 This is a schematic diagram of the server structure in an embodiment of this application;

[0099] Figure 13 This is a schematic diagram of the structure of a terminal device in an embodiment of this application. Detailed Implementation

[0100] This application provides a method, related apparatus, device, and storage medium for resource access. As can be seen, the accessing party can access resources corresponding to their permissions without needing to enter a login environment, thereby improving resource access efficiency.

[0101] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “corresponding” with any variations thereof are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0102] With technological advancements, an increasing number of cloud service providers offer users cloud computing services with varying functionalities. Different cloud service providers can manage user access permissions to various system resources or functions. Cloud computing is a computing model that distributes computing tasks across a resource pool comprised of numerous computers, enabling various application systems to obtain computing power, storage space, and information services as needed. The network providing these resources is called the "cloud." From the user's perspective, resources in the "cloud" are infinitely scalable, readily available, on-demand, expandable, and pay-as-you-go. Cloud computing can be categorized into public clouds, private clouds, and hybrid clouds based on deployment methods. Users can access resources with corresponding permissions through public cloud platforms, private cloud platforms, or hybrid cloud platforms. The following sections will introduce public clouds, private clouds, and hybrid clouds respectively.

[0103] A private cloud is created within a firewall, housing cloud infrastructure and hardware / software resources for various departments within an organization or enterprise to share resources within a data center. Besides hardware resources, creating a private cloud typically involves Infrastructure as a Service (IaaS) software for the cloud equipment. Private cloud computing also comprises three layers: cloud hardware, cloud platform, and cloud services. The difference is that cloud hardware consists of the user's own personal computer or server, rather than the cloud computing vendor's data center. Cloud computing vendors build data centers to provide public cloud services to millions of users, thus requiring hundreds of thousands or even millions of servers. For individuals, private cloud computing serves only family and friends; for enterprises, it serves only their own employees, customers, and suppliers. Therefore, the personal computers or servers of individuals or enterprises are sufficient to provide cloud services.

[0104] Public cloud typically refers to a cloud service provided by a third-party provider to users. Public clouds are generally accessible via the internet and may be free or inexpensive. The core attribute of a public cloud is shared resource services. Many instances of this type of cloud exist, providing services across today's open public networks.

[0105] Hybrid cloud, which combines public and private clouds, has become a major model and development direction of cloud computing in recent years. Private clouds are primarily geared towards enterprise users. For security reasons, enterprises prefer to store data in private clouds, but at the same time, they also want access to the computing resources of public clouds. Hybrid cloud is increasingly being adopted in this context. It combines and matches public and private clouds to achieve optimal results. This personalized solution achieves both cost-effectiveness and security.

[0106] Currently, users need to log in to the cloud platform to access resources in the system. Furthermore, if a specified time elapses after logging in, the system automatically logs out, requiring the user to re-enter their username and password upon the next login. This is particularly problematic for development environments, where users frequently need to access multiple versions of resources, each with its own set of login credentials. This makes switching between versions extremely cumbersome.

[0107] Based on this, this application proposes a resource access method to address the problem of low resource access efficiency. Specifically, users can access resources in the cloud system without logging in. For developers, this eliminates the need to maintain usernames and passwords when accessing different versions of resources, significantly improving development efficiency.

[0108] The method provided in this application can be applied to... Figure 1 The implementation environment shown and Figure 2For the implementation environment shown, please refer to [link / reference]. Figure 1 The implementation environment includes terminal device 110 and server 130, wherein terminal device 110 and server 130 are connected via communication network 120. Please refer to... Figure 2 The implementation environment includes a terminal device 110, a local server 140, and a cloud server 150. The terminal device 110 and the local server 140 are connected through a communication network 120, and the local server 140 and the cloud server 150 are connected through a communication network 120.

[0109] The communication network 120 involved in this application uses standard communication technologies and / or protocols, typically the Internet, but can also be any network, including but not limited to Bluetooth, local area network (LAN), metropolitan area network (MAN), wide area network (WAN), mobile, private network, or any combination of virtual private network. In some embodiments, customized or dedicated data communication technologies may be used to replace or supplement the above-mentioned data communication technologies.

[0110] The terminal devices 110 involved in this application include, but are not limited to, mobile phones, computers, smart voice interaction devices, smart home appliances, vehicle terminals, and aircraft. The client is deployed on the terminal device 110 and can run on the terminal device 110 via a browser or as a standalone app.

[0111] The server 130 involved in this application can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0112] The server 130 in this application may specifically refer to a local server 140 and a cloud server 150. The local server 140 is a hardware device used to provide computing services, and its components include, but are not limited to, a processor, hard disk, memory, and system bus. Since the local server 140 needs to respond to and process service requests, it should generally have the capability to undertake and guarantee services. The cloud server 150 is a scalable computing server, typically a server cluster. The computing of the cloud server 150 is implemented in the cloud, which can reduce development and maintenance costs. The cloud server uses distributed storage, enabling real-time multi-replica disaster recovery, eliminating single points of failure, effectively avoiding various faults, supporting elastic scaling of storage resources, and providing functions such as hot migration.

[0113] Combination Figure 1 In the illustrated implementation environment, terminal device 110 sends an access request to server 130 via communication network 120, wherein the access request carries domain name information. If the target login mode has been enabled, server 130 can obtain the access information and generate a resource request for invoking resources based on the access information. Thus, based on the resource request, the server 130 locally invokes the target resource under the corresponding permissions, and server 130 sends the target resource to terminal device 110 via communication network 120.

[0114] Combination Figure 2 In the illustrated implementation environment, terminal device 110 sends an access request to local server 140 via communication network 120, wherein the access request carries domain name information. If the target login mode is already enabled, local server 140 can obtain the access information and generate a resource request for invoking resources based on the access information. Therefore, local server 140 sends a resource request to cloud server 150 via communication network 120. Cloud server 150 invokes the target resource under the corresponding permissions based on the resource request and then sends feedback back to local server 140 via communication network 120. Local server 140 then sends the target resource to terminal device 110 via communication network 120.

[0115] Based on the above introduction, the resource access methods in this application will be described from the server's perspective below. Please refer to [link / reference]. Figure 3 In this application, the resource access method can be completed independently by the server, independently by the terminal device, or jointly by the terminal device and the server. This application includes:

[0116] 210. Receive a first access request sent by a terminal device, wherein the first access request carries first domain name information;

[0117] In one or more embodiments, a user triggers a first access request through a browser provided by a terminal device. The server (e.g., a local server) then receives the first access request from the terminal device through a scripting language runtime environment (Node.js) layer. The first access request carries first domain name information, which may specifically be main domain name information.

[0118] 220. In response to the first access request, if the target login mode has been enabled, the first access information of the first access party is obtained, wherein the first access information is information pre-stored in the server, or the first access information is information carried by the terminal device in a first small text file cookie and transmitted to the server.

[0119] In one or more embodiments, in response to a first access request, if the target login mode (i.e., passwordless login mode) is enabled, the server (e.g., a local server) can directly obtain the first access information of the first accessing party. The first access information includes the identity information (secretID) and key information (secretKey) of the first accessing party, with each accessing party having a unique pair of secretID and secretKey.

[0120] For example, in one scenario, the access information used when the access request was most recently triggered (i.e., the first access information) is retrieved from the browser's local storage. This access information (i.e., the first access information) is then added to a first small text file (cookie) along with the request and sent to the Node.js layer. For example, in another scenario, if the server does not receive access information from the terminal device, or if the system supports accessing resources using default access information, the server can retrieve the access information (i.e., the first access information) directly from local storage.

[0121] 230. Generate a first resource request based on the first access request and the first access information;

[0122] In one or more embodiments, the server (e.g., a local server) can determine the resources associated with the first domain name information carried in the first access request. Therefore, the server generates a first resource request by combining the addresses of these resources with the first access information. It should be noted that the first resource request can specifically be a Hypertext Transfer Protocol (HTTP) request or a Hypertext Transfer Protocol over Secure Socket Layer (HTTPS) request.

[0123] Specifically, taking an HTTP request as an example, the first access information (i.e., the first accessor's secretID and secretKey) and the request payload are combined into a query parameter in the request. This query parameter is then used as the request body of the first resource request and sent to the application programming interface (API) via form submission. This API can specifically be a cloud API (CAPI).

[0124] 240. In response to the first resource request, obtain the first target resource associated with the first domain name information;

[0125] In one or more embodiments, the server responds to a first resource request and invokes the resource corresponding to the first access information (i.e., the first target resource) based on the resource address carried in the first resource request.

[0126] Specifically, taking a request for cloud virtual machine (CVM) resources as an example, the local server sends a first resource request to the cloud server. The cloud server, based on the resource address carried in the first resource request, calls the corresponding resource (i.e., the first target resource), and then sends the first target resource back to the local server via an API (e.g., CAPI). Here, the first target resource is a resource associated with the first domain name information. For example, if the first domain name information needs to load resources A and B, then the first resource request can carry the calling addresses of resource A and resource B.

[0127] 250. Send the first target resource to the terminal device.

[0128] In one or more embodiments, a server (e.g., a local server) sends a first target resource to a terminal device, whereby the terminal device can render and display the first target resource through a browser.

[0129] This application provides a method for resource access. Using this method, when the target login mode is enabled, the server can obtain the user's access information locally, or the server can receive access information sent by the terminal device via a cookie, which can store the access information of the most recent visitor. Therefore, for the visitor, access to resources corresponding to the appropriate permissions can be obtained without entering a login environment, thereby improving resource access efficiency.

[0130] Optionally, in the above Figure 3Based on the corresponding embodiments, in another optional embodiment provided by this application, after receiving the first access request sent by the terminal device, it may further include:

[0131] If the first access request also carries target field information, it is determined that the target login mode has been enabled. The target field information and the first domain name information are used to form the target domain name information.

[0132] If the first access request does not carry the target field information, it is determined that the target login mode is not enabled.

[0133] or,

[0134] After receiving the first access request sent by the terminal device, it may also include:

[0135] If the value of the variable corresponding to the login mode variable is the first variable value, then it is determined that the target login mode has been enabled.

[0136] If the value of the variable corresponding to the login mode variable is the second variable value, then it is determined that the target login mode is not enabled.

[0137] In one or more embodiments, a method for controlling the on / off switch of a passwordless login mode is described. As can be seen from the foregoing embodiments, the server needs to determine whether the target login mode is enabled. If the target login mode is enabled, the server performs the corresponding operation. If the target login mode is not enabled, the user needs to enter a username and password on the login interface to log in. The following will describe two methods for determining whether the target login mode is enabled, specifically:

[0138] Method 1: Based on specified domain name information;

[0139] The first access request contains the first domain name information. If the target login mode needs to be triggered, the first access request also needs to contain the target field information. That is, the target field information and the first domain name information together constitute the target domain name information. Therefore, the user can enter the specified domain name information (i.e., the target domain name information) in the browser provided by the terminal device to directly access resources under the corresponding permissions.

[0140] For example, suppose the target domain information is "standalone.xxx.com", that is, the target domain information can be represented as "standalone.${main domain information}". Here, "standalone" is the target field information, and "xxx.com" is the first domain information. Based on this, if the first access request also carries the target field information, that is, the first access request is generated based on the target domain information, then it indicates that the target login mode is enabled. If the first access request does not carry the target field information, that is, the first access request is generated based on the first domain information, then it indicates that the target login mode is not enabled.

[0141] It should be noted that the target field information can also be set to other field information, which is not limited here. The target field information can be before the main domain information, or the target field information can be after the main domain information. The above example is given with the target field information before the main domain information, but it should not be construed as a limitation of this application.

[0142] Method 2: Based on backend variables;

[0143] In a server-side Node.js layer, the login mode variable can be used to determine whether a target login mode is enabled. Taking the login mode variable "isByPwd" as an example, if "isByPwd = true", it means the variable value is the first value, where "true" is the first value, thus indicating that the target login mode is enabled. If "isByPwd = false", it means the variable value is the second value, where "false" is the second value, thus indicating that the target login mode is not enabled.

[0144] Understandably, when the target login mode is enabled, login status verification is skipped. Simultaneously, the indicator for enabling the target login mode can be rendered to the browser using an embedded JavaScript (EJS) template engine. The browser can then display the corresponding UI elements based on this indicator.

[0145] Secondly, this application provides a method for controlling the on / off switch of the passwordless login mode. Using this method, in one scenario, the passwordless login mode can be directly enabled by specifying domain information; that is, resources in the system can be directly accessed through a specific domain name, avoiding the cumbersome operations associated with login. In another scenario, the passwordless login mode can be enabled through backend variables; that is, relevant personnel can control whether to enable the passwordless login mode according to actual needs, thereby improving the feasibility and flexibility of the solution.

[0146] Optionally, in the above Figure 3 Based on the corresponding embodiments, in another optional embodiment provided by this application, after receiving the first access request sent by the terminal device, it may further include:

[0147] If the first access request also carries target field information, and the value of the variable corresponding to the login mode variable is the value of the first variable, then it is determined that the target login mode has been enabled.

[0148] If the first access request also carries target field information, and the value of the variable corresponding to the login mode variable is the value of the second variable, then it is determined that the target login mode has not been enabled.

[0149] If the first access request does not carry the target field information, and the value of the variable corresponding to the login mode variable is the value of the first variable, then it is determined that the target login mode has been enabled.

[0150] If the first access request does not carry the target field information, and the value of the variable corresponding to the login mode variable is the value of the second variable, then it is determined that the target login mode is not enabled.

[0151] In one or more embodiments, another method for controlling the on / off switch of the passwordless login mode is described. As can be seen from the foregoing embodiments, whether to enable the target login mode can be determined based on specified domain information or backend variables. In practical applications, controlling the login mode based on backend variables has a higher priority than controlling the login mode based on specified domain information.

[0152] For example, assume that the first access request also carries target field information, that is, the first access request is a request generated based on the target domain name information. Meanwhile, assume that the value of the variable corresponding to the login mode variable is the first variable value. Based on this, the login mode variable is used first to determine that the target login mode has been enabled.

[0153] For example, assume that the first access request also carries target field information, that is, the first access request is a request generated based on the target domain name information. Meanwhile, assume that the value of the variable corresponding to the login mode variable is the second variable value. Based on this, the login mode variable is used first to determine that the target login mode is not enabled.

[0154] For example, assume that the first access request does not carry target field information, that is, the first access request is a request generated based on the first domain name information. At the same time, assume that the value of the variable corresponding to the login mode variable is the first variable value. Based on this, the login mode variable is used first to determine whether the target login mode has been enabled.

[0155] For example, assume that the first access request does not carry target field information, that is, the first access request is a request generated based on the first domain name information. Meanwhile, assume that the value of the variable corresponding to the login mode variable is the second variable value. Based on this, the login mode variable is used first to determine that the target login mode is not enabled.

[0156] Secondly, this application provides another method for controlling the passwordless login mode switch. This method prioritizes determining whether to enable the passwordless login mode based on backend variables. Therefore, relevant personnel have higher control authority and can control whether to enable the passwordless login mode according to actual needs, thereby improving the feasibility and flexibility of the solution.

[0157] Optionally, in the above Figure 3Based on the corresponding embodiments, in another optional embodiment provided by this application, obtaining the first access information of the first accessing party may specifically include:

[0158] Obtain first access information from the server, wherein the first access information includes the identity information and key information of the first accessing party.

[0159] In one or more embodiments, a method for accessing resources using general access information is described. As can be seen from the foregoing embodiments, in scenarios involving accessing system resources, a passwordless login solution can be achieved with a single configuration by configuring a set of access information on the server side.

[0160] Specifically, relevant personnel can configure a common access information set, using this as the primary access information. Based on this, all users accessing the system will use the same set of access information. Therefore, when the server's Node.js layer does not receive access information sent by the browser via cookies, it can directly use the configured default access information as the primary access information.

[0161] Secondly, this application provides a method for accessing resources using generic access information. Using this method, a default access setting can also be pre-defined. Based on this, different users can access the same resources without logging into the system, thereby improving the efficiency of system resource access.

[0162] Optionally, in the above Figure 3 Based on the corresponding embodiments, in another optional embodiment provided by this application, obtaining the first access information of the first accessing party may specifically include:

[0163] The terminal device receives a first cookie, wherein the first cookie carries first access information, which includes the identity information and key information of the first accessing party.

[0164] Retrieve the first access information from the first cookie.

[0165] In one or more embodiments, a method for accessing resources using private access information is described. As can be seen from the foregoing embodiments, in the scenario of accessing system resources, a user can first set up account information, and after registering in the system using this account information, obtain a set of access information (i.e., secretID and secretKey) bound to that account information. At the same time, different access information can be configured with corresponding access permissions, and different access permissions can access different system resources.

[0166] Specifically, for ease of understanding, please refer to Table 1, which illustrates the correspondence between account information and access information.

[0167] Table 1

[0168] Account Information secretID secretKey Zhang San WEQz8krbsJ5yKBZp848SA GFkf29xGARNpq86cd98joQ Li Si 941Hjf9398rndvNG93mav4 799538AJcd98jDA272jewOE

[0169] Assuming user "Zhang San" is the first visitor, based on Table 1, the first visitor's access information includes "WEQz8krbsJ5yKBZp848SA" and "GFkf29xGARNpq86cd98joQ". Based on this, assuming the server receives a cookie carrying the first access information (i.e., the first cookie) through the Node.js layer, the Node.js layer can extract the first access information from the first cookie. Therefore, the corresponding target resource can be provided to the first visitor.

[0170] Secondly, this application provides a method for accessing resources using private access information. Through this method, different users pre-configure their access information. Based on this, different users can access different resources without logging into the system. This not only improves the efficiency of system resource access but also allows for setting different access permissions for different users, thus achieving flexibility in resource access.

[0171] Optionally, in the above Figure 3 Based on the corresponding embodiments, in another optional embodiment provided by this application, after sending the first target resource to the terminal device, it may further include:

[0172] Receive a second access request sent by a terminal device, wherein the second access request carries second domain name information;

[0173] In response to the second access request, if the target login mode has been enabled, the second cookie sent by the terminal device is received, wherein the second cookie carries the first access information, wherein the first access information includes the identity information and key information of the first accessing party;

[0174] Based on the second access request and the first access information, a second resource request is generated;

[0175] In response to the second resource request, obtain the second target resource associated with the second domain name information;

[0176] Send the second target resource to the terminal device.

[0177] In one or more embodiments, a method for switching access between different version environments is described. As the foregoing embodiments illustrate, especially in development environments, users often need to access resources corresponding to multiple different version environments, each with its own set of login credentials. Therefore, users can quickly switch between version environments by triggering access requests.

[0178] Specifically, suppose a user (e.g., the first visitor) most recently triggered an access request (i.e., the first access request) using first access information, and the browser sent the first access information to the server's Node.js layer via a first cookie. Based on this, the user can continue to trigger a second access request through the browser as the first visitor. The second access request carries second domain information, which may specifically be the main domain information. Since the user used the first access information when triggering the first access request, the browser can add the first access information to the second cookie along with the request and send it to the server's (e.g., the local server's) Node.js layer. The first access information includes the first visitor's secretID and secretKey. Based on the second domain information carried in the second access request, the server (e.g., the local server) can determine the resources associated with the second domain information. Therefore, the server generates a second resource request by combining the addresses of these resources with the first access information. In response to the second resource request, the server (e.g., the cloud server) calls the resource corresponding to the first access information (i.e., the second target resource) based on the resource address carried in the second resource request. Based on this, the server (e.g., a local server) then sends the acquired second target resource to the terminal device. The terminal device can then render and display the second target resource through a browser.

[0179] It should be noted that if the Node.js layer of the server (e.g., the local server) does not receive the access information sent by the browser, or if the system supports accessing resources using the default access information, the server can directly extract the access information from the local machine (i.e., the first access information).

[0180] Secondly, this application provides a method for switching between different version environments. Through this method, the same user can also log in without a password in different version environments. Therefore, it is well-suited for development environments, thereby improving the efficiency of user switching between version environments.

[0181] Optionally, in the above Figure 3 Based on the corresponding embodiments, in another optional embodiment provided by this application, after sending the first target resource to the terminal device, it may further include:

[0182] If the terminal device responds to the access switching request, and the target login mode is already enabled, it receives the third cookie sent by the terminal device. The third cookie carries the second access information, which includes the identity information and key information of the second accessing party.

[0183] Based on the first access request and the second access information, a third resource request is generated;

[0184] In response to a third resource request, obtain the third target resource associated with the first domain name information;

[0185] Send third target resources to the terminal device.

[0186] In one or more embodiments, a method for switching between different system resources for access is described. As the foregoing embodiments illustrate, especially in development environments, different users often require resources corresponding to the same version of the environment, and each user has a unique set of login credentials. Therefore, different users can quickly access each other's identities by triggering access requests.

[0187] Specifically, suppose a user wants to switch to a second access identity to access resources corresponding to the first domain information. The user can trigger an access switching request through the browser provided by the terminal device. This request carries second access information, including the second access party's secretID and secretKey. Since the user uses this second access information when triggering the request, the browser adds it to a third cookie and sends it to the Node.js layer of the server (e.g., a local server). Based on the first domain information carried in the first access request, the server (e.g., the local server) can determine the resources associated with the first domain information. Therefore, the server generates a third resource request by combining the addresses of these resources with the access switching request. Responding to the third resource request, the server (e.g., a cloud server) calls the resource corresponding to the second access information (i.e., the third target resource) based on the resource address carried in the third resource request. Based on this, the server (e.g., the local server) then sends the obtained third target resource to the terminal device. Thus, the terminal device can render and display the third target resource through its browser.

[0188] Secondly, this application provides a method for switching between different system resources for access. Through this method, different users can log in without a password within the same environment. Therefore, it is well-suited for scenarios where multiple different users access resources, thereby improving the efficiency of users switching access identities.

[0189] Optionally, in the above Figure 3 Based on the corresponding embodiments, in another optional embodiment provided by this application, a first resource request is generated according to the first access request and the first access information, which may specifically include:

[0190] An interface call request is generated based on the first access request, wherein the interface call request is used to request the invocation of the application programming interface (API);

[0191] Based on the API call request and the first access information, generate the first resource request;

[0192] Obtaining the first target resource associated with the first domain name information can specifically include:

[0193] Call the API to retrieve the first target resource associated with the first domain name information.

[0194] In one or more embodiments, a method for invoking a target resource based on a resource request is described. As can be seen from the foregoing embodiments, taking the first domain name information carried in the first access request as an example, the server (e.g., a local server) associates resources based on the first domain name information. These resources typically need to be invoked through an API call request. The API call request can be an API request or a cloud API request, and is not limited here. Two methods for generating the first resource request will be described below.

[0195] Method 1: Automatically rewrite the domain name information;

[0196] Specifically, assume the first domain name is "xxx.com" and the target domain name is "standalone.xxx.com". Here, "standalone" is the target field information. Also assume the domain name information corresponding to resource A is "xxx.com / 111". Based on this, when the target login mode is enabled, the domain name information corresponding to resource A will be automatically changed to "standalone.xxx.com / 111", that is, "standalone.xxx.com / 111" will be used as the interface call request to invoke resource A.

[0197] Method 2: No need to rewrite domain name information;

[0198] Specifically, assume the first domain name is "xxx.com", and the domain name corresponding to resource A is "xxx.com / 111". Based on this, if the value of the first variable corresponding to the login mode variable determines that the target login mode has been enabled, then there is no need to rewrite the domain name information corresponding to resource A. That is, "xxx.com / 111" can be directly used as the interface call request for calling resource A.

[0199] Therefore, the server (e.g., a local server) encapsulates the interface call request and the initial access information into a first resource request, and accesses the corresponding first target resource (e.g., resource A) based on the first resource request. It is understood that the first resource request can be an HTTP request or an HTTPS request; this is not limited here.

[0200] Secondly, this application provides a method for invoking target resources based on resource requests. Through this method, before generating resource requests, the interface call requests can be automatically rewritten, ensuring that each interface call request meets the conditions for passwordless access, thereby guaranteeing the feasibility and operability of the solution.

[0201] Optionally, in the above Figure 3 Based on the corresponding embodiments, in another optional embodiment provided by this application, a first resource request is generated according to the interface call request and the first access information, which may specifically include:

[0202] The interface call request and the first access information are encapsulated to obtain the first resource request;

[0203] Calling the API to retrieve the first target resource associated with the first domain name information can specifically include:

[0204] The API is called to parse the first resource request and obtain the first access information to be verified, which includes the identity information to be verified and the key information to be verified.

[0205] If the identity information to be verified matches the pre-stored identity information, and the key information to be verified matches the pre-stored key information, and the identity information to be verified and the key information to be verified are successfully matched, then the first target resource associated with the first domain name information is obtained.

[0206] In one or more embodiments, a method for verifying access information based on APIs is described. As described in the foregoing embodiments, taking the first domain name information carried in the first access request as an example, after obtaining the interface call request (e.g., an API request or a cloud API request), the server can encapsulate the interface call request with the first access information to obtain the first resource request (e.g., an HTTP request or a cloud HTTPS request). The server calls the API or cloud API to parse the first resource request, thereby obtaining the first access information to be verified. If the first resource request has not been tampered with, it should carry the first access information. Therefore, the server needs to verify the parsed access information.

[0207] Specifically, the first access information to be verified includes identity information to be verified and key information to be verified. Based on this, the server can determine whether the identity information to be verified matches the pre-stored identity information. If they match, it means that the identity information to be verified has not been tampered with. Similarly, the server can determine whether the key information to be verified matches the pre-stored key information. If they match, it means that the key information to be verified has not been tampered with. In addition, the server also needs to determine whether the identity information to be verified and the key information to be verified belong to the same set of access information. If they do, it means that the identity information to be verified and the key information to be verified have been successfully matched. Thus, the server determines that the first resource request has not been intercepted or tampered with, and therefore, it can call the resource corresponding to the first access information (i.e., the first target resource) based on the first domain name information.

[0208] Furthermore, this application provides a method for verifying access information based on an API. Through this method, the server calls the API to verify the received access information, that is, to verify the consistency and accuracy of the key information and identity information, preventing information from being intercepted or tampered with during transmission, thereby improving the security and reliability of resource access.

[0209] Optionally, in the above Figure 3 Based on the corresponding embodiments, in another optional embodiment provided by this application, a first resource request is generated according to the interface call request and the first access information, which may specifically include:

[0210] Obtain the key information of the first accessing party from the first access information;

[0211] The API call request is encrypted using the key information of the first access party to obtain the encrypted API call request;

[0212] The encrypted interface call request and the identity information of the first accessing party are encapsulated to obtain the first resource request;

[0213] Calling the API to retrieve the first target resource associated with the first domain name information can specifically include,

[0214] The API is invoked to parse the first resource request, obtaining the encrypted API call request and the identity information of the first accessing party;

[0215] Call the API to obtain the key information of the first accessing party based on the identity information of the first accessing party;

[0216] If the encrypted interface call request is successfully decrypted using the key information of the first access party, the first target resource associated with the first domain name information is obtained.

[0217] In one or more embodiments, another method for verifying access information based on API is introduced. As described in the foregoing embodiments, taking the first domain name information carried in the first access request as an example, after obtaining the interface call request (e.g., an API request or a cloud API request), the server uses the secretKey in the first domain name information to encrypt the interface call request, thereby obtaining the encrypted interface call request. Then, the encrypted interface call request and the secretID of the first access party are encapsulated to obtain the first resource request (e.g., an HTTP request or a cloud HTTPS request). The server calls the API or cloud API to parse the first resource request, thereby obtaining the encrypted interface call request and the secretID of the first access party.

[0218] Specifically, the server stores the mapping relationship between secretID and secretKey locally. Therefore, the server can find the secretKey of the first access party through the secretID. Based on this, the server can use the secretKey of the first access party to decrypt the encrypted interface call request. If the decryption is successful, the server can call the resource corresponding to the first access information (i.e., the first target resource) based on the first domain name information.

[0219] Furthermore, this application provides another method for verifying access information based on API. Using this method, the server calls the API to verify the received access information, that is, to verify the consistency and accuracy of the key information and identity information. If the information is successfully decrypted, the server provides the corresponding resources, preventing the information from being intercepted or tampered with during transmission, thereby further improving the security and reliability of resource access.

[0220] Based on the above embodiments, the following will be combined with Figure 4 , Figure 4 This is a schematic diagram of an interaction process based on the target login mode in an embodiment of this application. As shown in the figure, taking access to cloud resources in a private cloud as an example, specifically:

[0221] In step S1, the user can send an access request through a browser, and the access request can carry the target domain name information.

[0222] In step S2, the access request first reaches the server's Node.js layer. The Node.js layer can determine whether the target login mode is enabled based on the login mode variable and the target field information. If the target login mode is enabled, the login status verification is skipped, and at the same time, "isByPwd=true" can be rendered to the window using the EJS template engine. If the target login mode is not enabled, the user is redirected to the login page.

[0223] In step S3, the Node.js layer calls a series of backend interfaces to obtain the access information and account information of the currently logged-in user. After aggregating the data, it mounts it to the window directory via the EJS template engine. The EJS template engine then loads the static resources required by the micro-frontend and returns Hypertext Markup Language (HTML) to the browser.

[0224] In step S4, the browser receives the HTML and renders the page, while simultaneously loading the micro-frontend resources.

[0225] In step S5, after the micro-frontend resources are loaded, the value of the login mode variable (i.e., "isByPwd") put in step S2 is retrieved from the window during page initialization. If it is the first variable value, the JavaScript software development kit (js-sdk) resources for passwordless login are loaded, thereby rendering the bound user interface.

[0226] In step S6, after the js-sdk resources are loaded, an information viewing control on the page will be rendered. This information viewing control can be represented as a floating button that displays the account information of the current visitor. In other words, the display of the information viewing control indicates that the target login mode has been enabled.

[0227] In step S7, the API function set (XmlHttpRequest) is intercepted at the main entry and exit point of the HTTP request. All request domains sent to the cloud API are rewritten to include target domain information.

[0228] In step S8, when the business sends a cloud API request, since the domain name information has already been rewritten, the domain name of the cloud API request with the target login mode enabled will be changed to the target domain name information containing the target field information. The rewritten cloud API requests will also directly reach the Node.js layer.

[0229] In step S9, when sending a cloud API request, the browser retrieves the current visitor's secretID and secretKey from localStorage, inserts them into the cookie along with the request, and then transmits the cookie to the node.js layer.

[0230] In step S10, after the request reaches the Node.js layer, the secretID and secretKey are retrieved from the cookie in the Node.js layer. If the cookie does not carry the secretID and secretKey, the configured default secretID and default secretKey are used.

[0231] In step S11, the secretID, secretKey, and request payload are combined into a request query. Then, the request query is sent to the cloud API as an HTTP request body via form submission.

[0232] In step S12, the target resource is returned via the cloud API, and after data processing, it can be displayed on the front-end browser.

[0233] Based on the above introduction, the resource access method in this application will be described from the perspective of the terminal device. Please refer to [link / reference]. Figure 5 In this application, the resource access method can be completed independently by the terminal device, independently by the server, or jointly by the terminal device and the server. This application includes:

[0234] 310. In response to a domain name input operation, a first access request is sent to the server so that the server, when the target login mode is enabled, obtains the first target resource associated with the first domain name information according to the first resource request. The first access request carries the first domain name information, the first resource request is generated based on the first access request and the first access information, the first access information is information pre-stored in the server, or the first access information is information carried by the terminal device in the first cookie and transmitted to the server.

[0235] In one or more embodiments, a user can enter domain name information through a browser provided by a terminal device, thereby triggering a first access request. This first access request carries first domain name information, which may specifically be the main domain name. The server (e.g., a local server) receives the first access request sent by the terminal device through a Node.js layer. If the target login mode (i.e., passwordless login mode) is enabled, the first access information of the first accessing party can be directly obtained. This first access information includes the first accessing party's secretID and secretKey.

[0236] It should be noted that the method by which the server obtains the first access information has been described in the foregoing embodiments, so it will not be repeated here.

[0237] Specifically, the server (e.g., a local server) can determine the resources associated with the first domain name information carried in the first access request. Therefore, the server generates a first resource request by combining the addresses of these resources with the first access information. In response to the first resource request, the server (e.g., a cloud server) invokes the resource corresponding to the first access information (i.e., the first target resource) based on the resource address carried in the first resource request, and then sends the first target resource to the server (e.g., the local server) via an API (e.g., a CAPI).

[0238] 320. Receive the first target resource sent by the server;

[0239] In one or more embodiments, a terminal device receives a first target resource associated with a first domain name information sent by a server (e.g., a local server).

[0240] 330. Render and display the first target resource.

[0241] In one or more embodiments, the terminal device renders the first target resource and displays it on the corresponding browser interface.

[0242] This application provides a method for resource access. Using this method, when the target login mode is enabled, the server can obtain the user's access information locally, or the server can receive access information sent by the terminal device via a cookie, which can store the access information of the most recent visitor. Therefore, for the visitor, access to resources corresponding to the appropriate permissions can be obtained without entering a login environment, thereby improving resource access efficiency.

[0243] Optionally, in the above Figure 3 Based on the corresponding embodiments, another optional embodiment provided in this application may further include:

[0244] In response to the domain name input operation, a second access request is sent to the server so that the server can obtain the second target resource associated with the second domain name information according to the second resource request when the target login mode has been enabled. The second access request carries the second domain name information, and the second resource request is generated based on the second access request and the first access information. The first access information is information carried by the terminal device in the second cookie and transmitted to the server.

[0245] Receive the second target resource sent by the server;

[0246] Render and display the second target resource.

[0247] In one or more embodiments, a method is described that supports users switching access in different version environments. As can be seen from the foregoing embodiments, users can trigger an access request by entering domain name information through a browser provided by their terminal device. It should be noted that the method of triggering the first access request is similar to that of triggering the second access request; the method of triggering the second access request will be described below with reference to the figures.

[0248] Specifically, for ease of understanding, please refer to Figure 6 , Figure 6 This is a schematic diagram of a resource access page in an embodiment of this application. As shown in the figure, A1 indicates the account information currently used by the user, such as "Zhang San". A2 indicates the domain name information input area. For example, if the target login mode is controlled based on a login mode variable, the user can enter the second domain name information, i.e., "xxxxx.com". For example, if the target login mode is controlled based on target field information, the user can enter both the second domain name information and the target field information, i.e., "standalone.xxxxx.com".

[0249] The account information indicated by A1 serves as the account information of the first access party, and this account information is bound to the first access information. Taking Table 1 as an example, the account information "Zhang San" corresponds to the first access information composed of secretID and secretKey. When the first access party enters the second domain name information in the domain name information input area, or when the first access party enters both the second domain name information and the target field information in the domain name information input area, a second access request is sent to the server through the browser. The server first generates a second resource request based on the second domain name information and the first access information carried in the second access request, and then obtains the second target resource associated with the second domain name information based on the second resource request. Thus, the terminal device receives the second target resource sent by the server and renders and displays it.

[0250] It should be noted that, in one scenario, the initial access information can be added to the second cookie with the request and sent to the server's Node.js layer via the browser. In another scenario, if the user does not change their access identity, the server can directly use the most recently used access information (e.g., the initial access information).

[0251] Secondly, this application provides a method to support users switching between different version environments. Through this method, the same user can also log in without a password in different version environments. Therefore, it is well-suited for development environments, thereby improving the efficiency of user switching between version environments.

[0252] Optionally, in the above Figure 3Based on the corresponding embodiments, another optional embodiment provided in this application may further include:

[0253] In response to the selection operation of the information viewing control, the account information and the corresponding switching control are displayed. The account information is bound to the second access information, which includes the identity information and key information of the second access party.

[0254] In response to the selection operation of the switching control, a third cookie is sent to the server so that the server can obtain the third target resource associated with the first domain information according to the third resource request when the target login mode is enabled. The third cookie carries the second access information, and the third resource request is generated based on the first access request and the second access information.

[0255] Receive third-party target resources sent by the server;

[0256] Render and display the third target resource.

[0257] In one or more embodiments, a method is described that supports users switching between different system resources for access. As can be seen from the foregoing embodiments, users can also switch between different identities to access resources.

[0258] Specifically, for ease of understanding, please refer to Figure 7 , Figure 7 This is another schematic diagram of the resource access page in the embodiments of this application, such as... Figure 7 As shown in Figure (A), B1 indicates an information viewing control, which can be represented as a floating button displaying the account information of the currently accessing user. When the user selects the information viewing control indicated by B1, the following will be displayed: Figure 7 The interface is shown in Figure (B). B2 indicates the user list; understandably, if a user has not bound access information, an empty user list is displayed. B3 indicates account information, for example, "Li Si". B4 indicates the switching control corresponding to the account information, for example, the switching control for the account information "Li Si". The account information is bound to second access information, which includes the identity information and key information of the second access party. Taking Table 1 as an example, the account information "Li Si" corresponds to the second access information consisting of secretID and secretKey.

[0259] When a user clicks the toggle control indicated by B4, the browser sends an access toggle request to the server, along with a third cookie carrying second access information. The server then generates a third resource request based on the first and second access information, and retrieves the third target resource associated with the first domain name based on the third resource request. The terminal device then receives the third target resource sent by the server and renders and displays it.

[0260] It should be noted that after the user clicks to switch controls, the entire page will be refreshed, and the user will access the environment with the updated user identity.

[0261] Secondly, this application provides a method to support users switching between different system resources for access. Through this method, different users can log in without a password within the same environment. Therefore, it is well-suited for scenarios where multiple different users access resources, thereby improving the efficiency of users switching access identities.

[0262] Optionally, in the above Figure 3 Based on the corresponding embodiments, another optional embodiment provided in this application may further include:

[0263] In response to an information addition operation, the information entry area is displayed;

[0264] In response to input operations in the information entry area, the accessor's account information, identity information, and key information are saved locally.

[0265] In one or more embodiments, a method for proactively adding visitor-related information is described. As can be seen from the foregoing embodiments, users can also add information corresponding to the visitor, including but not limited to account information, secretID, and secretKey.

[0266] Specifically, for ease of understanding, please refer to Figure 8 , Figure 8 This is another schematic diagram of the resource access page in the embodiments of this application, such as... Figure 8 As shown in Figure (A), C1 is used to indicate the addition of a control. When the user clicks the control indicated by C1, the information addition operation is triggered. This results in the following display: Figure 8The interface shown in Figure (B) is as follows: C2 indicates the information entry area, where users can enter the access party's account information, identity information, and key information. C3 indicates the confirm control; when the user clicks the confirm control after entering the information, the account information, secretID, and secretKey are saved in the browser's local storage, and the list of bound users is refreshed. C4 indicates the cancel control; when the user clicks the cancel control, they exit the information input interface.

[0267] Secondly, this application provides a method for proactively adding access-related information. Through this method, users can add account information, identity information, and key information to the user list according to their actual needs, so that users can directly select the corresponding identity from the user list for access later, thereby achieving flexibility in information processing.

[0268] Optionally, in the above Figure 3 Based on the corresponding embodiments, another optional embodiment provided in this application may further include:

[0269] In response to the information deletion operation, the visitor's account information, identity information, and key information are deleted from the browser's local storage.

[0270] In one or more embodiments, a method for actively deleting access-related information is described. As can be seen from the foregoing embodiments, users can also delete access-related information, including but not limited to account information, secretID, and secretKey.

[0271] Specifically, for ease of understanding, please refer to Figure 9 , Figure 9 This is another schematic diagram of the resource access page in the embodiments of this application, such as... Figure 9 As shown in Figure (A), D1 is used to indicate the delete control. When the user clicks the delete control indicated by D1, the information deletion operation is triggered. For example, if the user clicks the delete control corresponding to the account information "Li Si", the following will be displayed: Figure 9 The interface shown in Figure (B) shows that the secretID and secretKey corresponding to the account information "Li Si" will be deleted from the browser's local storage.

[0272] Secondly, this application provides a method for proactively deleting access-related information. Using this method, users can delete account information, identity information, and key information displayed in the user list according to their actual needs, avoiding the impact of useless information on the interface display and thus achieving flexibility in information processing.

[0273] The resource access device in this application is described in detail below. Please refer to [link / reference]. Figure 10 , Figure 10 This is a schematic diagram of one embodiment of the resource access device in this application. The resource access device 40 includes:

[0274] The receiving module 410 is used to receive a first access request sent by the terminal device, wherein the first access request carries first domain name information;

[0275] The acquisition module 420 is used to respond to the first access request. If the target login mode has been enabled, it acquires the first access information of the first access party. The first access information is information pre-stored in the server, or the first access information is information carried by the terminal device in a first small text file cookie and transmitted to the server.

[0276] The generation module 430 is used to generate a first resource request based on the first access request and the first access information;

[0277] The acquisition module 420 is also used to respond to the first resource request and acquire the first target resource associated with the first domain name information;

[0278] The sending module 440 is used to send the first target resource to the terminal device.

[0279] This application provides a resource access device. Using this device, when a target login mode is enabled, the server can obtain the user's access information locally, or the server can receive access information sent by the terminal device via a cookie, which can store the access information of the most recent visitor. Therefore, for the visitor, access to resources corresponding to the appropriate permissions can be obtained without entering a login environment, thereby improving resource access efficiency.

[0280] Optionally, in the above Figure 10 Based on the corresponding embodiments, in another embodiment of the resource access device 40 provided in this application, the resource access device 40 further includes a determination module 450;

[0281] The determination module 450 is used to determine that the target login mode has been enabled if the first access request sent by the terminal device also carries target field information after receiving the first access request. The target field information and the first domain name information are used to form the target domain name information.

[0282] The determination module 450 is also used to determine that the target login mode is not enabled if the first access request does not carry target field information after receiving the first access request sent by the terminal device.

[0283] or,

[0284] The determination module 450 is also used to determine that the target login mode has been enabled if the value of the variable corresponding to the login mode variable is the first variable value after receiving the first access request sent by the terminal device.

[0285] The determination module 450 is also used to determine that the target login mode is not enabled if the value of the variable corresponding to the login mode variable is the second variable value after receiving the first access request sent by the terminal device.

[0286] This application provides a resource access device. Using this device, in one scenario, a passwordless login mode can be directly enabled by specifying domain name information; that is, resources in the system can be directly accessed through a specific domain name, avoiding the cumbersome operations associated with login. In another scenario, a passwordless login mode can be enabled through backend variables; that is, relevant personnel can control whether to enable the passwordless login mode according to actual needs, thereby improving the feasibility and flexibility of the solution.

[0287] Optionally, in the above Figure 10 Based on the corresponding embodiments, in another embodiment of the resource access device 40 provided in this application,

[0288] The determination module 450 is also used to determine that after receiving the first access request sent by the terminal device, if the first access request also carries target field information and the value of the variable corresponding to the login mode variable is the first variable value, then the target login mode has been enabled.

[0289] The determination module 450 is also used to determine that, after receiving the first access request sent by the terminal device, if the first access request also carries target field information and the value of the variable corresponding to the login mode variable is the value of the second variable, then the target login mode is determined not to be enabled.

[0290] The determination module 450 is also used to determine that the target login mode has been enabled if, after receiving the first access request sent by the terminal device, the first access request does not carry target field information and the value of the variable corresponding to the login mode variable is the first variable value.

[0291] The determination module 450 is also used to determine that the target login mode is not enabled if, after receiving the first access request sent by the terminal device, the first access request does not carry target field information and the value of the variable corresponding to the login mode variable is the value of the second variable.

[0292] This application provides a resource access device. Using this device, the decision to enable passwordless login mode is primarily based on backend variable control. Therefore, relevant personnel have higher control authority and can control whether to enable passwordless login mode according to actual needs, thereby improving the feasibility and flexibility of the solution.

[0293] Optionally, in the above Figure 10 Based on the corresponding embodiments, in another embodiment of the resource access device 40 provided in this application,

[0294] The acquisition module 420 is specifically used to acquire first access information from the server, wherein the first access information includes the identity information and key information of the first accessing party.

[0295] This application provides a resource access device. Using this device, access information can be pre-set as default access information. Based on this, different users can access the same resources without logging into the system, thereby improving the efficiency of system resource access.

[0296] Optionally, in the above Figure 10 Based on the corresponding embodiments, in another embodiment of the resource access device 40 provided in this application,

[0297] The acquisition module 420 is specifically used to receive a first cookie sent by the terminal device, wherein the first cookie carries first access information, wherein the first access information includes the identity information and key information of the first accessing party;

[0298] Retrieve the first access information from the first cookie.

[0299] This application provides a resource access device. Using this device, different users pre-configure their access information. Based on this, different users can access different resources without logging into the system. This not only improves the efficiency of system resource access but also allows for setting different access permissions for different users, thus achieving flexibility in resource access.

[0300] Optionally, in the above Figure 10 Based on the corresponding embodiments, in another embodiment of the resource access device 40 provided in this application,

[0301] The receiving module 410 is further configured to receive a second access request sent by the terminal device after sending the first target resource to the terminal device, wherein the second access request carries second domain name information;

[0302] The receiving module 410 is also configured to respond to the second access request, and if the target login mode has been enabled, receive the second cookie sent by the terminal device, wherein the second cookie carries the first access information, wherein the first access information includes the identity information and key information of the first accessing party;

[0303] The generation module 430 is also used to generate a second resource request based on the second access request and the first access information;

[0304] The acquisition module 420 is also used to acquire the second target resource associated with the second domain name information in response to the second resource request;

[0305] The sending module 440 is also used to send a second target resource to the terminal device.

[0306] This application provides a resource access device. Using this device, the same user can perform passwordless login in different version environments. Therefore, it is well-suited for development environments, thereby improving the efficiency of user switching between version environments.

[0307] Optionally, in the above Figure 10 Based on the corresponding embodiments, in another embodiment of the resource access device 40 provided in this application,

[0308] The receiving module 410 is further configured to, after sending the first target resource to the terminal device, if the terminal device responds to the access switching request, receive the third cookie sent by the terminal device if the target login mode has been enabled, wherein the third cookie carries second access information, wherein the second access information includes the identity information and key information of the second accessing party.

[0309] The generation module 430 is also used to generate a third resource request based on the first access request and the second access information;

[0310] The acquisition module 420 is also used to respond to a third resource request and acquire a third target resource associated with the first domain name information;

[0311] The sending module 440 is also used to send a third target resource to the terminal device.

[0312] This application provides a resource access device. Using this device, different users can log in without a password within the same environment. Therefore, it is well-suited for scenarios where multiple different users access resources, thereby improving the efficiency of users switching access identities.

[0313] Optionally, in the above Figure 10 Based on the corresponding embodiments, in another embodiment of the resource access device 40 provided in this application,

[0314] The generation module 430 is specifically used to generate an interface call request based on the first access request, wherein the interface call request is used to request to call the application programming interface (API).

[0315] Based on the API call request and the first access information, generate the first resource request;

[0316] The acquisition module 420 is specifically used to call the API to obtain the first target resource associated with the first domain name information.

[0317] This application provides a resource access device. Using this device, before generating a resource request, the interface call request can be automatically rewritten, ensuring that each interface call request meets the conditions for passwordless access, thereby guaranteeing the feasibility and operability of the solution.

[0318] Optionally, in the above Figure 10 Based on the corresponding embodiments, in another embodiment of the resource access device 40 provided in this application,

[0319] The generation module 430 is specifically used to encapsulate the interface call request and the first access information to obtain the first resource request;

[0320] The acquisition module 420 is specifically used to call the API to parse the first resource request and obtain the first access information to be verified, wherein the first access information to be verified includes the identity information to be verified and the key information to be verified.

[0321] If the identity information to be verified matches the pre-stored identity information, and the key information to be verified matches the pre-stored key information, and the identity information to be verified and the key information to be verified are successfully matched, then the first target resource associated with the first domain name information is obtained.

[0322] This application provides a resource access device. Using this device, the server calls an API to verify the received access information, specifically verifying the consistency and accuracy of the key information and identity information, preventing information from being intercepted or tampered with during transmission, thereby improving the security and reliability of resource access.

[0323] Optionally, in the above Figure 10 Based on the corresponding embodiments, in another embodiment of the resource access device 40 provided in this application,

[0324] The generation module 430 is specifically used to obtain the key information of the first accessing party from the first access information;

[0325] The API call request is encrypted using the key information of the first access party to obtain the encrypted API call request;

[0326] The encrypted interface call request and the identity information of the first accessing party are encapsulated to obtain the first resource request;

[0327] The acquisition module 420 is specifically used to call the API to parse the first resource request and obtain the encrypted interface call request and the identity information of the first access party;

[0328] Call the API to obtain the key information of the first accessing party based on the identity information of the first accessing party;

[0329] If the encrypted interface call request is successfully decrypted using the key information of the first access party, the first target resource associated with the first domain name information is obtained.

[0330] This application provides a resource access device. Using this device, the server calls an API to verify the received access information, specifically verifying the consistency and accuracy of the key information and identity information. If the information is successfully decrypted, the corresponding resources are provided, preventing information from being intercepted or tampered with during transmission, thereby further improving the security and reliability of resource access.

[0331] The resource access device in this application is described in detail below. Please refer to [link / reference]. Figure 11 , Figure 11 This is a schematic diagram of one embodiment of the resource access device in this application. The resource access device 50 includes:

[0332] The sending module 510 is used to send a first access request to the server in response to the domain name input operation, so that the server can obtain the first target resource associated with the first domain name information according to the first resource request when the target login mode is enabled. The first access request carries the first domain name information, and the first resource request is generated based on the first access request and the first access information. The first access information is information pre-stored in the server, or the first access information is information carried by the terminal device in a first small text file cookie and transmitted to the server.

[0333] Receiver module 520 is used to receive the first target resource sent by the server;

[0334] Display module 530 is used to render and display the first target resource.

[0335] This application provides a resource access device. Using this device, when a target login mode is enabled, the server can obtain the user's access information locally, or the server can receive access information sent by the terminal device via a cookie, which can store the access information of the most recent visitor. Therefore, for the visitor, access to resources corresponding to the appropriate permissions can be obtained without entering a login environment, thereby improving resource access efficiency.

[0336] Optionally, in the above Figure 11Based on the corresponding embodiments, in another embodiment of the resource access device 50 provided in this application,

[0337] The sending module 510 is also used to send a second access request to the server in response to the domain name input operation, so that the server can obtain the second target resource associated with the second domain name information according to the second resource request when the target login mode has been enabled. The second access request carries the second domain name information, and the second resource request is generated according to the second access request and the first access information. The first access information is the information carried by the terminal device in the second cookie and transmitted to the server.

[0338] The receiving module 520 is also used to receive the second target resource sent by the server;

[0339] The display module 530 is also used to render and display the second target resource.

[0340] This application provides a resource access device. Using this device, the same user can perform passwordless login in different version environments. Therefore, it is well-suited for development environments, thereby improving the efficiency of user switching between version environments.

[0341] Optionally, in the above Figure 11 Based on the corresponding embodiments, in another embodiment of the resource access device 50 provided in this application,

[0342] The display module 530 is also used to respond to the selection operation of the information viewing control, and to display account information and the corresponding switching control of the account information. The account information is bound to the second access information, which includes the identity information and key information of the second access party.

[0343] The sending module 510 is also used to respond to the selection operation for the switching control and send a third cookie to the server so that the server can obtain the third target resource associated with the first domain name information according to the third resource request when the target login mode is enabled. The third cookie carries the second access information, and the third resource request is generated according to the first access request and the second access information.

[0344] The receiving module 520 is also used to receive third target resources sent by the server;

[0345] The display module 530 is also used to render and display the third target resource.

[0346] This application provides a resource access device. Using this device, different users can log in without a password within the same environment. Therefore, it is well-suited for scenarios where multiple different users access resources, thereby improving the efficiency of users switching access identities.

[0347] Optionally, in the above Figure 11 Based on the corresponding embodiments, in another embodiment of the resource access device 50 provided in this application, the resource access device 50 further includes a processing module 540;

[0348] The display module 530 is also used to display the information entry area in response to the information addition operation;

[0349] The processing module 540 is used to respond to input operations for the information entry area and save the accessor's account information, identity information and key information in local storage.

[0350] This application provides a resource access device. Using this device, users can add account information, identity information, and key information to a user list according to their actual needs, so that users can directly select the corresponding identity from the user list for access later, thereby achieving flexibility in information processing.

[0351] Optionally, in the above Figure 11 Based on the corresponding embodiments, in another embodiment of the resource access device 50 provided in this application,

[0352] The processing module 540 is also used to delete the accessor's account information, identity information, and key information from the browser's local storage in response to the information deletion operation.

[0353] This application provides a resource access device. Using this device, users can delete account information, identity information, and key information displayed in the user list according to actual needs, avoiding the impact of useless information on the interface display, thereby achieving flexibility in information processing.

[0354] Figure 12This is a schematic diagram of a server structure provided in an embodiment of this application. The server 600 can vary significantly due to different configurations or performance. It may include one or more central processing units (CPUs) 622 (e.g., one or more processors) and memory 632, and one or more storage media 630 (e.g., one or more mass storage devices) for storing application programs 642 or data 644. The memory 632 and storage media 630 can be temporary or persistent storage. The program stored in the storage media 630 may include one or more modules (not shown in the diagram), each module may include a series of instruction operations on the server. Furthermore, the CPU 622 may be configured to communicate with the storage media 630 and execute the series of instruction operations in the storage media 630 on the server 600.

[0355] Server 600 may also include one or more power supplies 626, one or more wired or wireless network interfaces 650, one or more input / output interfaces 658, and / or one or more operating systems 641, such as Windows Server. TM Mac OS X TM Unix™, Linux TM FreeBSD TM etc.

[0356] The steps performed by the server in the above embodiments can be based on this Figure 12 The server structure shown.

[0357] This application also provides a terminal device, such as... Figure 13 As shown, for ease of explanation, only the parts related to the embodiments of this application are shown. For specific technical details not disclosed, please refer to the method section of the embodiments of this application. In the embodiments of this application, a personal computer is used as an example for illustration:

[0358] Figure 13 This is a block diagram illustrating a portion of the structure of a personal computer related to the terminal device provided in an embodiment of this application. (Reference) Figure 13 The personal computer includes components such as a radio frequency (RF) circuit 710, a memory 720, an input unit 730, a display unit 740, a sensor 750, an audio circuit 760, a wireless fidelity (WiFi) module 770, a processor 780, and a power supply 790. Those skilled in the art will understand that... Figure 13The personal computer architecture shown does not constitute a limitation on the personal computer and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0359] The following is combined Figure 13 A detailed introduction to the various components of a personal computer:

[0360] RF circuit 710 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and processes it with processor 780; additionally, it transmits uplink data to the base station. Typically, RF circuit 710 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier (LNA), and a duplexer. Furthermore, RF circuit 710 can also communicate wirelessly with networks and other devices. The aforementioned wireless communication can use any communication standard or protocol, including but not limited to Global System for Mobile Communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, and Short Message Service (SMS).

[0361] The memory 720 can be used to store software programs and modules. The processor 780 executes various functional applications and data processing of the personal computer by running the software programs and modules stored in the memory 720. The memory 720 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the personal computer (such as audio data, telephone directory, etc.). In addition, the memory 720 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0362] The input unit 730 can be used to receive input numerical or character information, and to generate key signal inputs related to user settings and function control of the personal computer. Specifically, the input unit 730 may include a touch panel 731 and other input devices 732. The touch panel 731, also known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel 731), and drive the corresponding connected devices according to a pre-set program. Optionally, the touch panel 731 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to the processor 780, and can also receive and execute commands sent by the processor 780. In addition, the touch panel 731 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 731, the input unit 730 may also include other input devices 732. Specifically, other input devices 732 may include, but are not limited to, one or more of the following: a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a mouse, and a joystick.

[0363] The display unit 740 can be used to display information input by the user or information provided to the user, as well as various menus of the personal computer. The display unit 740 may include a display panel 741, optionally configured as a liquid crystal display (LCD), organic light-emitting diode (OLED), or similar form. Further, a touch panel 731 may cover the display panel 741. When the touch panel 731 detects a touch operation on or near it, it transmits the information to the processor 780 to determine the type of touch event. Subsequently, the processor 780 provides corresponding visual output on the display panel 741 based on the type of touch event. Although in Figure 13 In this embodiment, the touch panel 731 and the display panel 741 are two separate components to realize the input and output functions of the personal computer. However, in some embodiments, the touch panel 731 and the display panel 741 can be integrated to realize the input and output functions of the personal computer.

[0364] The personal computer may also include at least one sensor 750, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display panel 741 according to the ambient light level, and the proximity sensor can turn off the display panel 741 and / or the backlight when the personal computer is moved to the ear. As a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity and can be used for applications that recognize the posture of the personal computer (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition-related functions (such as pedometers, taps), etc. Other sensors that may be configured in the personal computer, such as gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0365] Audio circuit 760, speaker 761, and microphone 762 provide an audio interface between the user and a personal computer. Audio circuit 760 converts received audio data into electrical signals and transmits them to speaker 761, where speaker 761 converts them into sound signals for output. On the other hand, microphone 762 converts collected sound signals into electrical signals, which are then received by audio circuit 760, converted into audio data, and then processed by processor 780 before being transmitted via RF circuit 710 to, for example, another personal computer, or output to memory 720 for further processing.

[0366] WiFi is a short-range wireless transmission technology. Personal computers using the WiFi module 770 can help users send and receive emails, browse web pages, and access streaming media, providing wireless broadband internet access. Although Figure 13 WiFi module 770 is shown, but it is understood that it is not an essential component of a personal computer and can be omitted as needed without changing the nature of the invention.

[0367] The processor 780 is the control center of the personal computer, connecting various parts of the personal computer through various interfaces and lines. It performs various functions and processes data by running or executing software programs and / or modules stored in the memory 720, and by accessing data stored in the memory 720. Optionally, the processor 780 may include one or more processing units; optionally, the processor 780 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the aforementioned modem processor may also not be integrated into the processor 780.

[0368] The personal computer also includes a power supply 790 (such as a battery) to power various components. Optionally, the power supply can be logically connected to the processor 780 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. Although not shown, the personal computer may also include a camera, Bluetooth module, etc., which will not be described in detail here.

[0369] The steps performed by the terminal device in the above embodiments can be based on this Figure 13 The terminal device structure is shown.

[0370] This application also provides a computer device, including a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, it implements the steps of the methods described in the foregoing embodiments.

[0371] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the methods described in the foregoing embodiments.

[0372] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the methods described in the foregoing embodiments.

[0373] It is understood that in the specific implementation of this application, data such as access information are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0374] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0375] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

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

[0377] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0378] If the integrated unit is implemented as 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 this application, in essence, 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. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a server or terminal device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing computer programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0379] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for accessing resources, characterized in that, include: Receive a first access request sent by a terminal device, wherein the first access request carries first domain name information; In response to the first access request, if the target login mode has been enabled, the first access information of the first access party is obtained, wherein the first access information is information pre-stored in the server, or the first access information is information carried by the terminal device in a first small text file cookie and transmitted to the server. Based on the first access request and the first access information, a first resource request is generated, including: generating an interface call request based on the first access request, wherein the interface call request is used to request to call an application programming interface (API); and generating the first resource request based on the interface call request and the first access information. In response to the first resource request, the API is invoked to obtain the first target resource associated with the first domain name information; Send the first target resource to the terminal device; The step of generating the first resource request based on the interface call request and the first access information includes: Obtain the key information of the first accessing party from the first access information; The interface call request is encrypted using the key information of the first accessing party to obtain an encrypted interface call request; The encrypted interface call request and the identity information of the first accessing party are encapsulated to obtain the first resource request; The step of calling the API to obtain the first target resource associated with the first domain name information includes: The API is invoked to parse the first resource request, thereby obtaining the encrypted interface call request and the identity information of the first accessing party; Call the API to obtain the key information of the first accessing party based on the identity information of the first accessing party; If the encrypted interface call request is successfully decrypted using the key information of the first access party, the first target resource associated with the first domain name information is obtained.

2. The method according to claim 1, characterized in that, After receiving the first access request sent by the receiving terminal device, the method further includes: If the first access request also carries target field information, then it is determined that the target login mode has been enabled, wherein the target field information and the first domain name information are used to form target domain name information; If the first access request does not carry the target field information, it is determined that the target login mode is not enabled; or, After receiving the first access request sent by the receiving terminal device, the method further includes: If the value of the variable corresponding to the login mode variable is the first variable value, then it is determined that the target login mode has been enabled. If the value of the variable corresponding to the login mode variable is the second variable value, then it is determined that the target login mode is not enabled.

3. The method according to claim 1, characterized in that, After receiving the first access request sent by the receiving terminal device, the method further includes: If the first access request also carries target field information, and the value of the variable corresponding to the login mode variable is the first variable value, then it is determined that the target login mode has been enabled. If the first access request also carries the target field information, and the value of the variable corresponding to the login mode variable is the second variable value, then it is determined that the target login mode is not enabled. If the first access request does not carry the target field information, and the value of the variable corresponding to the login mode variable is the first variable value, then it is determined that the target login mode has been enabled. If the first access request does not carry the target field information, and the value of the variable corresponding to the login mode variable is the second variable value, then it is determined that the target login mode is not enabled.

4. The method according to claim 1, characterized in that, The step of obtaining the first access information of the first accessing party includes: The first access information is obtained from the server, wherein the first access information includes the identity information and key information of the first accessing party.

5. The method according to claim 1, characterized in that, The step of obtaining the first access information of the first accessing party includes: The terminal device sends a first cookie, wherein the first cookie carries the first access information, wherein the first access information includes the identity information and key information of the first accessing party; Retrieve the first access information from the first cookie.

6. The method according to claim 1, characterized in that, After sending the first target resource to the terminal device, the method further includes: Receive a second access request sent by the terminal device, wherein the second access request carries second domain name information; In response to the second access request, if the target login mode has been enabled, a second cookie sent by the terminal device is received, wherein the second cookie carries the first access information, wherein the first access information includes the identity information and key information of the first accessing party; A second resource request is generated based on the second access request and the first access information; In response to the second resource request, obtain the second target resource associated with the second domain name information; The second target resource is sent to the terminal device.

7. The method according to claim 1, characterized in that, After sending the first target resource to the terminal device, the method further includes: If the terminal device responds to the access switching request, and the target login mode is already enabled, the terminal device receives a third cookie sent by the terminal device, wherein the third cookie carries second access information, wherein the second access information includes the identity information and key information of the second accessing party. Based on the first access request and the second access information, a third resource request is generated; In response to the third resource request, obtain the third target resource associated with the first domain name information; The third target resource is sent to the terminal device.

8. The method according to claim 1, characterized in that, The step of generating a first resource request based on the interface call request and the first access information includes: The interface call request and the first access information are encapsulated to obtain the first resource request; The step of calling the API to obtain the first target resource associated with the first domain name information includes: The API is invoked to parse the first resource request and obtain the first access information to be verified, wherein the first access information to be verified includes identity information to be verified and key information to be verified. If the identity information to be verified is consistent with the pre-stored identity information, and the key information to be verified is consistent with the pre-stored key information, and the identity information to be verified and the key information to be verified are successfully matched, then the first target resource associated with the first domain name information is obtained.

9. A method for accessing a resource, characterized in that, include: In response to a domain name input operation, a first access request is sent to the server, so that the server, with the target login mode enabled, can obtain a first target resource associated with the first domain name information according to the first resource request. The first access request carries the first domain name information, and the first resource request is generated based on the first access request and first access information. The first access information is pre-stored on the server, or the first access information is information carried by the terminal device in a first small text file cookie and transmitted to the server. The first resource request is generated as follows: an interface call request is generated based on the first access request, the interface call request is used to request an application programming interface (API), and the key information of the first accessing party is obtained from the first access information; the interface call request is encrypted using the key information of the first accessing party to obtain an encrypted interface call request; the encrypted interface call request and the identity information of the first accessing party are encapsulated to obtain the first resource request. The server receives a first target resource, wherein the first target resource is obtained by: calling the API to parse the first resource request to obtain the encrypted interface call request and the identity information of the first access party; calling the API to obtain the key information of the first access party based on the identity information of the first access party; if the encrypted interface call request is successfully decrypted using the key information of the first access party, then the first target resource associated with the first domain name information is obtained. The first target resource is rendered and displayed.

10. The method according to claim 9, characterized in that, The method further includes: In response to a domain name input operation, a second access request is sent to the server so that the server, when the target login mode is enabled, can obtain a second target resource associated with the second domain name information according to the second resource request. The second access request carries the second domain name information, and the second resource request is generated based on the second access request and the first access information. The first access information is information carried by the terminal device in the second cookie and transmitted to the server. Receive the second target resource sent by the server; The second target resource is rendered and displayed.

11. The method according to claim 9, characterized in that, The method further includes: In response to a selection operation of the information viewing control, the system displays account information and a corresponding switching control for the account information, wherein the account information is bound to second access information, and the second access information includes the identity information and key information of the second accessing party; In response to the selection operation of the switching control, a third cookie is sent to the server so that the server can obtain a third target resource associated with the first domain name information according to a third resource request when the target login mode is enabled. The third cookie carries second access information, and the third resource request is generated based on the first access request and the second access information. Receive the third target resource sent by the server; The third target resource is rendered and displayed.

12. The method according to any one of claims 9 to 11, characterized in that, The method further includes: In response to an information addition operation, the information entry area is displayed; In response to input operations in the information entry area, the accessor's account information, identity information, and key information are saved in local storage.

13. The method according to any one of claims 9 to 11, characterized in that, The method further includes: In response to the information deletion operation, the visitor's account information, identity information, and key information are deleted from the browser's local storage.

14. A resource access device, characterized in that, include: The receiving module is used to receive a first access request sent by the terminal device, wherein the first access request carries first domain name information; The acquisition module is used to respond to the first access request. If the target login mode has been enabled, the module acquires the first access information of the first access party. The first access information is pre-stored in the information of the server, or the first access information is information carried by the terminal device in a first small text file cookie and transmitted to the server. A generation module is configured to generate a first resource request based on the first access request and the first access information, including: generating an interface call request based on the first access request, wherein the interface call request is used to request to call an application programming interface (API); and generating the first resource request based on the interface call request and the first access information. The acquisition module is further configured to respond to the first resource request by calling the API to acquire the first target resource associated with the first domain name information; The sending module is used to send the first target resource to the terminal device; Specifically, the generation module is used for: Obtain the key information of the first accessing party from the first access information; The interface call request is encrypted using the key information of the first accessing party to obtain an encrypted interface call request; The encrypted interface call request and the identity information of the first accessing party are encapsulated to obtain the first resource request; The acquisition module is specifically used for: The API is invoked to parse the first resource request, thereby obtaining the encrypted interface call request and the identity information of the first accessing party; Call the API to obtain the key information of the first accessing party based on the identity information of the first accessing party; If the encrypted interface call request is successfully decrypted using the key information of the first access party, the first target resource associated with the first domain name information is obtained.

15. The apparatus according to claim 14, characterized in that, The device also includes a determining module; The determining module is configured to, after receiving a first access request sent by a terminal device, determine that the target login mode has been enabled if the first access request also carries target field information, wherein the target field information and the first domain name information are used to form target domain name information; and determine that the target login mode has not been enabled if the first access request does not carry the target field information. or, The determining module is further configured to, after receiving the first access request sent by the terminal device, determine that the target login mode has been enabled if the value of the variable corresponding to the login mode variable is a first variable value; and determine that the target login mode has not been enabled if the value of the variable corresponding to the login mode variable is a second variable value.

16. The apparatus according to claim 14, characterized in that, The device further includes a determining module, the determining module being configured to: After receiving the first access request sent by the terminal device, if the first access request also carries target field information, and the value of the variable corresponding to the login mode variable is the first variable value, then it is determined that the target login mode has been enabled. After receiving the first access request sent by the terminal device, if the first access request also carries the target field information, and the variable value corresponding to the login mode variable is the second variable value, then it is determined that the target login mode has not been enabled. After receiving the first access request sent by the terminal device, if the first access request does not carry the target field information, and the value of the variable corresponding to the login mode variable is the first variable value, then it is determined that the target login mode has been enabled. After receiving the first access request sent by the terminal device, if the first access request does not carry the target field information, and the value of the variable corresponding to the login mode variable is the second variable value, then it is determined that the target login mode is not enabled.

17. A resource access device, characterized in that, include: A sending module is configured to respond to a domain name input operation by sending a first access request to a server, so that the server, when the target login mode is enabled, can obtain a first target resource associated with the first domain name information according to the first resource request. The first access request carries the first domain name information, and the first resource request is generated based on the first access request and first access information. The first access information is information pre-stored on the server, or the first access information is information carried by a terminal device in a first small text file cookie and transmitted to the server. The first resource request is generated as follows: an interface call request is generated based on the first access request, the interface call request is used to request an application programming interface (API), and the key information of the first accessing party is obtained from the first access information; the interface call request is encrypted using the key information of the first accessing party to obtain an encrypted interface call request; the encrypted interface call request and the identity information of the first accessing party are encapsulated to obtain the first resource request. The receiving module is configured to receive a first target resource sent by the server, wherein the first target resource is obtained by: calling the API to parse the first resource request to obtain the encrypted interface call request and the identity information of the first access party; calling the API to obtain the key information of the first access party based on the identity information of the first access party; and if the encrypted interface call request is successfully decrypted using the key information of the first access party, then the first target resource associated with the first domain name information is obtained. The display module is used to render and display the first target resource.

18. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 8, or implements the steps of the method according to any one of claims 9 to 13.

19. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 8, or implements the steps of the method according to any one of claims 9 to 13.

20. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 8, or implements the steps of the method according to any one of claims 9 to 13.

Images