CN115499214A - Access method, device and storage medium - Google Patents

Abstract

The application discloses an access method, device and storage medium, which relate to the field of access authentication and are used to reduce the network transmission process and improve user experience. The method includes: the first server receives the first access request sent by the first terminal; wherein, the first access request includes the information to be authenticated of the target account, which is used to request access to the target content of the first server; the target account is the second platform user account, the first server is the server of the first platform; the first server contains the target plug-in; the target plug-in is used to authenticate the target account of the second platform; when the authentication logic contained in the target plug-in does not need to confirm whether the target account is the second When registering an account on the platform, the first server authenticates the to-be-authenticated information based on the target plug-in; the first server sends a first response message to the first terminal when the to-be-authenticated information is authenticated; wherein, the first response message is used to indicate target content.

Description

An access method, device and storage medium

technical field

The present application relates to the field of access authentication, in particular to an access method, device and storage medium.

Background technique

In the client/server (client/server, CS) or browser/server (browser/server, BS) architecture, the authentication of the account information to be authenticated is an important link to ensure that data and resources can only be accessed by specific Account usage, but when an account on one platform needs to use resources on another platform, accessing between different platforms is a troublesome issue. Since these platforms may belong to different departments of different companies, there are differences in the platform certification logic, and it is more troublesome to unify the certification of these platforms. The traditional method is to configure an authentication server, and store the information to be authenticated (such as account and password) of the accessed platform in the authentication server. When an account on a platform needs to access resources on other platforms, it needs to be authenticated through the authentication server. During the authentication process, both the accessing platform and the accessed platform need to communicate with the authentication server through the network. Depending on the network conditions, the waiting time may be long or short, and the user experience is not friendly.

Contents of the invention

The present application provides an access method, device and storage medium, which are used to reduce the network transmission process and improve user experience.

In order to achieve the above-mentioned technical purpose, the application adopts the following technical solutions:

In the first aspect, the embodiment of the present application provides an access method, the method includes: the first server receives the first access request sent by the first terminal; wherein, the first access request includes the information to be authenticated of the target account, for requesting access to the target content of the first server; the target account is an account of a user of the second platform, and the first server is a server of the first platform; the first server includes a target plug-in; the target plug-in is used to authenticate the target account of the second platform; When the authentication logic contained in the target plug-in does not need to confirm whether the target account is a registered account of the second platform, the first server authenticates the to-be-authentication information based on the target plug-in; The terminal sends a first response message; wherein, the first response message is used to indicate target content.

It can be understood that the authentication process is completed by calling the target plug-in from the first server, and the first server may not communicate with the second server on the second platform, so as to reduce the network transmission process, avoid slow authentication due to network delay, and provide a better user experience . At the same time, the authentication process and the second platform can achieve zero coupling, without interdependence and interference, and increase system stability.

The above method is described by taking the second platform accessing the first platform as an example. Similarly, if the authentication plug-in of the second platform is exported to the first platform, the first platform can also access the second platform. The two platforms provide plug-ins with consistent specifications to each other, enabling low-cost access to each other. When there are multiple platforms, setting up standardized and consistent plug-ins together can allow multiple platforms to achieve low-cost docking and greatly reduce labor costs.

In one implementation, when the authentication logic contained in the target plug-in needs to confirm whether the target account is a registered account of the second platform, the above-mentioned first server authenticates the authentication information based on the target plug-in, including: the first server sends the second server Sending a request message, the request message is used to request whether the authentication target account is a registered account of the second platform; the second server is a server of the second platform; the first server receives the second response message; the second response message is used to indicate the authentication result; When the authentication result indicates that the target account is a registered account of the second platform, the first server authenticates the information to be authenticated based on the target plug-in in the first server.

It can be understood that when the authentication logic of the target function includes the need to confirm whether the target account is a registered account of the second platform, the second server of the second platform needs to call the account database to check the registered account. This process shows that the scheme proposed in the embodiment of the present application can contain various authentication logics, and can be implemented under a complex business platform to meet different authentication requirements.

