Page access method, system, device, program product and storage medium

Abstract

The embodiment of the present specification relates to the technical field of Internet, and provides a page access method, system, device, program product and storage medium, the method comprises: if it is determined that the current user who accesses the target page needs to carry out self-defined login, loading the login processing plug-in corresponding to the target page;Call the login processing plug-in, so that the login authentication system corresponding to the target page carries out identity authentication on the current user after being redirected;The login authentication result generated by the login authentication system is parsed through the login processing plug-in, and the analysis information of the login authentication result of the login processing plug-in is obtained;According to the analysis information, it is determined whether the current user can access the target page.

Description

Technical Field

[0001] This manual relates to the field of Internet technology, and in particular to methods, systems, devices, program products and storage media for accessing web pages. Background Technology

[0002] In complex B2B (Business-to-Business) environments, software integrators need to provide services to numerous enterprise clients simultaneously. For example, they might develop software for businesses, allowing users to log in and access the software's pages. Medium to large-sized enterprises often have their own in-house login and authentication systems and do not wish to adopt common industry-standard protocols such as single sign-on. Therefore, meeting users' customized login and authentication needs becomes a pressing technical challenge. Summary of the Invention

[0003] To overcome the problems existing in related technologies, this specification provides page access methods, systems, devices, program products, and storage media.

[0004] According to a first aspect of the embodiments of this specification, a page access method is provided, the method comprising:

[0005] If it is determined that the current user accessing the target page needs to perform a custom login, load the login processing plugin corresponding to the target page;

[0006] The login processing plugin is invoked so that the login authentication system corresponding to the target page can authenticate the current user after being redirected;

[0007] The login processing plugin parses the login authentication result generated by the login authentication system to obtain the parsing information of the login authentication result.

[0008] Based on the parsed information, it is determined whether the current user can access the target page.

[0009] According to a second aspect of the embodiments of this specification, a page access method is provided, the method being applied to a login processing plugin, the login processing plugin being loaded by a main login module after determining that the current user accessing the target page needs to perform a custom login; the method includes:

[0010] The system receives a call request from the main login module so that the login authentication system corresponding to the target page can authenticate the current user after being redirected, and parses the login authentication result generated by the login authentication system.

[0011] The parsed information is provided to the main login module so that the main login module can determine whether the current user can access the target page based on the parsed information.

[0012] According to a third aspect of the embodiments of this specification, a page access method is provided, the method comprising:

[0013] Provide users with an upload interface for login processing plugins;

[0014] The login processing plugin provided by the user is obtained through the upload interface and stored; wherein, the login processing plugin is loaded during the execution of the method described in the first aspect of the main login process and is used to execute the steps of the method described in the second aspect.

[0015] According to a fourth aspect of the embodiments of this specification, a page access system is provided, the system including a page access device and a login authentication system, the page access device being used to perform the steps of the methods described in the first, second, or third aspects.

[0016] According to a fifth aspect of the embodiments of this specification, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method embodiments described in the first, second, or third aspects above.

[0017] According to a sixth aspect of the embodiments of this specification, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the method embodiments described in the first, second, or third aspects above.

[0018] According to a seventh aspect of the embodiments of this specification, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of the method embodiments described in the first, second, or third aspects above.

[0019] The technical solutions provided in the embodiments of this specification may include the following beneficial effects:

[0020] In this embodiment, the user's login processing plugin is loaded into the target page access flow to enable users to insert custom login authentication processes. By calling the login processing plugin, the user can be redirected to the user's login authentication system, which then authenticates the current user. The login authentication result is parsed by the login processing plugin, and the parsed information determines whether the current user can access the target page. It can be seen that in this embodiment, the user's login processing plugin can be used to redirect to the user's login authentication system, allowing users to customize their authentication logic. The login processing plugin is directly triggered within the page access flow of this embodiment, and can be integrated with the user's login authentication system without incurring additional protocol adaptation resources or costs. The user side does not need to transmit the specific parsing method of the login authentication result to the service provider, ensuring user information security, and the service provider does not need to perform an additional parsing process. Therefore, this embodiment can support diverse login authentication mechanisms without defining a login authentication service for each user in the software.

[0021] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this specification. Attached Figure Description

[0022] Figure 1 This is a flowchart illustrating a page access method according to an exemplary embodiment of this specification.

[0023] Figure 2A This is a schematic diagram illustrating a custom plugin login framework according to an exemplary embodiment of this specification.

[0024] Figure 2B This is a schematic diagram illustrating another custom plugin login framework according to an exemplary embodiment of this specification.

[0025] Figure 2C This is a schematic diagram illustrating a login process according to an exemplary embodiment of this specification.

[0026] Figure 3 This is a flowchart illustrating a page access method according to an exemplary embodiment of this specification.

[0027] Figure 4A This is a flowchart illustrating a page access method according to an exemplary embodiment of this specification.

[0028] Figure 4B This is a schematic diagram of a plugin upload page illustrated in this specification according to an exemplary embodiment.

[0029] Figure 4CThis is a schematic diagram illustrating a login method settings page according to an exemplary embodiment of this specification.

[0030] Figure 5 This is a hardware structure diagram of a computer device containing a page access device, as illustrated in this specification according to an exemplary embodiment.

[0031] Figure 6 This is a block diagram illustrating a page access device according to an exemplary embodiment of this specification.

[0032] Figure 7 This is a block diagram illustrating another page access device according to an exemplary embodiment of this specification.

[0033] Figure 8 This is a block diagram illustrating another page access device according to an exemplary embodiment of this specification. Detailed Implementation

[0034] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this specification as detailed in the appended claims.

[0035] The terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of this specification. The singular forms “a,” “the,” and “the” as used in this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0036] It should be understood that although the terms first, second, third, etc., may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this specification, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0037] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this manual are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0038] First, let's explain some of the terms used in the embodiments of this specification:

[0039] Single Sign-On (SSO) is an authentication mechanism that allows users to access multiple mutually trusted application systems using a single set of login credentials without having to log in to each system repeatedly.

