CN110493184A - The processing method of login page, device, electronic device in the client - Google Patents

Abstract

The present invention provides a processing method, device, and electronic device for logging in a page in a client, wherein the method includes: receiving a service request for logging in a target H5 page in the client; obtaining a single point stored locally in the client Login credentials, where the SSO credentials are issued by the SSO authentication center based on the client's local login authorization; based on the SSO credentials, the SSO authentication center requests authorization to log in to the target H5 page. The invention solves the technical problem in the related art that the user needs to repeatedly input the login information in the H5 page when logging in the H5 page in the logged-in client.

Description

Method, device and electronic device for processing login page in client

technical field

The present invention relates to the field of computers, and in particular, to a method, device, and electronic device for processing a login page in a client.

Background technique

In order to meet the needs of browsing web pages in the native client (APP), the hybrid development mode of native+h5 can be used, in which native is the local method of realizing the client through Java and C code, and h5 is realized on the client. The function of the web page, through the combination of the native mode and the h5 mode, can display relevant information in the client through the web page, or combine the client and the web page to achieve certain functions.

However, in the prior art, the native login of the client and the h5 login are independent of each other, that is, if the user has already logged in in the client, the user still needs to log in in the h5 page when entering the h5 page in the client. Need to perform multiple login operations, the experience is not good.

For the above problems existing in the related art, no effective solution has been found so far.

SUMMARY OF THE INVENTION

The embodiments of the present invention provide a processing method, device, and electronic device for logging in a page in a client, so as to at least solve the problem that in the prior art, when logging in an H5 page in a logged-in client, the user needs to repeatedly input the login in the H5 page. Information technology issues.

According to an embodiment of the present invention, a processing method for logging in a page in a client is provided, including: receiving a service request for logging in a target H5 page in the client; acquiring a single sign-on credential stored locally in the client, The single sign-on credential is a credential issued by the single sign-on authentication center based on the client's local login authorization; based on the single sign-on credential, an authorization is requested from the single sign-on authentication center to log in to the target H5 page.

Further, acquiring the SSO credential stored locally in the client includes: in the case that the SSO credential does not exist in the client, calling out the local login interface of the client to receive the login information of the user account input by the user ; Send the login information to the SSO authentication center; Receive and store the SSO credentials authorized and issued by the SSO authentication center after the successful verification of the login information.

Further, the single sign-on credential has a valid duration, and based on the single sign-on credential, requesting authorization from the single sign-on authentication center to log in to the target H5 page includes: after the valid time period is exceeded, requesting authorization from the single sign-on authentication center based on the single sign-on credential. Request authorization fails; call up the local login interface of the client to receive the login information of the user account entered by the user; send the login information to the SSO authentication center; receive and store the SSO authentication center to verify the login information successfully. single sign-on credentials.

Further, calling out the local login interface of the client includes: calling the target native interface function through the preset JS function in the target H5 page, wherein the target native interface function is added in advance in the web page view program of the local login interface of the client. native interface function; executes the method corresponding to the target native interface function.

Further, calling out the local login interface of the client includes: jumping to the jump target page indicated in the schemaURL through the schemaURL pre-registered in the operating system for the target H5 page, wherein the jump target indicated in the schemaURL The page is the local login interface.

Further, requesting authorization from the SSO authentication center based on the SSO credential includes: monitoring whether the SSO credential is received through the JS callback function, and after receiving the SSO credential, sending the SSO credential to the SSO Log in to the certificate authority to request authorization.

According to another embodiment of the present invention, a processing device for logging in a page in a client is provided, comprising: a receiving module for receiving a service request for logging in a target H5 page in the client; an acquiring module for acquiring The single sign-on credentials stored locally in the client, wherein the single sign-on credentials are the credentials issued by the single sign-on authentication center based on the client's local login authorization; the request module is used to request the single sign-on authentication center based on the single sign-on credentials Authorization to log in to the target H5 page.

Further, the acquisition module includes: a calling unit for calling out a local login interface of the client when there is no single sign-on credential in the client to receive the login information of the user account input by the user; a sending unit for Send the login information to the single sign-on authentication center; the receiving unit is used to receive and store the single sign-on credentials authorized and issued by the single sign-on authentication center after the successful verification of the login information.