In another implementation manner, the first server receiving the first access request sent by the first terminal includes: the first server receiving the first access request sent by the first terminal through a uniform resource location system URL.

It can be understood that, when the first terminal sends an access request to the first server through the URL, it can quickly locate the first server according to the address information of the first server carried in the URL, thereby improving the sending efficiency.

In another implementation, before the first server authenticates the information to be authenticated based on the target plugin, the method further includes: selecting a target plugin from multiple plugins; the target plugin is a plugin that complies with the authentication logic of the information to be authenticated.

It can be understood that there may be multiple plug-ins in the first server, and only plug-ins consistent with the authentication logic of the information to be authenticated can authenticate the information to be authenticated. Therefore, in order to improve authentication efficiency and make authentication results accurate, it is necessary to first select a target plug-in from multiple plug-ins, and use the target plug-in to authenticate the authentication information.

In another implementation manner, after sending the first response message to the first terminal, the method further includes: within a preset time, the first server receives a second access request sent by the first terminal; the second access request is used to Access to the target content of the first server is requested; the first server sends a third response message to the first terminal; the third response message is used to indicate the target content.

It can be understood that when the first server receives the second access request sent by the same account from the first terminal within a preset time after the first server sends the first response message to the first terminal, the first server may There is no need to authenticate the same account again. This setting can avoid resource waste caused by repeated authentication, save time and improve efficiency.

In a second aspect, the present application provides an access device. The access device includes various modules applied to the method of the first aspect or any possible design manner of the first aspect.

In a third aspect, the present application provides an access device, including a memory and a processor. A memory is coupled to the processor; the memory is used to store computer program code, which includes computer instructions. When the processor executes the computer instruction, the access device is made to execute the volume adjustment method according to the first aspect and any possible design manner thereof.

In a fourth aspect, the present application provides a computer-readable storage medium, where the computer-readable storage medium includes computer instructions. Wherein, when the computer instructions run on the access device, the access device is made to execute the access method according to the first aspect and any possible design manner thereof.

In a fifth aspect, the present application provides a computer program product, where the computer program product includes computer instructions. Wherein, when the computer instructions run on the access device, the access device is made to execute the access method according to the first aspect and any possible design manner thereof.

For the specific description of the second aspect to the fifth aspect and its various implementations in this application, you can refer to the detailed description in the first aspect and its various implementations; and, the second to the fifth aspect and its various implementations For the beneficial effects of the manner, reference may be made to the first aspect and the analysis of beneficial effects in various implementation manners thereof, and details are not repeated here.

These or other aspects of the present application will be more clearly understood in the following description.

Description of drawings

FIG. 1 is an access flowchart when the account of the first terminal of platform A accesses the first server of platform B;

FIG. 2 is a schematic diagram of an implementation environment involved in an access method provided by an embodiment of the present application;

FIG. 3 is a flow chart of an access method provided by an embodiment of the present application;

FIG. 4 is an implementation process diagram of an authentication step provided by the embodiment of the present application;

FIG. 5 is a schematic structural diagram of an access device provided by an embodiment of the present application;

FIG. 6 is a schematic structural diagram of another access device provided by an embodiment of the present application.

detailed description

Hereinafter, the terms "first", "second" and "third" etc. are used for descriptive purposes only, and cannot be understood as indicating or implying relative importance or implicitly specifying the quantity of indicated technical features. Thus, a feature defined as "first", "second" or "third" etc. may expressly or implicitly include one or more of such features.

In the CS/BS architecture, authentication of account information to be authenticated is an important link to ensure that data and resources can only be used by specific accounts. However, when an account on one platform needs to use resources on another platform, the traditional method It is to configure an authentication server, and store the authentication information of the accessed platform in the authentication server. When an account of a platform needs to access other platforms, it needs to perform identity authentication through the authentication server. The authentication process communicates with the authentication server through the network, according to Depending on the network conditions, the waiting time may be long or short, and the user experience is not friendly; at the same time, this method requires a separate configuration of the authentication server, which is troublesome to install and maintain.