[0040] Identity Providers (IDPs) are systems or services responsible for digital authentication and authorization. They are responsible for creating, maintaining, and managing user identity information, verifying user identity credentials, and issuing identity certificates to Service Providers (SPs).

[0041] Service Providers (SPs): Applications or websites that provide services to users. When a user attempts to access resources provided by an SP, a corresponding request is sent to the IDP to verify and obtain the user's identity.

[0042] Custom plugins define key actions for resources in a standardized way, and expose the business logic of pre-processing and post-processing of resources and actions through open standards, allowing users to customize business logic as needed to complete certain functional scenarios.

[0043] Industry standard agreements refer to formal standards or specifications that are widely recognized and adopted in a specific industry or multiple industries. They are usually developed by standardization organizations, industry associations, technology alliances or institutions.

[0044] In complex B2B (Business-to-Business) environments, software integrators, as service providers, need to offer services to numerous enterprise clients simultaneously. Medium to large-sized enterprises often have their own in-house developed authentication systems, rather than adopting common single sign-on (SSO) protocols such as OAuth (Open Authorization), CAS (Central Authentication Service), or SAML (Security Assertion Markup Language).

[0045] Research has revealed that current software integrators do not support login integration with enterprises' self-developed identity authentication systems. On one hand, if software integrators want to support the personalized identity authentication services of various enterprises simultaneously, they often need to customize a separate software for each enterprise to meet its self-developed identity authentication system. This results in multiple software versions, which is detrimental to maintenance and iteration, and in software engineering, avoids bloated projects and external code intrusion. On the other hand, the complexity and security standards of enterprise-developed identity authentication systems vary, requiring software integrators to invest significant learning and development costs when integrating with enterprise identity authentication systems. Furthermore, enterprises typically do not want their self-developed identity authentication systems to be transparently transmitted to software integrators.

[0046] Based on this, the embodiments of this specification provide a page access method that enables user authentication using a user login authentication system during the process of providing services to users. The embodiments of this specification will now be described in detail.

[0047] like Figure 1 As shown, Figure 1 This is a flowchart illustrating a page access method according to an exemplary embodiment, comprising the following steps:

[0048] In step 102, if it is determined that the current user accessing the target page needs to perform a custom login, load the login processing plugin corresponding to the target page;

[0049] In step 104, the login processing plugin is invoked so that the login authentication system corresponding to the target page can authenticate the current user after being redirected;

[0050] In step 106, the login authentication result generated by the login authentication system is parsed by the login processing plugin to obtain the parsing information of the login authentication result by the login processing plugin;

[0051] In step 108, it is determined whether the current user can access the target page based on the parsed information.

[0052] As an example, the method of this embodiment can be applied to the server and / or client; wherein, the server can be a program installed on a backend device to provide services to the user. Exemplarily, the backend device can be a server, which can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud modules, cloud storage, network services, cloud communication, middleware services, domain name services, security services, and big data and artificial intelligence platforms. The client can be a program installed on a computer device to provide services to the user, including but not limited to applications, web pages, mini-programs, plugins, or components. The computer device includes but is not limited to hardware devices such as smartphones, personal digital assistants, tablets, personal computers, laptops, virtual reality terminal devices, and augmented reality terminal devices, and may also include cloud devices such as virtual machines or cloud desktops.

[0053] As an example, the page access in this embodiment can be performed by either the server or the client, or by both working together (each performing a part of the steps). This embodiment does not impose any restrictions on this. For example, when a user accesses a page on the client side, the client requests the server, and the server completes the page access process in this embodiment; or, the client completes the page access process on its own, or both work together to complete the page access process in this embodiment.

[0054] As an example, considering that a user login processing plugin is introduced in this embodiment to help complete page access, the process of the method in this embodiment can be called the main login process, and the execution entity that executes the main login process is called the main login module.

[0055] As an example, the target page in step 102 can be a page on a client, which can be provided to the user by the aforementioned service provider. For instance, taking a cloud computing service provider as an example, this cloud computing service provider can provide various types of services, such as data analysis services or business intelligence (BI) services, etc. The service provider can provide a service system to the user, and the service system can be presented through applications or web pages, etc.

[0056] Taking data analytics services as an example, cloud computing service providers can help enterprises build data analytics systems through intelligent data analysis and visualization capabilities. These systems can be configured on cloud devices provided by the service provider, and users within the enterprise can access one or more pages of the system. When a user accesses a page, authentication is required. For some enterprises, there is a need for customized authentication, and since the data analytics system is built by the cloud computing service provider, this embodiment provides a plug-in login solution.

[0057] In step 102, the login processing plugin can be pre-defined by the user. The user here can be a developer of the organization to which the target page belongs, meaning it can be different from the current user in step 102. Using a plugin login method allows users to perform custom authentication using a custom login authentication system when using the client provided by the service provider, without requiring intervention from the client provider.

[0058] Optionally, in practical applications, a client can contain multiple different pages, and different pages can correspond to the same login processing plugin. Alternatively, the organization owning the client can also set different custom login methods for different pages; therefore, different pages of a client can correspond to different login processing plugins.

[0059] In practical applications, the login processing plugin can be uploaded to the developers of the target page through various implementation methods to obtain the login processing plugin in advance. The specific implementation methods of the login processing plugin can be found in the following embodiments.

[0060] In some cases, service providers can obtain login processing plugins provided by different users and store or manage these different login processing plugins in a unified manner.

[0061] In step 102, when the current user needs to access the target page, it can be determined whether a custom login is required. For example, if the target page only has one custom login method as described in this embodiment, then upon receiving the access request, it can be directly determined that a custom login is required.

[0062] Optionally, the target page can also have multiple different login methods, such as the login methods of different login protocols mentioned in the previous embodiments and the custom login method of this embodiment. Therefore, the determination method for whether a custom login is required can be preset as needed. The specific determination method can be configured according to actual needs, and this embodiment does not limit it. As an example, the service provider provides services to different enterprise users. Some enterprise users need custom login, and others need to perform custom login. An identifier representing whether the client page of different enterprises needs custom login can be set, so that after obtaining the access request of the target page, it is determined whether a custom login is required according to the identifier corresponding to the target page. Optionally, it can also be determined based on other information. For example, if the client where the target page is located is deployed on the cloud device provided by the service provider, it can query whether a custom login is required based on the relevant information of the client where the target page is located (such as client information and cloud device information).