Further, the single sign-on credential has a valid duration, and the requesting module further includes: a requesting unit for requesting authorization failure from the single sign-on authentication center based on the single sign-on credential after the valid duration is exceeded; a calling unit for calling out the client The local login interface of the terminal is used to receive the login information of the user account input by the user; the sending unit is used to send the login information to the single sign-on authentication center; the receiving unit is used to receive and store the successful verification of the login information by the single sign-on authentication center Single sign-on credentials issued after authorization.

Further, the request unit is also used to call the target native interface function through the preset JS function in the target H5 page, wherein the target native interface function is the native interface function added in advance in the web page view program of the local login interface of the client; execute The method corresponding to the target native interface function.

Further, the request unit is also used to jump to the jump target page indicated in the schemaURL through the schemaURL registered in the operating system in advance for the target H5 page, wherein the jump target page indicated in the schemaURL is the local login interface .

Further, the request module is further configured to monitor whether the single sign-on credential is received through the JS callback function, and after receiving the single sign-on credential, send the single sign-on credential to the single sign-on authentication center to request authorization.

According to yet another embodiment of the present invention, a storage medium is also provided, wherein a computer program is stored in the storage medium, wherein the computer program is configured to execute the steps in any one of the above method embodiments when running.

According to yet another embodiment of the present invention, there is also provided an electronic device comprising a memory and a processor, wherein the memory stores a computer program, the processor is configured to run the computer program to execute any of the above Steps in Method Examples.

Through the present invention, by receiving the business request for logging in the target H5 page in the client; obtaining the single sign-on credential stored locally in the client, wherein the single sign-on credential is issued by the single sign-on authentication center based on the local login authorization of the client based on the single sign-on credentials to request authorization from the single sign-on authentication center to log in to the target H5 page, which solves the problem of requiring the user to repeatedly enter the login information in the H5 page when logging in to the H5 page in the logged-in client in the related technology. For technical problems, users do not need to repeatedly enter login information. If the client is logged in, they can directly log in to the H5 page.

Description of drawings

The accompanying drawings described herein are used to provide a further understanding of the present invention and constitute a part of the present application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the attached image:

1 is a flowchart of a method for processing a login page in a client according to an embodiment of the present invention;

2 is a schematic diagram of a processing apparatus for logging in a page in a client according to an embodiment of the present invention;

FIG. 3 is a block diagram of a hardware structure of an electronic device according to an embodiment of the present invention.

Detailed ways

In order to make those skilled in the art better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only It is a part of the embodiments of the present application, rather than all the embodiments, and the embodiments of the present application and the features of the embodiments may be combined with each other under the condition of no conflict. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the scope of protection of the present application.

It should be noted that the terms "first", "second", etc. in the description and claims of the present application and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence. It is to be understood that data so used may be interchanged under appropriate circumstances so that the embodiments of the application described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having" and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those expressly listed Rather, those steps or units may include other steps or units not expressly listed or inherent to these processes, methods, products or devices.

Example 1

This embodiment provides a method for processing a login page in a client, which can be applied to the client, where the client may be running a mobile terminal, a handheld terminal, or a similar computing device. Running on different computing devices is only the difference in the execution body of the solution, and those skilled in the art can predict that running on different computing devices can produce the same technical effect.

As shown in FIG. 1 , the method for processing a login page in a client provided by this embodiment includes the following steps:

Step 101: Receive a service request for logging in the target H5 page in the client.

The client is a client software (APP) installed in a terminal device (such as a mobile phone), and the local login of the client is realized by native, which is written and run based on the local operating system (such as iOS, Android, WP) of the terminal device. In addition, the client can also log in to the H5 page, and the H5 page is used to provide the service corresponding to the service request.

The native business provided in the client and the business provided in the webpage can belong to independent business systems. For example, the business provided by the client can be operations such as inquiry and transfer of bank accounts, while the business system of the H5 page is provided by the bank. Fund business information.

Step 102, obtaining a single sign-on credential stored locally in the client, wherein the single sign-on credential is a credential issued by the single sign-on authentication center based on the client's local login authorization;