In an example, as shown in FIG. 1 , FIG. 1 is an access process when an account of a first terminal of platform A accesses a first server of platform B. When the user accesses the first server through the account of the first terminal, the first terminal needs to send an authentication request for accessing the first server to the authentication server, and the authentication server encrypts the authentication password of the first server to generate a character string and returns it to the first terminal. After the first terminal receives the character string, it sends the character string and the account information of the user on the first terminal to the first server, and the first server sends the character string to the authentication server to confirm that the character string is generated by the authentication server, After the confirmation is completed, the first server returns the content that the user needs to access to the first terminal. In this process, the authentication password of platform B is configured in the authentication server. The first terminal does not directly obtain the password, but obtains a character string after encrypting the authentication password through the authentication server. Platform B also verifies the character string through the authentication server. During the whole process, platform A and platform B need to communicate with the authentication server for authentication.

Based on this, an embodiment of the present application provides an access method, in which the server of the first platform invokes a plug-in to authenticate the authentication information of the user's account of the second platform. After the first server of the first platform receives the first access request sent by the user of the second platform through the first terminal in the second platform, it calls the plug-in to verify the account of the second platform user included in the access request. The information is authenticated, and when the authentication is passed, the first server of the first platform returns the content accessed by the first access request to the first terminal of the second platform. It can be understood that the authentication process is completed by the first server calling the plug-in, and the first server may not communicate with the second server of the second platform, so as to reduce the network transmission process, avoid slow authentication caused by network delay, and provide better user experience. At the same time, the authentication process and the second platform can achieve zero coupling, without interdependence and interference, and increase system stability.

The implementation of the embodiment of the present application will be described in detail below with reference to the accompanying drawings.

Please refer to FIG. 2. FIG. 2 is a schematic diagram of an implementation environment involved in an access method provided by an embodiment of the present application. The implementation environment includes: a first platform 130 and a second platform 140, wherein the first platform 130 includes at least one A server 100; the second platform 140 includes at least one first terminal 110, and optionally, also includes a second server 120;

Wherein, the first terminal 110 is a terminal of the second platform 140 , the first server 100 is a server of the first platform 130 , and the second server 120 is a server of the second platform 140 . The second platform 140 and the first platform 130 are platforms for processing different businesses, and may belong to different companies, or may belong to different departments of the same company.

The first platform 130 or the second platform 140 may include multiple terminals and multiple servers. In this solution, the first platform 130 includes the first server 100, and the second platform 140 includes the first terminal 110 and the second server 120. .

The first terminal 110 is a device for users to process business on the second platform 140, the first server 100 is a device for authenticating the account for accessing the first platform 130, and optionally, the second server 120 is for the second A device for authenticating the account of the platform 140 .

The first terminal 110 may be a mobile phone, a tablet computer, a desktop, a laptop, a notebook computer, a netbook, etc. The embodiment of the present application does not specifically limit the specific form of the terminal.

In an application scenario, there are two departments in a company, a financial department and an auditing department. The financial system of the financial department is the first platform 130 , and the auditing system of the auditing department is the second platform 140 . The staff member logs into the account on the first terminal 110 of the second platform 140, and when the staff member needs to use the financial settlement data in the first platform 130 of the financial department, the staff member clicks on the first terminal 110 to access the first platform 130 After receiving the access application, the first server 100 of the first platform 130 calls the authentication method in the authentication plug-in that satisfies the authentication logic of the second platform 140, and authenticates the account information to be authenticated contained in the access application, and the authentication passes Afterwards, the first server 100 sends the financial settlement data to the first terminal 110 .