[0063] If it is determined that a custom login is required, a login processing plugin corresponding to the target page can be loaded. For example, the login processing plugin can be a program package, which can be obtained and decompressed to run the login processing plugin.

[0064] The login processing plugin can include user-preset custom login logic. This embodiment designs a user-defined login authentication system to authenticate the user's identity in a custom login scenario, thus meeting the user's custom login needs. In step 104, since the login processing plugin is loaded, this embodiment can call the plugin and redirect to the login authentication system corresponding to the target page, allowing the login processing plugin to parse the login authentication result generated by the login authentication system. In practical applications, the login processing plugin is provided by the user, and its calling and returning parameters can be set based on the service provider's requirements. Its internal processing logic can be customized by the user; this embodiment does not impose any limitations on this.

[0065] As an example, this embodiment is used to authenticate the current user's login. It can be understood that the current user is in a state of not using the login authentication system when accessing the target page.

[0066] As an example, the step of redirecting to the authentication page can be implemented in several ways. One approach is for the login processing plugin to include the access address of the authentication page, and then provide this access address to the execution entity of the method in this embodiment, which then redirects to the authentication page based on this access address. Alternatively, it is also optional for the login processing plugin to execute the redirection to the authentication page process itself.

[0067] Redirection, or redirection to the authentication page, allows users to view the authentication page of the login authentication system and perform identity authentication operations on that page. For example, users can enter their account and password information on the authentication page so that the authentication page can authenticate the user's identity. The specific identity authentication method can be implemented by the user's login authentication system.

[0068] The login authentication system is a user-defined system. Users can customize their login authentication logic to meet their specific identity authentication needs. After authenticating the current user, the login authentication system generates a login authentication result. Since the login authentication system belongs to the user, the parsing and processing of the login authentication result is handled by a login processing plugin in step 106 of this embodiment. This eliminates the need for the user to transmit the specific parsing method of the identity authentication message to the service provider, and also eliminates the need for the service provider to perform additional parsing procedures. Thus, the loading login processing plugin can parse the login authentication result obtained from the user's login authentication system and obtain parsed information. The execution entity in this embodiment can then determine whether the current user can access the target page based on the parsed information.

[0069] As an example, the parsed information may include information indicating whether the current user has passed login authentication, thereby determining whether the current user can access the target page; optionally, the parsed information may include other information so that the execution entity of this embodiment can perform other processing based on the included information, which is also optional and not limited in this embodiment.

[0070] As can be seen from the above embodiments, this embodiment, in the access process of the target page, implements a user-customized login authentication process by loading a user login processing plugin. By calling the login processing plugin, the user can be redirected to the user's login authentication system, which then authenticates the current user. The parsing of the resulting login authentication result can be completed by the login processing plugin, and the parsing information can determine whether the current user can access the target page. It can be seen that in this embodiment, the user's login processing plugin can be used to redirect to the user's login authentication system, allowing the user to customize their own authentication logic. The login processing plugin is directly triggered within the page access process of this embodiment, and can be integrated with the user's login authentication system without incurring additional protocol adaptation resources or cost burdens. The user side does not need to transmit the specific parsing method of the login authentication result to the service provider side, ensuring user information security, and the service provider does not need to execute an additional parsing process. Therefore, this embodiment can support diverse login authentication mechanisms without defining a login authentication service for each user in the software.

[0071] In some examples, if it is determined that the current user accessing the target page needs to perform a custom login, loading the login processing plugin corresponding to the target page includes:

[0072] In response to receiving the current access request to the target page, it is determined that the current user needs to perform a custom login, and the login processing plugin corresponding to the target page is loaded;

[0073] The step of invoking the login processing plugin to enable the login authentication system corresponding to the target page to authenticate the current user after redirection may include:

[0074] The login processing plugin is invoked based on the access request, so that the access address of the login authentication system determined by the login processing plugin based on the access request is redirected, and the login authentication system performs identity authentication on the current user.

[0075] In step 104, since the login processing plugin is loaded, this embodiment can call the plugin based on the request information carried in the access request. The login processing plugin can determine the access address of the login authentication system based on the request information.

[0076] As an example, the access request to the target page may contain one or more types of request information, such as, but not limited to: request parameters, request headers, session information (such as tokens and / or session identifiers). The login processing plugin can be invoked based on one or more (partial or all) types of request information carried in the access request; the specific settings can be configured according to actual needs.

[0077] In this way, the login processing plugin can determine different authentication page addresses based on the different request information carried in the access request. This allows users to enable different authentication pages of the login authentication system according to their needs, based on different types of current users, in order to support users' differentiated identity authentication requirements.

[0078] In some examples, the login processing plugin includes an authentication redirection module;

[0079] The invocation of the login processing plugin includes:

[0080] The authentication redirection module is invoked to return the access address of the login authentication system;

[0081] Based on the access address, the user is redirected to the login authentication system.

[0082] In this embodiment, the login processing plugin includes an authentication redirection module, which can be called by the execution entity of this embodiment, such as the main login process calling the authentication redirection module. Optionally, the login processing plugin may include one or more modules for executing different processes within the login processing plugin. The modules included in the login processing plugin can be methods in the Java language or functions in the C language.

[0083] Optionally, the main login process can obtain request information from the access request and call the authentication redirection module based on some or all of the request information carried in the access request. In this embodiment, the executing entity can perform a redirection based on the address returned by the authentication redirection module, i.e., redirect to the authentication page address, allowing the user to view the authentication page of the login authentication system and enter their account and password information on that page, so that the authentication page can authenticate the user's identity.