In this embodiment, both the native service provided in the client and the service system provided in the webpage are managed by a single sign-on (Single Sign-On, SSO for short) authentication center.

When the client receives a service request that needs to log in to the target H5 page, it can request the client to provide the SSO credentials issued by the SSO authentication center for the client, and request authorization from the SSO authentication center based on the SSO credentials.

The single sign-on authentication center can control the access rights of multiple related but independent systems, and users with this access rights can use a single user ID and password (for example, a pre-registered account and password, or mobile phone number and SMS verification password) to access each system, thereby avoiding the use of different usernames or passwords in each business system.

When the user enters the user ID and password in the client and successfully logs in locally, the single sign-on authentication center will authorize the client (such as session), or trust the client, and generate a single sign-on credential (such as sessionID) feedback For the client, the single sign-on credential is the identification of the search authorization of the single sign-on authentication center. After any system provides the correct SSO credentials to the SSO authentication center, it will obtain the authorization provided by the SSO authentication center to log in to the corresponding business system.

In an optional application scenario, the SSO credentials generated by each local login are different, and each SSO credential is time-sensitive, that is, the validity period of the SSO credentials can be set in advance The defined period or timing expires, for example, the validity of the single sign-on credential may be a preset period of time, or expire when the client exits the front end of the terminal device. After obtaining the SSO credentials, if the client needs to request a local service, the SSO authentication center can search for the corresponding authorization (such as the session corresponding to the session ID) based on the SSO credentials sent by the client. Authorization allows the client to access the corresponding service.

In this application scenario, when requesting authorization from the SSO authentication center based on the SSO credential to log in to the target H5 page, if the validity period expires, the request for authorization from the SSO authentication center based on the SSO credential will fail. , the client will call up the local login interface of the client to receive the login information of the user account entered by the user, and send the login information to the SSO authentication center; receive and store the SSO authentication center to authorize after the successful verification of the login information Issued single sign-on credentials.

Optionally, when obtaining SSO credentials stored locally in the client, there are two situations:

The first case is that the client has already logged in locally. At this time, you can request authorization in the single sign-on authentication center, so as to log in to the business system corresponding to the business requesting the H5 page, realize the access to the H5 page, and realize the corresponding business function.

The second case is that the client has not logged in locally. In this case, authorization cannot be requested in the single sign-on authentication center, so that the business system corresponding to the business requesting the H5 page cannot be logged in. Call up the local login interface of the client, and receive the account password entered by the user through the local login interface.

Optionally, the above method of calling out the local login interface can be implemented by js-native or schemaUrl.

If the js-native method is adopted, the steps of calling up the local login interface of the client may include: calling the target native interface function through the preset JS function in the target H5 page, wherein the target native interface function is the local login interface of the client in advance The native interface function added in the web view program of the , executes the method corresponding to the target native interface function.

For example, you can add a native interface function for the H5 page to call in the web page view program of the client's local login interface in advance; when the H5 page receives an access command, the H5 page uses the preset Js function in the H5 page to call the native interface function. The interface function name is sent to the native to call the name of the native interface function preset in the local login interface of the client, so that the H5 page can call the local login interface.

If the schemaUrl method is adopted, the local login interface of the client is called up, including: jumping to the jump target page indicated in the schemaURL through the schemaURL pre-registered in the operating system for the target H5 page, wherein the indicated in the schemaURL The jump target page is the local login interface.

For example, a schemaUrl is pre-registered with the operating system, and the registered schemaUrl includes a URL link and a jump target page (that is, the login interface of the local client). When the registered URL page link (the parameters of the URL page link carry parameters indicating the need to log in and not currently logged in, that is, the visited URL page link is the page that needs to be logged in and is not currently logged in) is accessed, the operation The page jump routing center of the system determines the jump target page according to the pre-registered schemaURL, thereby instructing the client to jump to the local login interface specified in the schemaURL.

After receiving the account password entered by the user through the local login interface, the account password is sent to the single sign-on authentication center. Among them, if the single sign-on authentication center verifies that the login is successful, it will feed back a single sign-on credential to the client. With the single sign-on credential, you can log in to all business systems managed by the single sign-on authentication center, including the local The business system corresponding to the business in the client and the business system corresponding to the business in the H5 page. Furthermore, after the client obtains the SSO credentials, the H5 page can re-obtain the client SSO credentials by calling back JS, and request authorization from the SSO authentication center based on the SSO credentials, which is implemented in the H5 page. The effect of automatic login.