In another application scenario, in the above scenario, after the first server 100 of the first platform 130 receives the access application sent by the first terminal 110 of the second platform 140, it needs to confirm that the staff member logged in on the second platform 140 Whether the account is an account of an employee of the audit department, at this time, the first server 100 sends the account authentication information to the second platform 140 and the second server 120, and the second server 120 saves the logged-in account of the employee and the account database After comparing the employee account information of the audit department, after confirming that the employee's account is an employee account of the audit department, the confirmation information is returned to the first server 100, and the first server 100 authenticates the information to be authenticated of the account.

The following describes the access method provided by the embodiment of this application:

The access method provided in the embodiment of the present application may be applied to the first server 100 . The execution subject of the access method provided in the embodiment of the present application may also be an access device. The access device may be a first server, or an application program (application, APP) installed on the first server to provide an access function, or a central processing unit (central processing unit, CPU) in the first server, or Or it is a control module in the first server for executing the access method. In the following, description will be made by taking the method provided by the embodiment of the present application as the first server as an example.

Please refer to FIG. 3 , which is a flow chart of an access method provided by an embodiment of the present application. As shown in Fig. 3, the method may include S101-S106.

S101: The first terminal sends a target account login request to the second server.

The first terminal is a terminal of the second platform, the second server is a server of the second platform, and the target account is an account of a user of the second platform.

The information related to the target account is stored in the second server database.

S102: The second server receives the target account login request, and returns a target account login interface to the first terminal. The login interface includes the first platform access entry.

The user of the second platform can use the target account to access the first platform through the access portal of the first platform.

The first platform access entry may include a uniform resource location system URL jump link.

S103: The first server receives the first access request sent by the first terminal. Wherein, the first access request includes the information to be authenticated of the target account, and is used to request access to the target content of the first server; the first server is a server of the first platform, and the second platform is different from the first platform.

Specifically: the first server receives the first access request sent by the first terminal through the URL of the uniform resource location system.

Target account: It is the account of the user of the second platform. When the user conducts business processing through the second platform, he needs to log in to his personal account according to the requirements of the second platform. At this time, the target account is the account logged in by the user on the second platform.

Information to be authenticated: may include the account name of the target account, account login password, user role (for example: ordinary user or advanced user), and platform name (for example: second platform), etc.

Target content: the content requested by the user on the first terminal (for example: homepage or shared folder).

Platform: It is a virtual platform that connects isolated terminals or servers together through physical links to form a data link, so as to achieve the purpose of resource sharing and communication. Different platforms have different capabilities and features. In an example, for a company, the platform may be a business platform for processing company business; or, the platform may be a resource sharing platform for storing information of various departments of the company. In another example, for the network, the platform may use the network as a carrier for communication or resource sharing software, such as Weibo, QQ or Email.

The second platform and the first platform can be different platforms of different departments of the same company, or different platforms of different companies. When users of the second platform want to access the resources of the first platform, they can click the The URL jump link of the access portal of a platform, at this time, the first terminal sends a first access request to the first server of the first platform, and the request is used to access the first platform. The first access request includes user account information and desired content information.

S104: The first server selects a target plug-in from multiple plug-ins; the target plug-in is a plug-in conforming to authentication logic of the information to be authenticated. The target plug-in is used to authenticate the information to be authenticated of the target account of the second platform.

Authentication logic: It is a logic that can be customized to authenticate the information to be authenticated. For example: the authentication logic can be customized as a logic that sequentially authenticates the target account's account name, account login password, user role (for example: common user or advanced user) and platform name (for example: second platform), Different user roles can have different access rights; or can be customized as the account name, account login password, user role (for example: ordinary user or advanced user) and platform name (for example: second platform) of the target account A logic that waits for part of the content to be authenticated. Generally, the account name and account login password of the target account are mandatory authentication contents, and others are optional authentication contents according to the authentication logic.