[0084] This embodiment designs a system where the authentication redirection module returns the address of the login authentication system, allowing users to configure the authentication page address of the login authentication system themselves within the login processing plugin. This eliminates the need for hardcoding the login authentication system address in the main login process, as it is dynamically provided by the login processing plugin. Furthermore, it allows for low-cost updates by modifying the login processing plugin when the user's login authentication system page changes. Optionally, different authentication page addresses can also be configured in the authentication redirection module. For example, different authentication page addresses can be set in the login processing module based on different request information. This allows users to enable different authentication pages for different types of current users, supporting differentiated authentication needs.

[0085] In some examples, the method is applied in the main login module, which includes a callback interface;

[0086] The login authentication system is used to: after obtaining the login authentication result, call the callback interface based on the login authentication result;

[0087] The login processing plugin includes a login processing module;

[0088] The step of obtaining the parsing information of the login authentication result by the login processing plugin includes:

[0089] If a request to call the callback interface is received from the login authentication system, the login authentication result is obtained from the request.

[0090] After invoking the login processing module based on the login authentication result, the parsing information of the login processing module on the login authentication result is obtained.

[0091] In this embodiment, considering that different login authentication systems may have different return formats, a callback interface is designed in the main login module to receive the login authentication results returned by the login authentication system in order to support different protocols and thus adapt to the return formats of different login authentication systems.

[0092] Furthermore, to parse and process the login authentication results, this embodiment includes a login processing module within the login processing plugin for parsing and processing the login authentication results. This login processing module is developed and designed by the user when developing the login processing plugin. Therefore, after the login authentication system obtains the login authentication result, it can call a callback interface based on the login authentication result. Thus, the main login module in this embodiment can obtain the login authentication result from the call request through the callback interface. Then, the main login module can call the login processing module based on the login authentication result, allowing the login processing module to perform the parsing of the login authentication result. Consequently, the main login module can obtain the parsing information of the login authentication result from the login processing module. Therefore, since the parsing of the login authentication result is performed by the login processing plugin, the user side does not need to transmit the specific parsing method to the service provider side, nor does the service provider need to perform any additional parsing processes.

[0093] As an example, when enterprise users use the login processing plugin, they need to be redirected to the address of the user's login authentication system first. Subsequently, the login authentication system will call back the plugin login callback interface on the client side to pass the user's identity information that has been successfully authenticated. Finally, the user can be redirected to the specified address when logging out.

[0094] For example, in a login processing plugin developed by enterprise developers, the access address of the login authentication system can be set. Furthermore, the authentication redirection module within the plugin can be used to return the access address of the login authentication system. The main login module can call this authentication redirection module based on the request information from the access request. This module can implement the following processing logic: if it is determined from the request information that the current user is not logged in, it returns the access address; if it is determined from the request information that the current user has already performed single sign-on, the request information contains relevant information indicating successful authentication, i.e., the login authentication result. Therefore, the authentication redirection module can determine that it does not need to redirect to the login authentication system, but can return the plugin's login callback interface. Thus, the main login process can call the login processing module in the login processing plugin after obtaining the returned callback interface.

[0095] The main login module can invoke the login processing module based on the login authentication result contained in the callback interface's call request. In this way, the login processing module can obtain the login authentication result transmitted by the main login module, parse it, and convert it into the parsing information required by the main login module. Therefore, this embodiment designs a callback interface in the main login module to receive the login authentication result returned by the login authentication system, supporting different protocols and thus adapting to the return formats of different login authentication systems.

[0096] In some examples, determining whether the current user can access the target page based on the parsed information may include:

[0097] If the parsed information indicates that login authentication failed, it is determined that the current user cannot access the target page;

[0098] If the parsed information contains the current user identity information obtained by converting the login authentication result by the login processing plugin according to a preset format, it is determined that the current user can access the target page.

[0099] This embodiment implements the processing of two different parsing results. For example, the login authentication result generated by the login authentication system may be that the current user's identity authentication is incorrect or that the current user is not allowed to access for other reasons. Therefore, the login processing plugin can return parsing information indicating that the login authentication has failed, so that the main login module can determine that the current user has failed to access the target page, and then perform corresponding follow-up processing, such as outputting information such as access not allowed.

[0100] In other examples, the login authentication system may result in successful login authentication. In such cases, the login authentication result may contain user identity information. This embodiment designs a login processing plugin to convert the login authentication result into the current user identity information according to a preset format. This eliminates the need for the user to transparently transmit the encapsulated form of the information in the login authentication result; the user only needs to transmit the user identity information required by the service provider according to the preset format. Thus, based on the current user identity information, it can be determined whether the current user is allowed to access the target page, and subsequently, the target page can be displayed on the client.

[0101] Optionally, the preset format can be set according to actual needs and can include one or more format information, such as encoding language information, encapsulation format information of user identity information, etc. As an example, taking Java language as an example, the format information of the preset format can include: Java class, class name, each attribute contained in the class, attribute name and data type of each attribute. Thus, the login processing plugin can return the current user identity information based on the preset format to the main login module.

[0102] Specific user identity information can be set according to actual needs, such as based on the information required to display the target page, including but not limited to user identifier, user name, user nickname, or other extended information (such as user avatar). This embodiment does not limit this. As an example, when displaying the target page, the user's login status can be displayed, and when displaying the user's login status, extended information such as user nickname or user avatar can be displayed. As an example, user identifier and other information can be used to determine the restrictions of certain specific functions when displaying the target page. For example, it can be used to determine whether the user has permission to access specific functions, thereby determining whether certain functional modules in the target page can be displayed.

[0103] Therefore, this embodiment can distinguish between successful and failed authentication scenarios and execute differentiated logic based on different results. Furthermore, a preset format is used to agree on the transmission format of user identity information with the user side, achieving decoupling between service provision and the user side.

[0104] Optionally, the login processing plugin may also include a logout module, so that when the main login module detects that a user has logged out, it can call the logout module in the login processing plugin. The logout module can return a specified logout address, which can then redirect the user to the page corresponding to that specified address, so that the user can see the logout page.

[0105] In some examples, considering the diversity of login methods, determining that the current user needs to perform a custom login includes:

[0106] Obtain the request information carried in the access request, and determine whether the request information conforms to the preset custom login strategy;

[0107] If the conditions are met, it is determined that the current user accessing the target page needs to perform a custom login.

[0108] In this embodiment, a custom login policy can be pre-set. This custom login policy can determine whether the access request requires custom login, thus providing users with diverse and differentiated login methods. For example, if different users within an organization can use different login methods, the custom login policy can be used to filter out users who need custom login and perform custom authentication on these users. Alternatively, if it is determined that the preset custom login policy is not met, other login methods can be used, such as the aforementioned OAuth, CAS, SAML, and other login methods. This embodiment does not limit this to any particular method.

[0109] In this embodiment, the custom login strategy can be set in conjunction with the request information of the access request, so that after the user initiates an access request, the request information of the access request can be obtained to determine whether a custom login is required.

[0110] The request information in the access request can be any one or more types of information, and this embodiment does not limit this. As an example, the request information may include one or more of the following: information carried in the access request, host information of the host where the target page is located (host IP address or host identifier, etc.) or page information of the target page (such as page domain name, identifier information of the client where the page is located), etc.

[0111] Based on this, the embodiments described herein design a custom login strategy based on access request information, which can automatically decide whether a custom login is required for an access request, thereby meeting the diverse and differentiated login methods of users, and also enabling automatic triggering of custom login methods.

[0112] In some examples, considering that a service provider may provide services to many users, and that there may be different login processing plugins within the same organization, in order to accurately determine the user's login processing plugin, loading the login processing plugin corresponding to the target page includes:

[0113] If an access request for the target page from the current user is received, the request information of the access request is obtained, and the login processing plugin corresponding to the request information is queried and loaded.

[0114] Considering that the service provider may store many different login processing plugins, this embodiment can query the corresponding login processing plugin based on the request information of the access request. The request information can be any one or more types of information, and this embodiment does not limit this. As an example, the request information may include one or more of the following: information carried in the access request, host information of the host where the target page is located (host network address or host identifier, etc.), or page information of the target page (such as page domain name, identifier information of the client where the page is located).

[0115] In this embodiment, when storing user login processing plugins, information matching the login processing plugins can be set. Therefore, after obtaining request information, the corresponding login processing plugin can be retrieved and loaded. Thus, this embodiment allows the service provider to store different login processing plugins and accurately retrieve the login processing plugin corresponding to the target page during the access processing flow of the target page.

[0116] The embodiments described in this specification will be described next. Figure 2AThe diagram shown is a schematic representation of a custom plugin login framework according to an exemplary embodiment of this specification.

[0117] In this embodiment, the service provider provides a certain software service;

[0118] For developers within organizations using this software service: they can develop custom login plugins based on the development toolkit provided by the service provider and their organization's internal self-developed identity authentication protocol specifications. The developed custom login plugins (e.g., development kits) can be provided to the service provider. For example, the service provider may provide a plugin controller that allows developers to register their login plugins, enabling hot-swapping of login plugins.

[0119] For other personnel in the organization who need to use the software service: When accessing the software service page, a login process will be triggered. This login process can load the login processing plugin based on the login processing plugin activated in the plugin controller. That is, the code of the custom plugin is hot-deployed through the program development kit, and then the code logic inside the plugin is executed.

[0120] The enterprise's login authentication system verifies the login identity, and the plugin code logic parses the login authentication result. After confirming that the login authentication system has returned a successful login authentication result, the user can successfully log in and access the software page.

[0121] like Figure 2B The diagram shown is another schematic representation of a custom plugin login framework according to an exemplary embodiment of this specification. The login processing plugin in the embodiments of this specification can be understood to have two forms:

[0122] Development mode: This refers to the process by which developers develop and define personalized login processing logic based on the development toolkit according to their internal business scenarios. As an example, the service provider provides a custom plugin management page, on which developers can create, upload, and publish plugins after development is completed.

[0123] Runtime state: This refers to the process where the service provider's plugin controller retrieves plugins uploaded by business developers, registers them, and distributes plugin resources to the machine for storage. This allows the program implementing the main login process to hot-load the plugins during execution. As an example, the service provider can set up two modules: a plugin controller and a plugin engine, to manage plugins provided by multiple users. For instance, the plugin controller can retrieve plugins uploaded by developers, register them (such as recording information about each user and uploaded plugins, as well as information about custom logins required by the user), and store the plugins. It can also distribute the stored plugins to the plugin engine when needed. In the plugin engine, during page access, when it's determined that a custom login is required, it routes the plugin corresponding to the current target page from multiple plugins, loads the plugin, and ultimately enables the plugin to execute.

[0124] like Figure 2C The diagram shown is a schematic representation of a login process according to an exemplary embodiment of this specification. The process can be as follows:

[0125] A user initiates an access request to a specific software page.

[0126] Optionally, as needed, certain pre-processing can be performed after receiving an access request, such as parsing and storing information in the access request; then, login processing can be performed, i.e., entering the main login process of this embodiment; in the main login process, login policy routing and loading of custom login plugins can be performed. During this process, it can be determined whether the access request conforms to the custom login policy. As an example, the custom login policy can be matched based on host information, page access address, information carried in the access request, etc.; if it does not conform, other login methods can be executed, which is not limited in this embodiment.

[0127] If the policy is matched, a custom login process can be triggered. If the conditions are met, it is determined that a custom login is required; the corresponding login processing plugin is then retrieved. In the main login process of the software, after the login plugin is loaded, the main login process will execute the plugin's code logic because it expands the location where the login processing plugin can be executed.

[0128] Optionally, the request information of the access request can be passed through to the plugin code first; then, in the plugin code process, the login user can be authenticated based on the request information and the enterprise's internal login authentication system.

[0129] Finally, the plugin process in the login processing plugin can also parse the login authentication result (login successful or login failed) of the login authentication system, so that the main login process of the software can obtain and save the parsed information of the login authentication result.

[0130] Based on the parsing information of the login authentication results provided by the plugin, the main login process of the software determines whether to display the software page.