Step 103 , request authorization from the single sign-on authentication center based on the single sign-on credential to log in to the target H5 page.

After obtaining the single sign-on credentials, send it to the single sign-on authentication center to request authorization. After the single sign-on authentication center is authorized, log in to the target H5 page.

Requesting authorization from the SSO authentication center based on the SSO credentials, including: monitoring whether the SSO credentials are received through the JS callback function, and sending the SSO credentials to the SSO authentication after receiving the SSO credentials The center requests authorization.

This embodiment uniformly manages the mutual login authentication of all business systems through the single sign-on authentication center, so that after the business system corresponding to the local business in the client is successfully logged in, it can be recognized by the business system of the business provided in the H5 page, And use the mutual call between the H5 page and the client native to obtain the single sign-on credentials for the client's local login, and when the client is not logged in locally, call up the local login interface to execute the login process, and log in locally. Realize the effect of logging in on the H5 page, simplifies the operation process of logging in to the H5 page in the client, and does not require the user to log in separately in the client and the H5 page, which greatly improves the user experience.

It should be noted that the steps shown in the flowcharts of the accompanying drawings may be executed in a computer system, such as a set of computer-executable instructions, and, although a logical sequence is shown in the flowcharts, in some cases, Steps shown or described may be performed in an order different from that herein.

From the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation. Based on this understanding, the technical solutions of the present invention can be embodied in the form of software products in essence or the parts that make contributions to the prior art, and the computer software products are stored in a storage medium (such as ROM/RAM, magnetic disk, CD-ROM), including several instructions to make a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in the various embodiments of the present invention.

Example 2

This embodiment also provides a processing device for logging in a page in a client. The device is used to implement the above-mentioned Embodiment 1 and its preferred implementation. For terms or implementations that are not described in detail in this embodiment, you can Refer to the relevant descriptions in Embodiment 1, and those that have already been described will not be repeated.

The term "module", as used below, is a combination of software and/or hardware that can implement predetermined functions. Although the devices described in the following embodiments are preferably implemented in software, implementations in hardware, or a combination of software and hardware, are also contemplated.

FIG. 2 is a schematic diagram of an apparatus for processing a login page in a client according to an embodiment of the present invention. As shown in FIG. 2 , the apparatus includes: a receiving module 10 , an obtaining module 20 , and a requesting module 30 .

The receiving module is used to receive the business request for logging in the target H5 page in the client; the obtaining module is used to obtain the single sign-on credential stored locally in the client, wherein the single sign-on credential is that the single sign-on authentication center is based on the client The certificate issued by the local login authorization of the terminal; the request module is used to request authorization from the single sign-on authentication center based on the single sign-on certificate to log in to the target H5 page.

Optionally, the obtaining module includes: a calling unit, used for calling out the local login interface of the client when there is no single sign-on credential in the client, to receive the login information of the user account input by the user; the sending unit, using It is used to send the login information to the single sign-on authentication center; the receiving unit is used to receive and store the single sign-on certificate authorized and issued by the single sign-on authentication center after the successful verification of the login information.

Optionally, the single sign-on credential has a valid duration, and the requesting module further includes: a request unit, used to request authorization failure from the single sign-on authentication center based on the single sign-on credential after the valid duration is exceeded; a calling unit, used to call out The local login interface of the client is used to receive the login information of the user account input by the user; the sending unit is used to send the login information to the single sign-on authentication center; the receiving unit is used to receive and store the authentication of the login information by the single sign-on authentication center A single sign-on credential issued after a successful authorization.

Optionally, the requesting unit is further configured to call the target native interface function through the preset JS function in the target H5 page, wherein the target native interface function is a native interface function added in advance in the web page view program of the local login interface of the client; Execute the method corresponding to the target native interface function.

Optionally, the requesting unit is further configured to jump to the jump target page indicated in the schemaURL through the schemaURL pre-registered in the operating system for the target H5 page, where the jump target page indicated in the schemaURL is a local login interface.