Each platform can contain one or more authentication logics. In one example, different authentication logics can be set for different user roles in the authentication information. For example, the access rights contained in the authentication logic set for ordinary users are ordinary Permissions, the access permissions contained in the authentication logic set for advanced users are advanced permissions, which can be developed according to platform requirements.

Plug-in: A small program that can be run in the software developed according to the authentication logic.

Multiple plug-ins: multiple plug-ins developed according to multiple authentication logics; the multiple plug-ins in the first platform may include plug-ins conforming to the authentication logic of the second platform and plug-ins conforming to the authentication logic of the first platform. Multiple plug-ins are packaged in one file and installed on the first server in advance.

Target plug-in: among multiple plug-ins, the plug-in is consistent with the authentication logic of the information to be authenticated. For example: the multiple plug-ins built in the first server are respectively plug-in 1-plug-in 5, where plug-in 1 is a plug-in that conforms to the authentication logic of ordinary users of the second platform, plug-in 2 is a plug-in that complies with the authentication logic of advanced users of the second platform, and plug-in 3- Plug-in 5 is a plug-in conforming to the authentication logic of the first platform. When the user role contained in the information to be authenticated is an ordinary user, at this time, plug-in 1 is the target plug-in.

When the first server receives the first access request sent by the first terminal, the first server calls the plug-in in turn. When the called plug-in meets the authentication logic of the information to be authenticated, it is the target plug-in; otherwise, continue to call the next plug-in until the target plugin is selected.

S105: The first server authenticates the to-be-authentication information based on the target plug-in.

Specifically, when the authentication logic contained in the target plug-in needs to confirm whether the target account is a registered account, S103 may include the following option 1 or option 2:

Wherein, the registered account is an account whose account information is stored in the database of the second server, that is, the authentication logic contained in the target plug-in needs to confirm whether the target account information is stored in the database of the second server.

Solution 1: When the authentication logic contained in the target plug-in does not need to confirm whether the target account is a registered account, at this time, the first server authenticates the information to be authenticated of the target account based on the target plug-in.

In one example, the authentication logic of the target plug-in is, for example, the account name of the target account, account login password, user role (for example: ordinary user or advanced user) and platform name (for example: second platform) contained in the information to be authenticated At this time, the function in the target plug-in authenticates the above information in turn. When each information is authenticated, the target account is authenticated; when one of the information is not authenticated, the target account is not authenticated.

Solution 2: When the authentication logic contained in the target plug-in needs to confirm whether the target account is a registered account, at this time, the authentication steps are as follows: (As shown in Figure 4, the implementation process of Step 1-Step 3 in Figure 4)

Step 1. The first server sends a request message to the second server, and the request message is used to request whether the authentication target account is a registered account of the second platform; the second server is a server of the second platform.

After receiving the request message, the second server calls the database to check whether the target account is a registered account stored in the database, and after the check is completed, sends the authentication result to the first server.

Step 2. The first server receives the second response message; the second response message is used to indicate the authentication result.

The authentication result includes: the target account is a registered account or the target account is not a registered account.

Step 3. When the authentication result is used to indicate that the target account is a registered account of the second platform, the first server authenticates the authentication information based on the target plug-in in the first server; when the authentication result is used to indicate that the target account is not a registered account of the second platform When registering an account, the first server does not perform authentication on the information to be authenticated.

S106: The first server sends a first response message to the first terminal when the authentication information to be authenticated is passed; wherein, the first response message is used to indicate target content.

After the information to be authenticated of the target account passes the authentication of the target function, the first server sends the target content requested to be accessed in the first access request to the first terminal.

When the authentication of the information to be authenticated fails or the first server does not authenticate the information to be authenticated, the first server does not return the target content, and the first terminal displays a jump failure.

Optionally, after the first server sends the first response message to the first terminal, within a preset time, the first server receives the second access request sent by the first terminal; the second access request is used to request access to the first server the target content; the first server sends a third response message to the first terminal; the third response message is used to indicate the target content.