[0131] like Figure 3 The diagram shown is a flowchart illustrating another page access method according to an exemplary embodiment of this specification. The method is applied to a login processing plugin, which is loaded by the main login module after determining that the current user accessing the target page needs to perform a custom login. The method may include the following steps:

[0132] In step 302, a call request from the main login module is received so that the login authentication system corresponding to the target page can authenticate the current user after being redirected, and the login authentication result generated by the login authentication system is parsed.

[0133] In step 304, the parsed information is provided to the main login module so that the main login module can determine whether the current user can access the target page based on the parsed information.

[0134] In some examples, receiving the call request from the main login module includes:

[0135] The system receives a call request initiated by the main login module based on the current user's access request to the target page, determines the access address of the login authentication system based on the access request, redirects the access address of the login authentication system, and then the login authentication system authenticates the current user.

[0136] In some examples, the login processing plugin includes an authentication redirection module;

[0137] The step of receiving the call request initiated by the main login module based on the current user's access request to the target page, and determining the access address of the login authentication system based on the access request, includes:

[0138] In response to the main login module's call request to the authentication redirection module based on the access request, the access address of the login authentication system is determined based on the request information in the access request and returned, so that the main login module redirects to the login authentication system based on the access address;

[0139] And / or,

[0140] The main login module includes a callback interface; the login authentication system is used to: after obtaining the login authentication result, call the callback interface based on the login authentication result; the login processing plugin also includes a login processing module;

[0141] Providing the parsed information to the main login module includes:

[0142] In response to the main login module's call request to the login processing module, the login authentication result is obtained from the call request to the login processing module, parsed, and then provided to the main login module; wherein, the call request to the login processing module is initiated by the main login module after obtaining the login authentication result from the call request from the login authentication system to the callback interface.

[0143] like Figure 4A The diagram shown is a flowchart illustrating another page access method according to an exemplary embodiment of this specification. The method may include the following steps:

[0144] In step 402, an upload interface for the login processing plugin is provided to the user;

[0145] In step 404, the login processing plugin provided by the user is obtained through the upload interface and stored; wherein, the login processing plugin is loaded during the execution of the aforementioned method embodiment by the main login module and is used for execution. Figure 3 The steps of the illustrated embodiment.

[0146] As an example, the method of this embodiment can be applied to a client provided by a service provider to a developer. The client can be a program installed on a computer device to provide services to the user. The client includes, but is not limited to, applications, web pages, applets, plugins, or components. Computer devices include, but are not limited to, hardware devices such as smartphones, personal digital assistants, tablets, personal computers, laptops, virtual reality terminal devices, and augmented reality terminal devices, and may also include cloud devices such as virtual machines or cloud desktops.

[0147] The client can provide an upload interface for login processing plugins. For example, it can provide a plugin upload page for developers to upload their developed login processing plugins. Figure 4BThe diagram shown is a schematic of a plugin upload page according to an exemplary embodiment of this specification. The "Plugin Upload" control on this page is the upload interface. Optionally, the page may also include other controls, such as a plugin name editing control, which can be configured as needed in practical applications. Developers can upload their developed login processing plugin packages by clicking the "Plugin Upload" control on this page. After the client obtains the login processing plugin package, it can send it to the server for storage, thereby realizing the developer's processing flow for the login processing plugin.

[0148] Optionally, the server can also provide plugin binding functionality. For example, users can bind their registered login processing plugins to their target page (or the client containing the target page); such as... Figure 4C The image shown is a schematic diagram of a login method settings page according to an exemplary embodiment of this specification. Figure 4C Developers can choose the login method for the target page, which includes a startup control for the plugin login method. Users can start plugin login and select the login plugin corresponding to the target page, thereby enabling the plugin login method for the target page and binding the login processing plugin.

[0149] As can be seen from the above embodiments, this embodiment introduces a login processing plugin, which exposes the login authentication, logout and other processes to the outside world. The newly added login management custom plugin extension point can be customized and extended by the external system as needed, which solves the problem of integrating and connecting the diverse and personalized self-developed identity authentication system of enterprises.

[0150] This embodiment is characterized by high flexibility: each enterprise can customize the login process in the custom plugin according to the enterprise's identity authentication and security specifications;

[0151] This embodiment features low cost: the custom login plugin is directly triggered by the integrator's internal software mechanism, which can be perfectly integrated with the enterprise's business system without generating additional protocol adaptation resources or cost burdens.

[0152] This embodiment features zero coupling: software integrators provide a unified custom plugin to support diverse authentication mechanisms without having to define an authentication service for each enterprise in the software.

[0153] This embodiment utilizes hot-swappable technology, enabling enterprises to dynamically load and launch login plugin code without restarting the project. This plug-and-play solution not only eliminates the need to customize independent software code for each enterprise's identity authentication system but also achieves standardized software output. Through this technology, enterprises can easily meet their individual login needs without special customization.

[0154] This embodiment's open, customizable plugin mechanism uses login authentication as a key entry point, allowing customers to embed their customized login process code into custom plugins. In other words, this feature enables customers to insert custom login logic into the service provider's main login process code, significantly improving system scalability. Furthermore, this design avoids the problems of bloated project code and difficult-to-maintain proxy governance, maintaining system simplicity and maintainability.

[0155] Corresponding to the embodiments of the page access method described above, this specification also provides embodiments of the page access device and the computer equipment on which it is applied.

[0156] The embodiments of the page access device described in this specification can be applied to computer devices, such as servers or terminal devices. The device embodiments can be implemented through software, hardware, or a combination of both. Taking software implementation as an example, as a logical device, it is formed by its processor reading the corresponding computer program instructions from non-volatile memory into memory for execution. From a hardware perspective, such as... Figure 5 The diagram shown is a hardware structure diagram of a computer device containing the page access device described in this manual. (Except for...) Figure 5 In addition to the processor 510, network interface 520, memory 530, and non-volatile memory 540 shown, the computer device where the page access device is located in the embodiment may also include other hardware depending on the actual function of the computer device, which will not be described in detail here.