Optionally, the request module is further configured to monitor whether the single sign-on credential is received through the JS callback function, and after receiving the single sign-on credential, send the single sign-on credential to the single sign-on authentication center to request authorization.

Through the present invention, by receiving the business request for logging in the target H5 page in the client; obtaining the single sign-on credential stored locally in the client, wherein the single sign-on credential is issued by the single sign-on authentication center based on the local login authorization of the client based on the single sign-on credentials to request authorization from the single sign-on authentication center to log in to the target H5 page, which solves the problem of requiring the user to repeatedly enter the login information in the H5 page when logging in to the H5 page in the logged-in client in the related technology. For technical problems, users do not need to repeatedly enter login information. If the client is logged in, they can directly log in to the H5 page.

It should be noted that the above modules can be implemented by software or hardware, and the latter can be implemented in the following ways, but not limited to this: the above modules are all located in the same processor; or, the above modules can be combined in any combination The forms are located in different processors.

Obviously, those skilled in the art should understand that the above-mentioned modules or steps of the present invention can be implemented by a general-purpose computing device, which can be centralized on a single computing device, or distributed in a network composed of multiple computing devices Alternatively, they may be implemented in program code executable by a computing device, such that they may be stored in a storage device and executed by the computing device, and in some cases, in a different order than here The steps shown or described are performed either by fabricating them separately into individual integrated circuit modules, or by fabricating multiple modules or steps of them into a single integrated circuit module. As such, the present invention is not limited to any particular combination of hardware and software.

Example 3

An embodiment of the present invention further provides a storage medium, where a computer program is stored in the storage medium, wherein the computer program is configured to execute the steps in any one of the above method embodiments when running.

Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: a USB flash drive, a read-only memory (Read-Only Memory, referred to as ROM), a random access memory (Random Access Memory, referred to as RAM), Various media that can store computer programs, such as removable hard disks, magnetic disks, or optical disks.

This embodiment uniformly manages the mutual login authentication of all business systems through the single sign-on authentication center, so that after the business system corresponding to the local business in the client is successfully logged in, it can be recognized by the business system of the business provided in the H5 page, And use the mutual call between the H5 page and the client native to obtain the single sign-on credentials for the client's local login, and when the client is not logged in locally, call up the local login interface to execute the login process, and log in locally. Realize the effect of logging in on the H5 page, simplifies the operation process of logging in to the H5 page in the client, and does not require the user to log in separately in the client and the H5 page, which greatly improves the user experience.

Example 4

An embodiment of the present invention also provides an electronic device, comprising a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any of the above method embodiments.

This embodiment uniformly manages the mutual login authentication of all business systems through the single sign-on authentication center, so that after the business system corresponding to the local business in the client is successfully logged in, it can be recognized by the business system of the business provided in the H5 page, And use the mutual call between the H5 page and the client native to obtain the single sign-on credentials for the client's local login, and when the client is not logged in locally, call up the local login interface to execute the login process, and log in locally. Realize the effect of logging in on the H5 page, simplifies the operation process of logging in to the H5 page in the client, and does not require the user to log in separately in the client and the H5 page, which greatly improves the user experience.