It can be understood that when the first server receives the second access request sent by the same account from the first terminal within a preset time after the first server sends the first response message to the first terminal, the first server may There is no need to authenticate the same account again. This setting can avoid resource waste caused by repeated authentication, save time and improve efficiency.

An access method provided in an embodiment of the present application, in which the server of the first platform invokes a plug-in to authenticate the authentication information of the user's account of the second platform. After the first server of the first platform receives the first access request sent by the user of the second platform through the first terminal in the second platform, it calls the plug-in to verify the account of the second platform user included in the access request. The information is authenticated, and when the authentication is passed, the first server of the first platform returns the content accessed by the first access request to the first terminal of the second platform. It can be understood that the authentication process is completed by the first server calling the plug-in, and the first server may not communicate with the second server of the second platform, so as to reduce the network transmission process, avoid slow authentication caused by network delay, and provide better user experience. At the same time, the authentication process and the second platform can achieve zero coupling, without interdependence and interference, and increase system stability.

The method provided by the embodiment of this application is described by taking the second platform to access the first platform as an example. When there are third platform, fourth platform and more platforms, and users among multiple platforms can share platform resources, you can define A shared plug-in file, the authentication plug-in developed by the authentication logic of each platform is saved in the shared plug-in file, and the shared plug-in file is installed in multiple platform servers to achieve the purpose of multi-platform resource sharing. Multi-platform resource sharing enables multi-platforms to achieve low-cost docking. When multiple platforms share the same plug-in file specifications, almost zero-cost docking can be achieved, and a large amount of labor costs will be saved.

The foregoing mainly introduces the solutions provided by the embodiments of the present application from the perspective of methods. In order to realize the above functions, it includes corresponding hardware structures and/or software modules for performing various functions. It should be easy for those skilled in the art to realize that the present application can be implemented in the form of hardware or a combination of hardware and computer software in combination with the units and algorithm steps of each example described in the embodiments disclosed herein. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Expert technical targets may use different methods to implement the described functions for each particular application, but such implementation should not be regarded as exceeding the scope of the present application.

The embodiment of the present application also provides an access device 200 . As shown in FIG. 5 , it is a schematic structural diagram of an access device 200 provided in the embodiment of the present application.

Wherein, the access device 200 includes: a receiving module 210, configured for the first server to receive the first access request sent by the first terminal; wherein, the first access request includes the information to be authenticated of the target account, and is used for requesting access to the first server. Target content; the target account is the account of the second platform user, and the first server is the server of the first platform; the first server contains the target plug-in; the target plug-in is used to authenticate the target account of the second platform; the authentication module 220 is used to When the authentication logic contained in the target plug-in does not need to confirm whether the target account is a registered account of the second platform, the first server authenticates the information to be authenticated based on the target plug-in; the sending module 230 is used for the first server to pass the authentication of the information to be authenticated In this case, a first response message is sent to the first terminal; wherein, the first response message is used to indicate the target content.

In a possible embodiment, the sending module 230 is also used to: when the authentication logic included in the target plug-in needs to confirm whether the target account is a registered account of the second platform, the first server sends a request message to the second server, and the request message Used to request whether the authentication target account is a registered account of the second platform; the second server is a server of the second platform; the receiving module 210 is also used for the first server to receive the second response message; the second response message is used to indicate the authentication result ; When the authentication result is used to indicate that the target account is a registered account of the second platform, the authentication module 220 is specifically configured to authenticate the information to be authenticated by the first server based on the target plug-in.

In a possible embodiment, the receiving module 230 is specifically configured to: the first server receives the first access request sent by the first terminal through a uniform resource location system URL.

In a possible embodiment, the access device 200 further includes: a selection module 240; before the first server authenticates the authentication information based on the target plugin, the selection module 240 is configured to select a target plugin from multiple plugins; the target plugin It is a plug-in that conforms to the authentication logic of the information to be authenticated.