[0157] like Figure 6 As shown, Figure 6 This is a block diagram illustrating a page access device according to an exemplary embodiment of this specification, the device comprising:

[0158] Loading module 61 is used to: if it is determined that the current user accessing the target page needs to perform a custom login, load the login processing plugin corresponding to the target page;

[0159] Calling module 62 is used to: call the login processing plugin so that the login authentication system corresponding to the target page can authenticate the current user after being redirected;

[0160] The acquisition module 63 is used to: parse the login authentication result generated by the login authentication system through the login processing plugin, and obtain the parsing information of the login authentication result by the login processing plugin;

[0161] The determination module 64 is used to: determine whether the current user can access the target page based on the parsed information.

[0162] In some examples, if the loading module 61 determines that the current user accessing the target page needs to perform a custom login, it loads the login processing plugin corresponding to the target page, including:

[0163] In response to receiving the current access request to the target page, it is determined that the current user needs to perform a custom login, and the login processing plugin corresponding to the target page is loaded;

[0164] In the calling module 62, the login processing plugin is called so that the login authentication system corresponding to the target page performs identity authentication on the current user after being redirected, including:

[0165] The login processing plugin is invoked based on the access request, so that the access address of the login authentication system determined by the login processing plugin based on the access request is redirected, and the login authentication system performs identity authentication on the current user.

[0166] In some examples, the login processing plugin includes an authentication redirection module;

[0167] The calling module 62 calls the login processing plugin, including:

[0168] The authentication redirection module is invoked to return the access address of the login authentication system;

[0169] Based on the access address, the user is redirected to the login authentication system.

[0170] In some examples, the device is used in a main login module, which includes a callback interface;

[0171] The login authentication system is used to: after obtaining the login authentication result, call the callback interface based on the login authentication result;

[0172] The login processing plugin includes a login processing module;

[0173] The step of obtaining the parsing information of the login authentication result by the login processing plugin includes:

[0174] If a request to call the callback interface is received from the login authentication system, the login authentication result is obtained from the request.

[0175] After invoking the login processing module based on the login authentication result, the parsing information of the login processing module on the login authentication result is obtained.

[0176] In some examples, the determining module 63 determines whether the current user can access the target page based on the parsed information, including:

[0177] If the parsed information indicates that login authentication failed, it is determined that the current user cannot access the target page;

[0178] If the parsed information contains the current user identity information obtained by converting the login authentication result by the login processing plugin according to a preset format, it is determined that the current user can access the target page.

[0179] In some examples, the loading module 61 is also used for:

[0180] Obtain the request information of the access request and determine whether the request information conforms to the preset custom login strategy;

[0181] If the conditions are met, it is determined that the current user accessing the target page needs to perform a custom login.

[0182] like Figure 7 As shown, Figure 7 This is a block diagram illustrating another page access device according to an exemplary embodiment of this specification. The device is applied to a login processing plugin, which is loaded by the main login module after determining that the current user accessing the target page needs to perform a custom login. The device may include:

[0183] The receiving module 71 is configured to: receive the call request from the main login module so that the login authentication system corresponding to the target page can perform identity authentication on the current user after being redirected, and parse the login authentication result generated by the login authentication system;

[0184] The module 72 is configured to: provide parsing information to the main login module so that the main login module can determine whether the current user can access the target page based on the parsing information.

[0185] In some examples, the receiving module 71 receives the call request from the main login module, including:

[0186] The system receives a call request initiated by the main login module based on the current user's access request to the target page, determines the access address of the login authentication system based on the access request, redirects the access address of the login authentication system, and then the login authentication system authenticates the current user.

[0187] In some examples, the login processing plugin includes an authentication redirection module;

[0188] The receiving module 71 receives a call request initiated by the main login module based on the current user's access request to the target page, and determines the access address of the login authentication system based on the access request, including:

[0189] In response to the main login module's call request to the login processing module, the login authentication result is obtained from the call request to the login processing module, parsed, and then provided to the main login module; wherein, the call request to the login processing module is initiated by the main login module after obtaining the login authentication result from the call request from the login authentication system to the callback interface;

[0190] And / or,

[0191] The main login module includes a callback interface; the login authentication system is used to: after obtaining the login authentication result, call the callback interface based on the login authentication result; the login processing plugin also includes a login processing module;

[0192] The providing module 72 provides the parsed information to the main login module, including:

[0193] In response to the main login module's call request to the login processing module, the login authentication result is obtained from the call request to the login processing module, parsed, and then provided to the main login module; wherein, the call request to the login processing module is initiated by the main login module after obtaining the login authentication result from the call request from the login authentication system to the callback interface.

[0194] like Figure 8 As shown, Figure 8 This is a block diagram illustrating another page access device according to an exemplary embodiment of this specification, the device comprising:

[0195] Module 81 is provided for: providing users with an upload interface for login processing plugins;

[0196] The storage module 82 is used to: obtain and store the login processing plugin provided by the user through the upload interface; wherein the login processing plugin is loaded during the execution of the aforementioned method by the main login module and is used to execute the steps of the aforementioned method.

[0197] The specific implementation process of the functions and roles of each module in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0198] Accordingly, embodiments of this specification also provide a page access system, the system including a page access device and a login authentication system, the page access device being used to execute the steps of any of the foregoing method embodiments.

[0199] Accordingly, this specification also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the aforementioned page access method embodiments.

[0200] Accordingly, embodiments of this specification also provide a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the page access method embodiment.

[0201] Accordingly, embodiments of this specification also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the page access method embodiments.

[0202] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of the solution in this specification according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0203] The above embodiments can be applied to one or more computer devices. The computer device is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions. The hardware of the computer device includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0204] The computer device can be any electronic product that can interact with the user, such as a personal computer, tablet computer, smartphone, personal digital assistant (PDA), game console, interactive network television (IPTV), smart wearable device, etc.

[0205] The computer equipment may also include network equipment and / or user equipment. The network equipment includes, but is not limited to, a single network server, a server group consisting of multiple network servers, or a cloud based on cloud computing consisting of a large number of hosts or network servers.