Optionally, the above-mentioned electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the above-mentioned processor, and the input-output device is connected to the above-mentioned processor. Taking the electronic device as an electronic device as an example, FIG. 3 is a block diagram of a hardware structure of an electronic device according to an embodiment of the present invention. As shown in FIG. 3 , the electronic device may include one or more (only one is shown in FIG. 3 ) processor 302 (the processor 302 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 304 for storing data, optionally, the above electronic device may further include a transmission device 306 and an input/output device 308 for communication functions. Those skilled in the art can understand that the structure shown in FIG. 3 is only a schematic diagram, which does not limit the structure of the above electronic device. For example, the electronic device may also include more or fewer components than shown in FIG. 3 , or have a different configuration than that shown in FIG. 3 .

The memory 304 can be used to store computer programs, for example, software programs and modules of application software, such as computer programs corresponding to the image recognition method in the embodiment of the present invention. The processor 302 executes the computer programs stored in the memory 304 by running the computer programs. Various functional applications and data processing implement the above method. Memory 304 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, memory 304 may further include memory located remotely from processor 302, which may be connected to the electronic device through a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

Transmission means 306 is used to receive or transmit data via a network. A specific example of the above-mentioned network may include a wireless network provided by a communication provider of the electronic device. In one example, the transmission device 306 includes a network adapter (Network Interface Controller, NIC for short), which can be connected to other network devices through the base station so as to communicate with the Internet. In one example, the transmission device 306 may be a radio frequency (Radio Frequency, RF for short) module, which is used to communicate with the Internet in a wireless manner.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the principle of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. a kind of processing method of login page in the client, which is characterized in that the described method includes:

Receive the service request for logging in the target H5 page in the client；

Obtain the single-sign-on voucher being locally stored in the client, wherein the single-sign-on voucher is single-sign-on The voucher of the client-based local log-on authorization granting of authentication center；

Based on the single-sign-on voucher to the single sign-on authentication center requests authorization, to log in the target H5 page.

2. the method according to claim 1, wherein described obtain the single-point being locally stored in the client Logging on authentication, comprising:

In the case where the single-sign-on voucher is not present in the client, local log-on circle of the client is recalled Face, to receive the log-on message of the user account of user's input；

The log-on message is sent to the single sign-on authentication center；

Receive and store the list that authorization is provided after the single sign-on authentication center is proved to be successful the log-on message Point logging on authentication.

3. the method according to claim 1, wherein the single-sign-on voucher has effective time, the base In the single-sign-on voucher to the single sign-on authentication center requests authorization, to log in the target H5 page, comprising:

After beyond the effective time, the single-sign-on voucher is based on to the single sign-on authentication center requests authorization Failure；

The local log-on interface of the client is recalled, to receive the log-on message of the user account of user's input；

The log-on message is sent to the single sign-on authentication center；

Receive and store the list that authorization is provided after the single sign-on authentication center is proved to be successful the log-on message Point logging on authentication.

4. according to the method in claim 2 or 3, which is characterized in that the local log-on interface for recalling the client, Include:

Pass through the default JS function call target native interface function in the target H5 page, wherein the target Native interface function is that the native added in the webpage view program at the local log-on interface of the client in advance connects Mouth function；

Execute the corresponding method of the target native interface function.

5. according to the method in claim 2 or 3, which is characterized in that the local log-on interface for recalling the client, Include:

By the schemaURL registered in an operating system in advance for the target H5 page, the schemaURL is jumped to In the indicated jump target page, wherein the indicated jump target page is the local log-on in the schemaURL Interface.

6. the method according to claim 1, wherein described stepped on based on the single-sign-on voucher to the single-point Record authentication center's request authorization, comprising:

Monitor whether to receive the single-sign-on voucher by JS call back function, and receive the single-sign-on voucher it The single-sign-on voucher is sent to the single sign-on authentication center requests authorization afterwards.

7. a kind of processing unit of login page in the client, which is characterized in that described device includes:

Receiving module, for receiving the service request for logging in the target H5 page in the client；

Obtain module, for obtaining the single-sign-on voucher being locally stored in the client, wherein the single-sign-on with Card is the voucher of the client-based local log-on authorization granting in single sign-on authentication center；

Request module, for being based on the single-sign-on voucher to the single sign-on authentication center requests authorization, to log in State the target H5 page.

8. device according to claim 7, which is characterized in that the acquisition module includes:

Call unit recalls the client in the case where for the single-sign-on voucher to be not present in the client Local log-on interface, with receive user input user account log-on message；

Transmission unit, for the log-on message to be sent to the single sign-on authentication center；

Receiving unit is authorized for receiving and storing after the single sign-on authentication center is proved to be successful the log-on message The single-sign-on voucher provided.

9. a kind of storage medium, which is characterized in that be stored with computer program in the storage medium, wherein the computer Program is arranged to perform claim when operation and requires method described in 1 to 6 any one.

10. a kind of electronic device, including memory and processor, which is characterized in that be stored with computer journey in the memory Sequence, the processor are arranged to run the computer program in method described in perform claim 1 to 6 any one of requirement.