In a possible embodiment, after sending the first response message to the first terminal, the receiving module 230 is further configured to, within a preset time, the first server receive the second access request sent by the first terminal; The access request is used to request access to the target content of the first server. The sending module 230 is further configured to: the first server sends a third response message to the first terminal; the third response message is used to indicate the target content.

Certainly, the access device 200 , the receiving module 210 , the authentication module 220 and the sending module 230 provided in this embodiment of the application include but are not limited to the above modules.

FIG. 6 is a schematic structural diagram of another access device 300 provided by an embodiment of the present application. As shown in FIG. 6 , the access device 300 includes a processor 301 , a memory 302 and a network interface 303 .

Wherein, the processor 301 includes one or more CPUs. The CPU may be a single-core CPU (single-CPU) or a multi-core CPU (multi-CPU).

The memory 302 includes, but is not limited to, RAM, ROM, EPROM, flash memory, or optical memory.

Optionally, the processor 301 implements the access method provided by the embodiment of the present application by reading the instruction stored in the memory 302, or, the processor 301 implements the access method provided by the embodiment of the present application by using the instruction stored internally. In the case that the processor 301 implements the method in the foregoing embodiment by reading the instruction stored in the memory 302, the memory 302 stores an instruction for implementing the access method provided in the embodiment of the present application.

The network interface 303 is a wired interface (port), such as FDDI, GE interface. Alternatively, network interface 303 is a wireless interface. It should be understood that the network interface 303 includes multiple physical ports, and the network interface 303 is used to access a network. Optionally, the access device further includes a bus 304, and the processor 301, the memory 302, and the network interface 303 are generally connected to each other through the bus 304, or are connected to each other in other ways.

In actual implementation, the receiving module 210 , the authentication module 220 , the sending module 230 and the selection module 240 of the access device 200 can be realized by calling the computer program code in the memory by the processor. For the specific execution process, reference may be made to the description of the above-mentioned method part, which will not be repeated here.

Another embodiment of the present application also provides an access device, including a memory and a processor. A memory is coupled to the processor; the memory is used to store computer program code, which includes computer instructions. Wherein, when the processor executes the computer instruction, the access device is made to execute each step of the method shown in the above method embodiment.

Another embodiment of the present application also provides a computer-readable storage medium, where computer instructions are stored in the computer-readable storage medium, and when the computer instructions are run on the access device, the access device executes the methods shown in the above method embodiments Access the individual steps performed by the device in the process.

Another embodiment of the present application further provides a chip system, which is applied to an access device. The chip system includes one or more interface circuits, and one or more processors. The interface circuit and the processor are interconnected by wires. The interface circuit is for receiving signals from the memory of the access device and sending signals to the processor, the signals comprising computer instructions stored in the memory. When the processor of the access device executes the computer instructions, the access device executes various steps performed by the access device in the method flow shown in the above method embodiments.

In another embodiment of the present application, a computer program product is also provided. The computer program product includes computer instructions. When the computer instructions are run on the access device, the access device executes the access device in the method flow shown in the above method embodiment. steps performed.

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using a software program, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When computer-executed instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. A computer can be a general purpose computer, special purpose computer, computer network, or other programmable device. Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g. Coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (such as infrared, wireless, microwave, etc.) transmission to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be accessed by a computer or may contain one or more data storage devices such as servers and data centers that can be integrated with the medium. The available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, solid state disk (solid state disk, SSD)) and the like.

The foregoing is only a specific implementation manner of the present application. Those skilled in the art may conceive of changes or substitutions based on the specific implementation methods provided in this application, and all of them shall fall within the protection scope of this application.

Claims (9)