[0206] The network in which the computer device is located includes, but is not limited to, the Internet, wide area network, metropolitan area network, local area network, and virtual private network (VPN).

[0207] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0208] The steps of the various methods described above are only for clarity. In practice, they can be combined into one step or some steps can be split into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this patent. Adding insignificant modifications or introducing insignificant designs to the algorithm or process, but without changing the core design of the algorithm and process, are also within the scope of protection of this application.

[0209] While this specification contains numerous specific implementation details, these should not be construed as limiting the scope of any invention or the scope of the claims, but rather are primarily intended to describe features of specific embodiments of a particular invention. Certain features described in the various embodiments herein may also be implemented in combination in a single embodiment. Conversely, various features described in a single embodiment may also be implemented separately in various embodiments or in any suitable sub-combination. Furthermore, while features may function in certain combinations as described above and even initially claimed in this way, one or more features from a claimed combination may be removed from that combination in some cases, and a claimed combination may refer to a sub-combination or a variation thereof.

[0210] The terms "specific example" or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with the embodiments or examples, which are included in at least one embodiment or example of this specification. In this specification, illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0211] Other embodiments of this specification will readily occur to those skilled in the art upon consideration of the specification and practice of the invention claimed herein. This specification is intended to cover any variations, uses, or adaptations that follow the general principles of this specification and include common knowledge or customary techniques in the art not claimed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this specification are indicated by the following claims.

[0212] It should be understood that this specification is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this specification is limited only by the appended claims.

[0213] The above description is merely a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection of this specification.

Claims

1. A method for accessing a webpage, the method comprising: If it is determined that the current user accessing the target page needs to perform a custom login, load the login processing plugin corresponding to the target page; The login processing plugin is invoked so that the login authentication system corresponding to the target page can authenticate the current user after being redirected; The login processing plugin parses the login authentication result generated by the login authentication system to obtain the parsing information of the login authentication result. Based on the parsed information, it is determined whether the current user can access the target page.

2. The method according to claim 1, wherein loading the login processing plugin corresponding to the target page if it is determined that the current user accessing the target page needs to perform a custom login includes: In response to receiving the current access request to the target page, it is determined that the current user needs to perform a custom login, and the login processing plugin corresponding to the target page is loaded; The step of invoking the login processing plugin to enable the login authentication system corresponding to the target page to authenticate the current user after redirection includes: The login processing plugin is invoked based on the access request, so that the access address of the login authentication system determined by the login processing plugin based on the access request is redirected, and the login authentication system performs identity authentication on the current user.

3. The method according to claim 1, wherein the login processing plugin includes an authentication redirection module; The invocation of the login processing plugin includes: The authentication redirection module is invoked to return the access address of the login authentication system; Based on the access address, the user is redirected to the login authentication system.

4. The method according to claim 1, wherein the method is applied in the main login module, and the main login module includes a callback interface; The login authentication system is used to: after obtaining the login authentication result, call the callback interface based on the login authentication result; The login processing plugin includes a login processing module; The step of obtaining the parsing information of the login authentication result by the login processing plugin includes: If a request to call the callback interface is received from the login authentication system, the login authentication result is obtained from the request. After invoking the login processing module based on the login authentication result, the parsing information of the login processing module on the login authentication result is obtained.

5. The method according to any one of claims 1 to 4, wherein determining whether the current user can access the target page based on the parsed information comprises: If the parsed information indicates that login authentication failed, it is determined that the current user cannot access the target page; If the parsed information contains the current user identity information obtained by converting the login authentication result by the login processing plugin according to a preset format, it is determined that the current user can access the target page.

6. The method according to any one of claims 2 to 4, wherein determining that the current user needs to perform a custom login includes: Obtain the request information of the access request and determine whether the request information conforms to the preset custom login strategy; If the conditions are met, it is determined that the current user accessing the target page needs to perform a custom login.

7. A page access method, the method being applied to a login processing plugin, the login processing plugin being loaded by the main login module after determining that the current user accessing the target page needs to perform a custom login; the method comprising: The system receives a call request from the main login module so that the login authentication system corresponding to the target page can authenticate the current user after being redirected, and parses the login authentication result generated by the login authentication system. The parsed information is provided to the main login module so that the main login module can determine whether the current user can access the target page based on the parsed information.

8. The method according to claim 7, wherein receiving the call request from the main login module includes: The system receives a call request initiated by the main login module based on the current user's access request to the target page, determines the access address of the login authentication system based on the access request, redirects the access address of the login authentication system, and then the login authentication system authenticates the current user.

9. The method according to claim 7 or 8, wherein the login processing plugin includes an authentication redirection module; The step of receiving the call request initiated by the main login module based on the current user's access request to the target page, and determining the access address of the login authentication system based on the access request, includes: In response to the main login module's call request to the authentication redirection module based on the access request, the access address of the login authentication system is determined based on the request information in the access request and returned, so that the main login module redirects to the login authentication system based on the access address; And / or, The main login module includes a callback interface; the login authentication system is used to: after obtaining the login authentication result, call the callback interface based on the login authentication result; The login processing plugin also includes a login processing module; Providing the parsed information to the main login module includes: In response to the main login module's call request to the login processing module, the login authentication result is obtained from the call request to the login processing module, parsed, and then provided to the main login module; wherein, the call request to the login processing module is initiated by the main login module after obtaining the login authentication result from the call request from the login authentication system to the callback interface.

10. A method for accessing a webpage, the method comprising: Provide users with an upload interface for login processing plugins; The login processing plugin provided by the user is obtained through the upload interface and stored; wherein, the login processing plugin is loaded during the execution of the method of any one of claims 1 to 6 by the main login module and is used to execute the steps of the method of any one of claims 7 to 9.

11. A page access system, the system comprising a page access device and a login authentication system, the page access device being configured to perform the steps of the method according to any one of claims 1 to 10.

12. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 10.

13. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 1 to 10.

14. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 10.

Images