1. An access method, characterized in that, comprising: The first server receives the first access request sent by the first terminal; wherein, the first access request includes the information to be authenticated of the target account, which is used to request access to the target content of the first server; the target account is the first The account of the second platform user, the first server is a server of the first platform; the first server includes a target plug-in; the target plug-in is used to authenticate the target account of the second platform; When the authentication logic contained in the target plug-in does not need to confirm whether the target account is a registered account of the second platform, the first server authenticates the information to be authenticated based on the target plug-in; The first server sends a first response message to the first terminal when the authentication of the information to be authenticated is passed; where the first response message is used to indicate the target content. 2. The method according to claim 1, wherein when the authentication logic contained in the target plug-in needs to confirm whether the target account is a registered account of the second platform, the first server based on the target plug-in Authenticate the information to be authenticated, including: The first server sends a request message to the second server, and the request message is used to request authentication of whether the target account is a registered account of the second platform; the second server is a server of the second platform; The first server receives a second response message; the second response message is used to indicate an authentication result; When the authentication result indicates that the target account is a registered account of the second platform, the first server authenticates the information to be authenticated based on the target plug-in in the first server. 3. The method according to claim 1, wherein the first server receives the first access request sent by the first terminal, comprising: The first server receives the first access request sent by the first terminal through a Uniform Resource Locator URL. 4. The method according to claim 1, wherein before the first server authenticates the information to be authenticated based on the target plug-in, the method further comprises: Selecting a target plug-in from multiple plug-ins; the target plug-in is a plug-in that conforms to the authentication logic of the information to be authenticated. 5. The method according to claim 1, characterized in that, after sending the first response message to the first terminal, the method further comprises: Within a preset time, the first server receives a second access request sent by the first terminal; the second access request is used to request access to the target content of the first server; The first server sends a third response message to the first terminal; the third response message is used to indicate the target content. 6. An access device, characterized in that it comprises: The receiving module is used for the first server to receive the first access request sent by the first terminal; wherein, the first access request includes the information to be authenticated of the target account, and is used to request access to the target content of the first server; The target account is an account of a second platform user, and the first server is a server of the first platform; the first server includes a target plug-in; the target plug-in is used to authenticate the target account of the second platform; An authentication module, configured to, when the authentication logic contained in the target plug-in does not need to confirm whether the target account is a registered account of the second platform, the first server performs authentication on the information to be authenticated based on the target plug-in certification; A sending module, configured for the first server to send a first response message to the first terminal when the authentication of the information to be authenticated is passed; wherein the first response message is used to indicate the target content. 7. The access device of claim 6, wherein: When the authentication logic included in the target plug-in needs to confirm whether the target account is a registered account of the second platform, the sending module is further configured to send a request message from the first server to the second server, the The request message is used to request to verify whether the target account is a registered account of the second platform; the second server is a server of the second platform; The receiving module is further configured to receive, by the first server, a second response message; the second response message is used to indicate an authentication result; When the authentication result is used to indicate that the target account is a registered account of the second platform, the authentication module is specifically configured to authenticate the information to be authenticated by the first server based on the target plug-in; The receiving module is specifically configured to receive, by the first server, the first access request sent by the first terminal through a Uniform Resource Locator URL; The access device also includes: a selection module; Before the first server authenticates the information to be authenticated based on the target plugin, the selection module is configured to select a target plugin from a plurality of plugins; the target plugin is a plugin that conforms to the authentication logic of the information to be authenticated ; After the first response message is sent to the first terminal, the receiving module is further configured to, within a preset time, the first server receive a second access request sent by the first terminal; the The second access request is used to request access to the target content of the first server; The sending module is further configured to: the first server sends a third response message to the first terminal; the third response message is used to indicate the target content. 8. An access device, characterized in that it includes a memory and a processor; the memory is coupled to the processor; the memory is used to store computer program codes, and the computer program codes include computer instructions; wherein, when the When the processor executes the computer instructions, the access device is caused to perform the method described in claims 1-5. 9. A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer instructions; wherein, when the computer instructions are run on the access device, the access device is made to execute the method according to claim 1. - The method described in any one of 5.

Images