WO2018028448A1 - 一种认证方法、设备以及认证客户端 - Google Patents

一种认证方法、设备以及认证客户端 Download PDF

Info

Publication number
WO2018028448A1
WO2018028448A1 PCT/CN2017/095110 CN2017095110W WO2018028448A1 WO 2018028448 A1 WO2018028448 A1 WO 2018028448A1 CN 2017095110 W CN2017095110 W CN 2017095110W WO 2018028448 A1 WO2018028448 A1 WO 2018028448A1
Authority
WO
WIPO (PCT)
Prior art keywords
authentication
browser
information
jump
request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2017/095110
Other languages
English (en)
French (fr)
Inventor
张娜娜
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to JP2019507769A priority Critical patent/JP6708784B2/ja
Priority to KR1020197007139A priority patent/KR102175117B1/ko
Priority to EP17838578.7A priority patent/EP3499836B1/en
Priority to SG11201901102SA priority patent/SG11201901102SA/en
Priority to KR1020207031517A priority patent/KR102289994B1/ko
Publication of WO2018028448A1 publication Critical patent/WO2018028448A1/zh
Priority to US16/272,852 priority patent/US10686786B2/en
Priority to PH12019500293A priority patent/PH12019500293A1/en
Anticipated expiration legal-status Critical
Priority to US16/867,527 priority patent/US10798095B2/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/36—User authentication by graphic or iconic representation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
    • G06F16/9558—Details of hyperlinks; Management of linked annotations
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/45—Structures or tools for the administration of authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0884—Network architectures or network communication protocols for network security for authentication of entities by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0892—Network architectures or network communication protocols for network security for authentication of entities by using authentication-authorization-accounting [AAA] servers or protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H04W12/084—Access security using delegated authorisation, e.g. open authorisation [OAuth] protocol

Definitions

  • the present application relates to the field of Internet information processing technologies, and in particular, to an authentication method, a device, and an authentication client.
  • the current authentication method generally includes the following:
  • the user equipment used by the user A obtains the link address of the authentication page from the user B in some manner;
  • user A starts any browser installed in the user equipment used, and loads the authentication page corresponding to the link address obtained in the first step in the browser;
  • the user A enters the identity information to be authenticated in the authentication page, and sends an authentication request to the authentication client, where the authentication request includes the identity information to be authenticated.
  • the authentication client when the authentication client receives the authentication request, the authentication client authenticates the identity information to be authenticated included in the authentication request.
  • the authentication client pushes the authentication result to the default browser.
  • the embodiment of the present application provides an authentication method, a device, and an authentication client, which are used to solve the present problem.
  • An embodiment of the present application provides an authentication method, including:
  • the authentication client receives the authentication request sent by the target browser, where the authentication request includes information to be authenticated and a jump parameter for implementing a jump between the target browser and the authentication client.
  • the authentication client After the authentication client obtains the authentication result, the authentication client searches for the identifier information of the target browser that matches the jump parameter from the mapping file according to the jump parameter,
  • the mapping file includes a mapping relationship between the identifier information of different browsers and the jump parameters of the browser;
  • the authentication client sends a page jump request to the target browser according to the identifier information of the target browser, where the page jump request includes the authentication result.
  • the embodiment of the present application further provides an authentication method, including:
  • the browser determines that the time difference between the first time and the second time is greater than a set threshold, the browser sends an authentication result obtaining request to the authentication client, where the authentication result obtaining request is used to obtain the The authentication result of the information to be authenticated;
  • the browser displays the authentication result when receiving the authentication result sent by the authentication client.
  • the embodiment of the present application further provides an authentication device, including:
  • a search unit after authenticating the information to be authenticated to obtain an authentication result, searching, according to the jump parameter, identifier information of the target browser that matches the jump parameter from a mapping file, where the mapping file is Included in the mapping relationship between the identifier information of different browsers and the jump parameters of the browser;
  • a sending unit configured to send a page jump request to the target browser according to the identifier information of the target browser, where the page jump request includes the authentication result.
  • the embodiment of the present application further provides an authentication device, including:
  • a determining unit determining a first time to send an authentication request to the authentication client, and a second time after performing the jump operation after the sending the authentication request, where the authentication request includes information to be authenticated;
  • the sending unit when determining that the time difference between the first time and the second time is greater than a set threshold, sending an authentication result obtaining request to the authentication client, where the authentication result obtaining request is used to obtain the waiting The authentication result of the authentication information;
  • the display unit displays the authentication result when receiving the authentication result sent by the authentication client.
  • the embodiment of the present application further provides an authentication client, where the authentication client includes: a memory, a signal receiver, a signal transmitter, and a processor, where:
  • mapping file includes a mapping relationship between identifier information of different browsers and a jump parameter of the browser
  • a signal receiver configured to receive an authentication request sent by the target browser, where the authentication request includes information to be authenticated and a jump parameter for implementing a jump between the target browser and the authentication client;
  • the processor running the program code stored in the memory, performs the following operations:
  • mapping file After authenticating the to-be-authenticated information received by the signal receiver to obtain an authentication result, searching, according to the jump parameter received by the signal receiver, the mapping file to find the matching with the jump parameter.
  • the mapping information of the target browser, the mapping file includes a mapping relationship between the identifier information of the different browsers and the jump parameter of the browser; and the indication signal transmitter according to the identification information of the target browser.
  • the target browser sends a page jump request, where the page jump request includes the authentication result;
  • the signal transmitter sends a page jump request to the target browser according to the identification information of the target browser.
  • the authentication client receives the authentication request sent by the target browser, where the authentication request includes information to be authenticated and a jump parameter for implementing a jump between the target browser and the authentication client; After the authentication information is authenticated and the authentication result is obtained, the identifier information of the target browser that matches the jump parameter is searched from the mapping file according to the jump parameter, where the mapping file includes different browsers. a mapping relationship between the identifier information and the jump parameter of the browser; sending, according to the identifier information of the target browser, a page jump request to the target browser, where the page jump request includes the authentication result.
  • the authentication client can determine the original browser that sends the authentication request according to the jump parameter carried in the authentication request, so that the authentication client sends the authentication result to the original browser, thereby effectively avoiding
  • the authentication client cannot accurately locate the original browser that sends the authentication request, which causes the authentication result to be lost, and improves the authentication efficiency.
  • FIG. 1 is a schematic flowchart of an authentication method according to an embodiment of the present application
  • FIG. 2 is a schematic diagram of a method for determining a mapping file according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart of an authentication method according to an embodiment of the present disclosure
  • FIG. 4 is a schematic flowchart of an authentication method according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a scenario of an authentication method according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of an authentication device according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of an authentication device according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of an authentication client according to an embodiment of the present disclosure.
  • the application software cannot accurately obtain which other application software is installed on the user equipment at the same time, then according to the prior art, the authentication client is After the information is authenticated, it is impossible to determine whether the browser is the same as the browser used to send the authentication request. Therefore, the authentication result can only be sent to the default browser of the authentication client, so that the default browser receives the authentication. As a result, the authentication result cannot be identified, which leads to the loss of user information. At this time, the authentication request has to be re-initiated, resulting in prolonged authentication process.
  • an embodiment of the present application provides an authentication method, a device, and an authentication client, where an authentication client receives an authentication request sent by a target browser, where the authentication request includes information to be authenticated and is used for implementation.
  • a jump parameter that is jumped between the target browser and the authentication client; and after authenticating the to-be-authenticated information to obtain an authentication result, searching and searching from the mapping file according to the jump parameter
  • the mapping information of the target browser is matched by the jump parameter, and the mapping file includes a mapping relationship between the identifier information of the different browsers and the jump parameter of the browser; and the identifier information of the target browser is Sending a page jump request to the target browser, where the page jump request includes the authentication result.
  • the authentication client can determine the original browser that sends the authentication request according to the jump parameter carried in the authentication request, so that the authentication client sends the authentication result to the original browser, thereby effectively avoiding
  • the authentication client cannot accurately locate the original browser that sends the authentication request, which causes the authentication result to be lost, and improves the authentication efficiency.
  • the scenario applied by the embodiment of the present application may include an authentication request initiated by the browser, where the authentication request is redirected to an authentication application, and the authentication application authenticates the authentication information included in the authentication request. And display the certification results in the original browser.
  • user A obtains a link address of an authentication page by scanning code, and randomly selects a browser to load an authentication page corresponding to the link address; user A inputs information requiring authentication in the loaded authentication page, and browses through the browsing.
  • the device sends the information to be authenticated to the authentication client.
  • the authentication client can be installed in the user device used by user B. Then, the authentication client authenticates the received information that needs to be authenticated, and successfully calls when the authentication succeeds.
  • the same browser as User A selected and displays the authentication results in the browser's page.
  • the authentication client provided by the embodiment of the present application can support the iOS operating system, and can also support the iOS-like operating system, which is not specifically limited herein.
  • the identifier information of the browser described in the embodiment of the present application may be read from the installation package of the browser.
  • the identifier information of the browser may also be referred to as a browser identifier. (or source application).
  • Different browsers have different jump parameters that are called when the jump operation is performed. This difference may refer to different formats or other differences, and is not specifically limited herein.
  • the common feature is that the jump parameter contains the identifier of the browser.
  • FIG. 1 is a schematic flowchart diagram of an authentication method according to an embodiment of the present application. The method can be as follows.
  • Step 101 The authentication client receives an authentication request sent by the target browser, where the authentication request includes information to be authenticated and a jump parameter for implementing a jump between the target browser and the authentication client.
  • step 101 an application scenario is assumed.
  • user B needs to authenticate the information provided by user A (here, identity information is included).
  • user B is directed to User A provides the link address of an authentication page.
  • the link address of the authentication page may be the real address information, the two-dimensional code format, or other forms, which are not specifically limited herein.
  • link address of the authentication page provided by user B to user A is a two-dimensional code
  • user A obtains the link address of the authentication page by scanning code or other means, and starts any one installed in the user equipment used by user A.
  • the browser sends an authentication page access request to the server, where the authentication page access request includes a link address; the browser receives the page information sent by the server, and displays the page information.
  • User A enters the information to be authenticated in the displayed page, and triggers the authentication control in the page, which is regarded as the initiation of authentication. request. Because the authentication control includes the address of the authentication client, a page jump request is initiated, and the page jump request includes the jump parameter and the information to be authenticated, and the jump to the authentication client.
  • the page jump request here can be regarded as initiating an authentication request to the authentication client.
  • the jump parameter here may be a scheme parameter, that is, a Uniform Resource Identifier (or URI) of a local application is opened in the iOS operating system, and the URI is used to identify a string of a certain Internet resource name. In the embodiment, it can be understood as the name string of the browser.
  • a Uniform Resource Identifier or URI
  • the jump parameter is generated, and the identifier information of the browser included in the jump parameter (ie, the name string of the browser) is determined, so that the jump parameter can be determined according to the jump parameter. Which browser is executed by the jump operation.
  • the method further includes:
  • the information to be authenticated input by the user is encrypted, and the encrypted information to be authenticated is obtained.
  • a token is generated according to the user identity information, and the token can be regarded as the encrypted information to be authenticated.
  • the encrypted information to be authenticated may be carried in the authentication request and sent to the authentication client.
  • the authentication client receives the authentication request sent by the browser.
  • Step 102 The authentication client authenticates the to-be-authenticated information to obtain an authentication result.
  • step 102 the authentication client parses the received to-be-authenticated information, and if it is determined that the to-be-authenticated information is encrypted identity authentication information, decrypts the encrypted identity authentication information included in the authentication request, and The decrypted identity authentication information is authenticated and the authentication result is obtained.
  • the authentication information to be authenticated is determined to be non-encrypted identity authentication information, the authentication information is directly authenticated, and the authentication result is obtained.
  • the method further includes:
  • the authentication client may further determine whether the authentication request is sent by the browser or sent by the application software. If the result of the determination is sent by the browser, proceed to step 103;
  • the authentication result is sent to the application software.
  • the authentication request received by the authentication client in step 101 may be sent by the browser, or may be sent by the application software, and is not specifically limited herein.
  • the manner of determining whether the authentication request is sent by the browser or sent by the application software includes but is not limited to:
  • the authentication result is parsed. If the authentication result contains a page address, and the header field of the page address is http/https, it is determined that the authentication request is sent by the browser. Otherwise, it is determined that the authentication request is sent by the application software.
  • Step 103 The authentication client searches, according to the jump parameter, the identifier information of the target browser that matches the jump parameter from the mapping file, where the mapping file includes identifier information of different browsers. The mapping relationship between the jump parameters of the browser.
  • step 103 the authentication client obtains the source Application parameter when receiving the authentication request.
  • the operating system of the user equipment invokes the running information of the browser to obtain the source application parameter (ie, [-application:open URL:source Application:annotation]). And determining, according to the obtained source application parameter, the jump parameter, and the jump parameter is carried in the authentication request and sent to the authentication client, so that the authentication client can determine the identifier information of the original browser that performs the jump operation from the jump parameter. .
  • the source application parameter ie, [-application:open URL:source Application:annotation]
  • the authentication client searches for the identifier information of the browser corresponding to the received jump parameter from the mapping file according to the mapping relationship between the stored identifier information of the browser and the jump parameter, according to the search.
  • the identification information of the browser to which it is determined determines the original browser that performs the jump operation.
  • the method further includes:
  • the authentication client sends a mapping file update request including the jump parameter to the server when the identifier information of the target browser matched by the jump parameter is not found in the mapping file, and the mapping file is updated.
  • the request is used by the server to determine identification information of a browser that matches the jump parameter according to the jump parameter and update the mapping file.
  • mapping file may be generated by the server and sent to the authentication client, or may be generated by the authentication client, which is not limited herein.
  • the authentication client when the authentication client does not find the identifier information of the target browser that matches the jump parameter from the mapping file, the authentication client stores the source application parameter, and the next cold start The stored source Application parameters are sent to the server.
  • the server When receiving the source Application parameter, the server searches for the browser corresponding to the source Application parameter, and downloads the installation package of the browser, decompresses the installation package of the browser, obtains the ipa package of the browser, and obtains the info from the ipa package. .plist file. Find the URL typeset from the info.plist file, and determine the URL Schems corresponding to the URL typeset, find the scheme corresponding to the browser from the URL Schems, and establish the mapping relationship between the identifier information of the found browser and the scheme, and use The established mapping relationship updates the mapping file.
  • the server updates the mapping file
  • the authentication client restarts, it will update the mapping text.
  • the piece is sent to the authentication client.
  • mapping file is determined.
  • FIG. 2 is a schematic diagram of a method for determining a mapping file according to an embodiment of the present disclosure.
  • S2021 Select an installation package of one of the browsers, and read an info.plist file from the installation package, where the info.plist file contains at least one key-value pair of the browser.
  • the installation package of the selected browser is decompressed, the ipa package of the browser is obtained, and the info.plist file is obtained from the ipa package. Multiple key-value pairs for the browser are included in this info.plist file.
  • These key-value pairs contain key-value pairs of the browser's identification information and the browser's jump parameters.
  • the URL typeset is searched from the info.plist file, and the URL Schems corresponding to the URL typeset is determined, and the scheme corresponding to the browser is found from the URL Schems, and the scheme can be called a jump parameter.
  • the name corresponding to the scheme is selected to be the closest to the name of the browser.
  • the Bundle identifier (the source information of the browser) is searched from the info.plist file, and the combination of the Bundle identifier and the selected scheme is referred to as the determined identifier information of the browser and the browser.
  • the key-value pair of the jump parameter is searched from the info.plist file, and the combination of the Bundle identifier and the selected scheme.
  • S2023 Determine a mapping relationship between the identifier information of the browser and the jump parameter of the browser, and store the mapping relationship into the mapping file.
  • Step 104 The authentication client sends a page jump request to the target browser according to the identifier information of the target browser, where the page jump request includes the authentication result.
  • step 104 the authentication client sends a page jump request to the target browser according to the identifier information of the target browser, so that the target browser displays a page jump when receiving the page jump request.
  • the result of the certification contained in the request is the result of the certification contained in the request.
  • the authentication client receives the authentication request sent by the target browser, where the authentication request includes the information to be authenticated and is used to implement the target browser and the authentication client. a jump parameter of the jump; and after authenticating the information to be authenticated to obtain an authentication result, searching, according to the jump parameter, the identifier information of the target browser that matches the jump parameter from the mapping file , the mapping text
  • the device includes a mapping relationship between the identifier information of the different browsers and the jump parameter of the browser; sending, according to the identifier information of the target browser, a page jump request to the target browser, where the page jumps
  • the certification result is included in the transfer request.
  • the authentication client can determine the original browser that sends the authentication request according to the jump parameter carried in the authentication request, so that the authentication client sends the authentication result to the original browser, thereby effectively avoiding
  • the authentication client cannot accurately locate the original browser that sends the authentication request, which causes the authentication result to be lost, and improves the authentication efficiency.
  • FIG. 3 is a schematic flowchart diagram of an authentication method according to an embodiment of the present application. The method can be as follows.
  • Step 301 The browser determines a first time to send an authentication request to the authentication client, and a second time after the jump operation is performed after the authentication request is issued, where the authentication request includes information to be authenticated.
  • step 301 when the user A and the user B conduct business cooperation through negotiation, the user B needs to authenticate the information provided by the user A (here, the identity information is included). At this time, the user B provides the user A with an authentication page.
  • Link address In the embodiment of the present application, the link address of the authentication page may be the real address information, the two-dimensional code format, or other forms, which are not specifically limited herein.
  • link address of the authentication page provided by user B to user A is a two-dimensional code
  • user A obtains the link address of the authentication page by scanning code or other means, and starts any one installed in the user equipment used by user A.
  • the browser sends an authentication page access request to the server, where the authentication page access request includes a link address; the browser receives the page information sent by the server, and displays the page information.
  • User A enters the information to be authenticated in the displayed page, and triggers the authentication control in the page, which is regarded as the initiation of the authentication request.
  • the browser records the timestamp of the authentication control that triggered the page, and records it as the first time.
  • the browser After the authentication control in the page is triggered, the browser performs a jump operation. At this time, when the execution of the jump operation is completed, the time stamp when the jump operation is completed is recorded, and is recorded as the second time.
  • Step 302 The browser determines whether the time difference between the first time and the second time is greater than a set threshold according to the first time and the second time, if yes, executing step 303; Otherwise, step 305 is performed.
  • step 302 a time difference between the first time and the second time is calculated, and a magnitude relationship between the time difference and the set threshold is further determined.
  • the threshold value may be determined according to actual needs, or may be determined according to test data, and is not specifically limited herein. For example: set the threshold to 2s.
  • the code logic will be blocked.
  • the jump to the authentication client if the time difference between the first time and the second time is greater than a set threshold, determining that the jump is successful, if the first time and the first If the time difference between the two times is not greater than the set threshold, it is determined that the jump fails.
  • Step 303 The browser sends an authentication result obtaining request to the authentication client, where the authentication result obtaining request is used to obtain the authentication result of the to-be-authenticated information.
  • Step 304 The browser displays the authentication result when receiving the authentication result sent by the authentication client.
  • Step 305 The browser displays installation prompt information of the authentication client.
  • FIG. 4 is a schematic flowchart diagram of an authentication method according to an embodiment of the present application. The method can be as follows.
  • Step 401 The target browser sends an authentication request to the authentication client.
  • Step 402 The target browser determines a first time to send an authentication request to the authentication client.
  • Step 403 The second time after the target browser performs the jump operation after the authentication request is issued.
  • Step 404 The browser determines whether the time difference between the first time and the second time is greater than a set threshold according to the first time and the second time, if yes, executing step 409; Otherwise, step 410 is performed.
  • Step 405 The authentication client receives an authentication request sent by the target browser, where the authentication request includes information to be authenticated and a jump parameter for implementing a jump between the target browser and the authentication client.
  • Step 406 The authentication client authenticates the information to be authenticated to obtain an authentication result.
  • step 406 the browser sends an authentication result obtaining request to the authentication client, where the authentication result obtaining request is used to obtain the authentication result of the information to be authenticated, and the step 409 is performed.
  • Step 407 The authentication client searches, according to the jump parameter, the identifier information of the target browser that matches the jump parameter from the mapping file, where the mapping file includes identifier information of different browsers. The mapping relationship between the jump parameters of the browser.
  • Step 408 The authentication client sends a page jump request to the target browser according to the identifier information of the target browser, where the page jump request includes the authentication result.
  • step 402 to step 404 and step 405 to step 408 in the embodiment of the present application may be performed simultaneously or in a sequential manner.
  • Step 409 The browser displays the authentication result when receiving the authentication result sent by the authentication client.
  • Step 410 The browser displays installation prompt information of the authentication client.
  • FIG. 5 is a schematic diagram of a scenario of an authentication method according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of an authentication device according to an embodiment of the present disclosure.
  • the authentication device includes: a receiving unit 61, a searching unit 62, and a sending unit 63, where:
  • the receiving unit 61 receives an authentication request sent by the target browser, where the authentication request includes information to be authenticated and a jump parameter for implementing a jump between the target browser and the authentication device;
  • the searching unit 62 after authenticating the information to be authenticated to obtain an authentication result, according to the jump parameter, searching, from the mapping file, identifier information of the target browser that matches the jump parameter, the mapping
  • the file includes a mapping relationship between the identifier information of different browsers and the jump parameters of the browser;
  • the sending unit 63 is configured to send a page jump request to the target browser according to the identifier information of the target browser, where the page jump request includes the authentication result.
  • the authentication device further includes: an update unit 64, where:
  • the updating unit 64 when not finding the identification information of the target browser that the jump parameter matches from the mapping file, sending a mapping file update request including the jump parameter to the server, where the mapping file is An update request is used by the server to determine identification information of a browser that matches the jump parameter according to the jump parameter and update the mapping file.
  • the searching unit 62 searches, according to the jump parameter, the identifier information of the target browser that matches the jump parameter from the mapping file, including:
  • mapping relationship between the identifier information of the browser and the jump parameter stored in the mapping file a mapping relationship exists between the mapping file and the jump parameter included in the received authentication request.
  • the identification information of the target browser is not limited to the mapping relationship between the identifier information of the browser and the jump parameter stored in the mapping file.
  • the authentication device further includes: a mapping file generating unit 65, wherein:
  • the mapping file generating unit 65 obtains the mapping file by:
  • the to-be-authenticated information is encrypted identity authentication information
  • the authentication device further includes an authentication unit 66, wherein:
  • the authentication unit 66 performs authentication on the information to be authenticated to obtain an authentication result, and includes:
  • the authentication device described in the embodiment of the present disclosure may be implemented by using a software, or may be implemented by using a hardware, and is not limited herein.
  • the original browser that sends the authentication request is determined according to the jump parameter carried in the authentication request, so that the authentication client sends the authentication result to the original browser, thereby effectively avoiding the existing technology.
  • the authentication client cannot accurately locate the original browser that sends the authentication request, which causes the authentication result to be lost, which improves the authentication efficiency.
  • FIG. 7 is a schematic structural diagram of an authentication device according to an embodiment of the present disclosure.
  • the authentication device includes: a determining unit 71, a transmitting unit 72, and a display unit 73, wherein:
  • a determining unit 71 determining a first time to send an authentication request to the authentication client, and a second time after performing the jump operation after the sending the authentication request, where the authentication request includes information to be authenticated;
  • the sending unit 72 when determining that the time difference between the first time and the second time is greater than a set threshold, sending an authentication result obtaining request to the authentication client, where the authentication result obtaining request is used to obtain the The authentication result of the information to be authenticated;
  • the display unit 73 displays the authentication result when receiving the authentication result sent by the authentication client.
  • the display unit 73 displays the installation prompt information of the authentication client when it is determined that the time difference between the first time and the second time is not greater than a set threshold.
  • the authentication device provided in the embodiment of the present disclosure may be implemented by using a software, or may be implemented by using a hardware, and is not specifically limited herein.
  • the authentication device provided by the embodiment of the present application may be a browser, and the browser determines whether the authentication jump process is successfully executed by determining the execution time of the different operations, and if the execution is successful, requests the authentication client to obtain the authentication result, so that the user The certification result can be obtained as soon as possible, and the execution efficiency of the certification is improved.
  • FIG. 8 is a schematic structural diagram of an authentication client according to an embodiment of the present disclosure.
  • the authentication client includes a memory 81, a signal receiver 82, a signal transmitter 83, and a processor 84, wherein:
  • the storage unit 81 stores a program code for performing an authentication operation and a mapping file, where the mapping file includes a mapping relationship between identifier information of different browsers and a jump parameter of the browser;
  • the signal receiver 82 receives an authentication request sent by the target browser, where the authentication request includes information to be authenticated and a jump parameter for implementing a jump between the target browser and the authentication client.
  • the processor 84 runs the program code stored in the memory and performs the following operations:
  • mapping file After authenticating the to-be-authenticated information received by the signal receiver to obtain an authentication result, searching, according to the jump parameter received by the signal receiver, the mapping file to find the matching with the jump parameter.
  • the mapping information of the target browser, the mapping file includes a mapping relationship between the identifier information of the different browsers and the jump parameter of the browser; and the indication signal transmitter according to the identification information of the target browser.
  • the target browser sends a page jump request, where the page jump request includes the authentication result;
  • the signal transmitter 83 sends a page jump request to the target browser according to the identification information of the target browser.
  • the authentication client described in the embodiment of the present application has the functions of the authentication device in the fourth embodiment, and details are not described herein again.
  • the processor described in the embodiment of the present application may be a central processing unit or other controllers, and is not specifically limited herein.
  • the authentication client After authenticating the authentication information, the authentication client can determine the original browser that sends the authentication request according to the jump parameter carried in the authentication request, so that the authentication client sends the authentication result to the original browser, effectively avoiding the existing In the technology, the authentication client cannot accurately locate the original browser that sends the authentication request, which causes the authentication result to be lost, which improves the authentication efficiency.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.
  • embodiments of the present application can be provided as a method, system, or computer program product. Accordingly, the present application may employ an entirely hardware embodiment, an entirely software embodiment, or an embodiment incorporating software and hardware aspects. form. Moreover, the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Databases & Information Systems (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Power Engineering (AREA)
  • Data Mining & Analysis (AREA)
  • Information Transfer Between Computers (AREA)
  • Storage Device Security (AREA)

Abstract

本申请公开了一种认证方法、设备以及认证客户端，包括：认证客户端接收通过目标浏览器发送的认证请求，所述认证请求中包含待认证信息和用于实现所述目标浏览器与所述认证客户端之间跳转的跳转参数；并在对所述待认证信息进行认证得到认证结果后，根据所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，所述映射文件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系；根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求，所述页面跳转请求中包含所述认证结果，有效避免现有技术中认证客户端无法准确定位发送认证请求的原始浏览器导致认证结果丢失的问题，提升了认证效率。

Description

一种认证方法、设备以及认证客户端
本申请要求2016年08月12日递交的申请号为201610663316.8、发明名称为“一种认证方法、设备以及认证客户端”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及互联网信息处理技术领域，尤其涉及一种认证方法、设备以及认证客户端。
背景技术
在实际应用中，存在这么一种现象：用户A为业务服务需求方，用户B为业务服务提供方，在用户B向用户A提供业务服务时，用户B需要对用户A所提供的身份信息进行认证。
那么目前所采用的认证方式一般包含以下内容：
第一步，用户A所使用的用户设备通过某种方式从用户B处获取认证页面的链接地址；
第二步，用户A启动所使用的用户设备中安装的任意一个浏览器，并在该浏览器中加载第一步中获取到的链接地址对应的认证页面；
第三步，用户A在该认证页面中输入待认证的身份信息，并向认证客户端发送认证请求，该认证请求中包含待认证的身份信息；
第四步，认证客户端在接收到认证请求时，对该认证请求中包含的待认证的身份信息进行认证；
第五步，认证客户端将认证结果推送给默认的浏览器。
经研究发现，第五步中所描述的默认浏览器与第二步中启动的浏览器属于不同的浏览器，此时，默认浏览器在接收到认证结果时，无法确定认证结果对应的身份信息，进而确定待认证的身份信息丢失，重新发起身份认证，这一过程使得认证流程耗时较长，影响用户对认证客户端的用户体验。
发明内容
有鉴于此，本申请实施例提供了一种认证方法、设备以及认证客户端，用于解决现 有技术中存在认证流程耗时较长的问题。
本申请实施例提供了一种认证方法，包括：
认证客户端接收通过目标浏览器发送的认证请求，所述认证请求中包含待认证信息和用于实现所述目标浏览器与所述认证客户端之间跳转的跳转参数；
所述认证客户端在对所述待认证信息进行认证得到认证结果后，根据所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，所述映射文件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系；
所述认证客户端根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求，所述页面跳转请求中包含所述认证结果。
本申请实施例还提供了一种认证方法，包括：
浏览器确定向认证客户端发送认证请求的第一时间，以及在所述认证请求发出之后执行跳转操作后的第二时间，所述认证请求中包含待认证信息；
所述浏览器在确定所述第一时间和所述第二时间之间的时间差大于设定阈值时，向所述认证客户端发送认证结果获取请求，所述认证结果获取请求用于获取所述待认证信息的认证结果；
所述浏览器在接收到所述认证客户端发送的所述认证结果时，显示所述认证结果。
本申请实施例还提供了一种认证设备，包括：
接收单元，接收通过目标浏览器发送的认证请求，所述认证请求中包含待认证信息和用于实现所述目标浏览器与所述认证设备之间跳转的跳转参数；
查找单元，在对所述待认证信息进行认证得到认证结果后，根据所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，所述映射文件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系；
发送单元，用于根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求，所述页面跳转请求中包含所述认证结果。
本申请实施例还提供了一种认证设备，包括：
确定单元，确定向认证客户端发送认证请求的第一时间，以及在所述认证请求发出之后执行跳转操作后的第二时间，所述认证请求中包含待认证信息；
发送单元，在确定所述第一时间和所述第二时间之间的时间差大于设定阈值时，向所述认证客户端发送认证结果获取请求，所述认证结果获取请求用于获取所述待认证信息的认证结果；
显示单元，在接收到所述认证客户端发送的所述认证结果时，显示所述认证结果。
本申请实施例还提供了一种认证客户端，所述认证客户端包括：存储器、信号接收器、信号发射器和处理器，其中：
存储器，存储执行认证操作的程序代码以及映射文件，所述映射文件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系；
信号接收器，接收通过目标浏览器发送的认证请求，所述认证请求中包含待认证信息和用于实现所述目标浏览器与所述认证客户端之间跳转的跳转参数；
处理器，运行所述存储器中存储的程序代码，执行以下操作：
在对信号接收器接收到的所述待认证信息进行认证得到认证结果后，根据所述信号接收器接收到的所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，所述映射文件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系；并指示信号发射器根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求，所述页面跳转请求中包含所述认证结果；
信号发射器器，根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求。
本申请实施例采用的上述至少一个技术方案能够达到以下有益效果：
认证客户端接收通过目标浏览器发送的认证请求，所述认证请求中包含待认证信息和用于实现所述目标浏览器与所述认证客户端之间跳转的跳转参数；并在对所述待认证信息进行认证得到认证结果后，根据所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，所述映射文件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系；根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求，所述页面跳转请求中包含所述认证结果。这样，认证客户端在对待认证信息进行认证之后，能够根据认证请求中携带的跳转参数，确定发送所述认证请求的原始浏览器，使得认证客户端将认证结果发送给原始浏览器，有效避免现有技术中认证客户端无法准确定位发送认证请求的原始浏览器导致认证结果丢失的问题，提升了认证效率。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1为本申请实施例提供的一种认证方法的流程示意图；
图2为本申请实施例提供的一种映射文件的确定方式的示意图；
图3为本申请实施例提供的一种认证方法的流程示意图；
图4为本申请实施例提供的一种认证方法的流程示意图；
图5为本申请实施例提供的一种认证方法的场景示意图；
图6为本申请实施例提供的一种认证设备的结构示意图；
图7为本申请实施例提供的一种认证设备的结构示意图；
图8为本申请实施例提供的一种认证客户端的结构示意图。
具体实施方式
目前，在iOS操作系统中，不同应用软件相对独立，对于同一个用户设备中，应用软件不能准确获取该用户设备上还同时安装了哪些其他的应用软件，那么按照现有技术，认证客户端在对信息进行认证之后，无法确定本地是否安装与发送认证请求所使用的浏览器相同的浏览器，因此，只能向认证客户端默认的浏览器发送认证结果，使得默认的浏览器在接收到认证结果时无法对认证结果进行识别，进而导致用户信息的丢失，此时不得不重新发起认证请求，导致认证流程时间延长。
为了实现本申请的目的，本申请实施例提供了一种认证方法、设备以及认证客户端，认证客户端接收通过目标浏览器发送的认证请求，所述认证请求中包含待认证信息和用于实现所述目标浏览器与所述认证客户端之间跳转的跳转参数；并在对所述待认证信息进行认证得到认证结果后，根据所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，所述映射文件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系；根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求，所述页面跳转请求中包含所述认证结果。这样，认证客户端在对待认证信息进行认证之后，能够根据认证请求中携带的跳转参数，确定发送所述认证请求的原始浏览器，使得认证客户端将认证结果发送给原始浏览器，有效避免现有技术中认证客户端无法准确定位发送认证请求的原始浏览器导致认证结果丢失的问题，提升了认证效率。
需要说明的是，本申请实施例所应用的场景可以包含通过浏览器发起认证请求，此时该认证请求跳转至一个认证应用中，由该认证应用对该认证请求中包含的认证信息进行认证，并将认证结果显示在原始浏览器中。
例如：用户A通过扫码方式获取一个认证页面的链接地址，并随机选择一个浏览器加载该链接地址对应的认证页面；用户A在加载完成的认证页面中输入需要认证的信息，并通过该浏览器将需要认证的信息发送给认证客户端；认证客户端可以安装在用户B所使用的用户设备中，那么认证客户端对接收到的需要认证的信息进行认证，并在认证通过时，成功调用与用户A选择的相同的浏览器，并将认证结果显示在该浏览器的页面中。
本申请实施例所提供的认证客户端可以支持iOS操作系统，也可以支持类iOS操作系统，这里不做具体限定。
需要说明的是，本申请实施例中所记载的浏览器的标识信息可以是从浏览器的安装包中读取到的，本申请实施例中浏览器的标识信息又可以称之为浏览器标识(或者source Application)。浏览器不同，在执行跳转操作时所调用的跳转参数也不同，这个的不同可以是指格式不同，也可以是其他不同，这里不做具体限定。所具备的共同特点是：跳转参数中包含浏览器的标识。
为使本申请的目的、技术方案和优点更加清楚，下面结合本申请具体实施例及相应的附图对本申请技术方案进行清楚、完整地描述。显然，所描述的实施例仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
以下结合附图，详细说明本申请各实施例提供的技术方案。
实施例1
图1为本申请实施例提供的一种认证方法的流程示意图。所述方法可以如下所示。
步骤101：认证客户端接收通过目标浏览器发送的认证请求，所述认证请求中包含待认证信息和用于实现所述目标浏览器与所述认证客户端之间跳转的跳转参数。
在步骤101中，假设一种应用场景，当用户A与用户B之间通过协商进行业务合作时，用户B需要对用户A提供的信息(这里包含身份信息)进行认证，此时，用户B向用户A提供一个认证页面的链接地址。在本申请实施例中，认证页面的链接地址可以是真实地址信息，也可以是二维码形式，还可以是其他形式，这里不做具体限定。
如果用户B向用户A提供的认证页面的链接地址为二维码，那么用户A通过扫码或者其他方式获取该认证页面的链接地址，并启动用户A所使用的用户设备中安装的任意一款浏览器，向服务器发送认证页面访问请求，该认证页面访问请求中包含链接地址；浏览器接收服务器发送的页面信息，并显示该页面信息。
用户A在显示的页面中输入待认证信息，并触发页面中的认证控件，视为发起认证 请求。由于该认证控件中包含认证客户端的地址，此时发起页面跳转请求，该页面跳转请求中包含跳转参数和待认证信息，跳转至认证客户端。这里的页面跳转请求可以视为向认证客户端发起认证请求。
这里的跳转参数可以是scheme参数，即在iOS操作系统中打开一个本地应用的统一资源标识符(Uniform Resource Identifier，或URI)，URI用于标识某一互联网资源名称的字符串，在本申请实施例中可以理解为浏览器的名称字符串。
这里需要说明的是，浏览器在执行跳转操作时，生成跳转参数，该跳转参数中包含的浏览器的标识信息(即浏览器的名称字符串)，这样可以根据跳转参数确定该跳转操作是由哪个浏览器执行的。
可选地，在触发页面中的认证控件时，所述方法还包括：
对用户输入的待认证信息进行加密处理，得到加密后的待认证信息。
例如：若用户A输入的用户身份信息，那么根据用户身份信息生成一个token，token即可视为加密后的待认证信息。
在向认证客户端发送认证请求时，可以将加密后的待认证信息携带在认证请求中发送给认证客户端。
具体地，认证客户端接收到通过浏览器发送的认证请求。
步骤102：所述认证客户端对所述待认证信息进行认证得到认证结果。
在步骤102中，认证客户端对接收到的待认证信息进行解析，若确定所述待认证信息为加密的身份认证信息，那么对所述认证请求中包含的加密的身份认证信息进行解密，并对解密后的身份认证信息进行认证，得到认证结果。
若确定所述待认证信息为非加密的身份认证信息，那么直接对待认证信息进行认证，得到认证结果。
可选地，在得到认证结果时，所述方法还包括：
所述认证客户端还可以进一步判断所述认证请求是由浏览器发送的还是由应用软件发送的，若判断结果是由浏览器发送的，那么继续执行步骤103；
若判断结果是由应用软件发送的，那么将认证结果发送给该应用软件。
也就是说步骤101中认证客户端所接收到的认证请求可以是由浏览器发送的，也可以是由应用软件发送的，这里不做具体限定。
这里判断所述认证请求是由浏览器发送的还是由应用软件发送的的方式包括但不限于：
解析认证结果，若认证结果中包含页面地址，且页面地址的头部字段为http/https，那么确定该认证请求是由浏览器发送的，否则，确定该认证请求是由应用软件发送的。
步骤103：所述认证客户端根据所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，所述映射文件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系。
在步骤103中，所述认证客户端在接收到认证请求时，获取source Application参数。
具体地，用户设备在通过浏览器向认证客户端发送认证请求时，用户设备的操作系统调用浏览器的运行信息，获取source Application参数(即【-application：open URL：source Application：annotation】)，并根据获取的source Application参数确定跳转参数，并将跳转参数携带在认证请求中发送给认证客户端，使得认证客户端能够从跳转参数中确定执行跳转操作的原始浏览器的标识信息。
具体地，所述认证客户端根据存储的浏览器的标识信息与跳转参数之间的映射关系，从映射文件中查找与接收到的所述跳转参数对应的浏览器的标识信息，根据查找到的所述浏览器的标识信息确定执行跳转操作的原始浏览器。
可选地，所述方法还包括：
所述认证客户端在从映射文件中查找不到所述跳转参数匹配的所述目标浏览器的标识信息时，向服务器发送包含所述跳转参数的映射文件更新请求，所述映射文件更新请求用于所述服务器根据所述跳转参数确定与所述跳转参数匹配的浏览器的标识信息并更新所述映射文件。
在实际应用中，映射文件可以是由服务器生成并发送给认证客户端的，也可以是认证客户端生成的，这里不做限定。
可选地，所述认证客户端在从映射文件中查找不到所述跳转参数匹配的所述目标浏览器的标识信息时，所述认证客户端存储获取source Application参数，并在下一次冷启动时，将存储的source Application参数发送给服务器。
服务器在接收到source Application参数时，查找source Application参数对应的浏览器，并下载该浏览器的安装包，对该浏览器的安装包进行解压，得到浏览器的ipa包，从ipa包中获取info.plist文件。从info.plist文件中查找URL typeset，并确定URL typeset对应的URL Schems，从URL Schems中查找到浏览器对应的scheme；建立查找到的浏览器的标识信息与scheme之间的映射关系，并利用建立的映射关系更新映射文件。
服务器在更新映射文件之后，当检测到认证客户端重新启动时，将更新后的映射文 件发送给认证客户端。
下面详细说明映射文件的确定方式。
图2为本申请实施例提供的一种映射文件的确定方式的示意图。
S201：获取不同浏览器的安装包。
S202：针对每一个浏览器的安装包，执行以下操作：
S2021：选择其中一个浏览器的安装包，从所述安装包中读取info.plist文件，所述info.plist文件中包含所述浏览器的至少一个键值对。
具体地，对选择的浏览器的安装包进行解压，得到浏览器的ipa包，从ipa包中获取info.plist文件。在这个info.plist文件中包含了针对浏览器的多个键值对。
这些键值对中包含浏览器的标识信息与所述浏览器的跳转参数的键值对。
S2022：确定浏览器的标识信息与所述浏览器的跳转参数的键值对。
具体地，从info.plist文件中查找URL typeset，并确定URL typeset对应的URL Schems，从URL Schems中查找到浏览器对应的scheme，这个scheme可以称之为跳转参数。
当查找到的scheme的个数大于1时，选择scheme对应的名称与浏览器的名称最接近的。
此外，从info.plist文件中查找Bundle identifier(浏览器的标识信息，即source application)，此时将Bundle identifier和选择的scheme的组合称之为确定的浏览器的标识信息与所述浏览器的跳转参数的键值对。
S2023：确定浏览器的标识信息与所述浏览器的跳转参数之间的映射关系，并将所述映射关系存储至映射文件中。
步骤104：所述认证客户端根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求，所述页面跳转请求中包含所述认证结果。
在步骤104中，所述认证客户端根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求，使得所述目标浏览器在接收到该页面跳转请求时显示页面跳转请求中包含的认证结果。
通过本申请实施例所提供的技术方案，认证客户端接收通过目标浏览器发送的认证请求，所述认证请求中包含待认证信息和用于实现所述目标浏览器与所述认证客户端之间跳转的跳转参数；并在对所述待认证信息进行认证得到认证结果后，根据所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，所述映射文 件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系；根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求，所述页面跳转请求中包含所述认证结果。这样，认证客户端在对待认证信息进行认证之后，能够根据认证请求中携带的跳转参数，确定发送所述认证请求的原始浏览器，使得认证客户端将认证结果发送给原始浏览器，有效避免现有技术中认证客户端无法准确定位发送认证请求的原始浏览器导致认证结果丢失的问题，提升了认证效率。
实施例2
图3为本申请实施例提供的一种认证方法的流程示意图。所述方法可以如下所示。
步骤301：浏览器确定向认证客户端发送认证请求的第一时间，以及在所述认证请求发出之后执行跳转操作后的第二时间，所述认证请求中包含待认证信息。
在步骤301中，当用户A与用户B之间通过协商进行业务合作时，用户B需要对用户A提供的信息(这里包含身份信息)进行认证，此时，用户B向用户A提供一个认证页面的链接地址。在本申请实施例中，认证页面的链接地址可以是真实地址信息，也可以是二维码形式，还可以是其他形式，这里不做具体限定。
如果用户B向用户A提供的认证页面的链接地址为二维码，那么用户A通过扫码或者其他方式获取该认证页面的链接地址，并启动用户A所使用的用户设备中安装的任意一款浏览器，向服务器发送认证页面访问请求，该认证页面访问请求中包含链接地址；浏览器接收服务器发送的页面信息，并显示该页面信息。
用户A在显示的页面中输入待认证信息，并触发页面中的认证控件，视为发起认证请求，此时浏览器记录触发页面的认证控件的时间戳，记为第一时间。
在触发页面中的认证控件之后，浏览器执行跳转操作，此时在跳转操作执行完成时，记录跳转操作完成时的时间戳，记为第二时间。
步骤302：所述浏览器根据所述第一时间和所述第二时间，判断所述第一时间和所述第二时间之间的时间差是否大于设定阈值，若大于，则执行步骤303；否则，执行步骤305。
在步骤302中，计算所述第一时间与所述第二时间之间的时间差，进一步判断时间差与设定阈值之间的大小关系。
需要说明的是，设定阈值可以根据实际需要确定，也可以根据试验数据确定，这里不做具体限定。例如：设定阈值为2s。
具体地，在iOS平台中，页面一旦被处于后台操作，则代码逻辑将被阻塞。当触发 页面的认证控件后，跳转至认证客户端，若所述第一时间和所述第二时间之间的时间差大于设定阈值，则确定跳转成功，若所述第一时间和所述第二时间之间的时间差不大于设定阈值，则确定跳转失败。
步骤303：所述浏览器向所述认证客户端发送认证结果获取请求，所述认证结果获取请求用于获取所述待认证信息的认证结果。
步骤304：所述浏览器在接收到所述认证客户端发送的所述认证结果时，显示所述认证结果。
步骤305：所述浏览器显示认证客户端的安装提示信息。
实施例3
图4为本申请实施例提供的一种认证方法的流程示意图。所述方法可以如下所示。
步骤401：目标浏览器向认证客户端发送认证请求。
步骤402：目标浏览器确定向认证客户端发送认证请求的第一时间。
步骤403：目标浏览器在所述认证请求发出之后执行跳转操作后的第二时间。
步骤404：所述浏览器根据所述第一时间和所述第二时间，判断所述第一时间和所述第二时间之间的时间差是否大于设定阈值，若大于，则执行步骤409；否则，执行步骤410。
步骤405：认证客户端接收通过目标浏览器发送的认证请求，所述认证请求中包含待认证信息和用于实现所述目标浏览器与所述认证客户端之间跳转的跳转参数。
步骤406：所述认证客户端对所述待认证信息进行认证得到认证结果。
可选地，在步骤406中，所述浏览器向所述认证客户端发送认证结果获取请求，所述认证结果获取请求用于获取所述待认证信息的认证结果，跳转执行步骤409。
步骤407：所述认证客户端根据所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，所述映射文件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系。
步骤408：所述认证客户端根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求，所述页面跳转请求中包含所述认证结果。
需要说明的是，本申请实施例中步骤402～步骤404与步骤405～步骤408的执行可以同时执行也可以按照顺序方式执行。
步骤409：所述浏览器在接收到所述认证客户端发送的所述认证结果时，显示所述认证结果。
步骤410：所述浏览器显示认证客户端的安装提示信息。
图5为本申请实施例提供的一种认证方法的场景示意图。
实施例4
图6为本申请实施例提供的一种认证设备的结构示意图。所述认证设备包括：接收单元61、查找单元62和发送单元63，其中：
接收单元61，接收通过目标浏览器发送的认证请求，所述认证请求中包含待认证信息和用于实现所述目标浏览器与所述认证设备之间跳转的跳转参数；
查找单元62，在对所述待认证信息进行认证得到认证结果后，根据所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，所述映射文件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系；
发送单元63，用于根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求，所述页面跳转请求中包含所述认证结果。
在本申请的另一个实施例中，所述认证设备还包括：更新单元64，其中：
所述更新单元64，在从映射文件中查找不到所述跳转参数匹配的所述目标浏览器的标识信息时，向服务器发送包含所述跳转参数的映射文件更新请求，所述映射文件更新请求用于所述服务器根据所述跳转参数确定与所述跳转参数匹配的浏览器的标识信息并更新所述映射文件。
在本申请的另一个实施例中，所述查找单元62根据所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，包括：
根据映射文件中存储的浏览器的标识信息与跳转参数之间的映射关系，从所述映射文件中查找与接收到的所述认证请求中包含的所述跳转参数之间存在映射关系的所述目标浏览器的标识信息。
在本申请的另一个实施例中，所述认证设备还包括：映射文件生成单元65，其中：
所述映射文件生成单元65，通过以下方式得到所述映射文件：
针对不同的浏览器，分别执行以下操作：
获取浏览器的安装包，并从所述安装包中读取info.plist文件，所述info.plist文件中包含所述浏览器的至少一个键值对；
从所述info.plist文件中查找包含所述浏览器的标识信息与所述浏览器的跳转参数的键值对；
确定浏览器的标识信息与所述浏览器的跳转参数之间的映射关系，并将所述映射关 系存储至映射文件中。
在本申请的另一个实施例中，所述待认证信息为加密的身份认证信息；
所述认证设备还包括：认证单元66，其中：
所述认证单元66，对所述待认证信息进行认证得到认证结果，包括：
对所述认证请求中包含的加密的身份认证信息进行解密，并对解密后的身份认证信息进行认证，得到认证结果。
需要说明的是，本申请实施例所记载的认证设备可以通过软件方式实现，也可以通过硬件方式实现，这里不做限定。认证设备在对待认证信息进行认证之后，能够根据认证请求中携带的跳转参数，确定发送所述认证请求的原始浏览器，使得认证客户端将认证结果发送给原始浏览器，有效避免现有技术中认证客户端无法准确定位发送认证请求的原始浏览器导致认证结果丢失的问题，提升了认证效率。
实施例5
图7为本申请实施例提供的一种认证设备的结构示意图。所述认证设备包括：确定单元71、发送单元72和显示单元73，其中：
确定单元71，确定向认证客户端发送认证请求的第一时间，以及在所述认证请求发出之后执行跳转操作后的第二时间，所述认证请求中包含待认证信息；
发送单元72，在确定所述第一时间和所述第二时间之间的时间差大于设定阈值时，向所述认证客户端发送认证结果获取请求，所述认证结果获取请求用于获取所述待认证信息的认证结果；
显示单元73，在接收到所述认证客户端发送的所述认证结果时，显示所述认证结果。
在本申请的另一个实施例中，所述显示单元73，在确定所述第一时间和所述第二时间之间的时间差不大于设定阈值时，显示认证客户端的安装提示信息。
需要说明的是，本申请实施例中提供的认证设备可以通过软件方式实现，也可以通过硬件方式实现，这里不做具体限定。本申请实施例提供的认证设备可以是浏览器，浏览器通过确定不同操作的执行时间，推测认证跳转流程是否执行成功，并在执行成功的情况下，向认证客户端请求认证结果，使得用户能够尽快获取认证结果，提升认证的执行效率。
实施例6
图8为本申请实施例提供的一种认证客户端的结构示意图。所述认证客户端包括：存储器81、信号接收器82、信号发射器83和处理器84，其中：
存储器81，存储执行认证操作的程序代码以及映射文件，所述映射文件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系；
信号接收器82，接收通过目标浏览器发送的认证请求，所述认证请求中包含待认证信息和用于实现所述目标浏览器与所述认证客户端之间跳转的跳转参数；
处理器84，运行所述存储器中存储的程序代码，执行以下操作：
在对信号接收器接收到的所述待认证信息进行认证得到认证结果后，根据所述信号接收器接收到的所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，所述映射文件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系；并指示信号发射器根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求，所述页面跳转请求中包含所述认证结果；
信号发射器器83，根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求。
需要说明的是，本申请实施例中所记载的认证客户端具备实施例4中认证设备所具备的功能，这里不再做详细赘述。本申请实施例中所记载的处理器可以是中央处理器，也可以是其他控制器，这里不做具体限定。
认证客户端在对待认证信息进行认证之后，能够根据认证请求中携带的跳转参数，确定发送所述认证请求的原始浏览器，使得认证客户端将认证结果发送给原始浏览器，有效避免现有技术中认证客户端无法准确定位发送认证请求的原始浏览器导致认证结果丢失的问题，提升了认证效率。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指 定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本领域技术人员应明白，本申请的实施例可提供为方法、系统或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例 的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
以上所述仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利要求范围之内。

Claims (15)

  1. 一种认证方法，其特征在于，包括：
    认证客户端接收通过目标浏览器发送的认证请求，所述认证请求中包含待认证信息和用于实现所述目标浏览器与所述认证客户端之间跳转的跳转参数；
    所述认证客户端在对所述待认证信息进行认证得到认证结果后，根据所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，所述映射文件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系；
    所述认证客户端根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求，所述页面跳转请求中包含所述认证结果。
  2. 如权利要求1所述的认证方法，其特征在于，所述方法还包括：
    所述认证客户端在从映射文件中查找不到所述跳转参数匹配的所述目标浏览器的标识信息时，向服务器发送包含所述跳转参数的映射文件更新请求，所述映射文件更新请求用于所述服务器根据所述跳转参数确定与所述跳转参数匹配的浏览器的标识信息并更新所述映射文件。
  3. 如权利要求1所述的认证方法，其特征在于，所述认证客户端根据所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，包括：
    所述认证客户端根据映射文件中存储的浏览器的标识信息与跳转参数之间的映射关系，从所述映射文件中查找与接收到的所述认证请求中包含的所述跳转参数之间存在映射关系的所述目标浏览器的标识信息。
  4. 如权利要求1至3任一项所述的认证方法，其特征在于，通过以下方式得到所述映射文件：
    针对不同的浏览器，分别执行以下操作：
    获取浏览器的安装包，并从所述安装包中读取info.plist文件，所述info.plist文件中包含所述浏览器的至少一个键值对；
    从所述info.plist文件中查找包含所述浏览器的标识信息与所述浏览器的跳转参数的键值对；
    确定浏览器的标识信息与所述浏览器的跳转参数之间的映射关系，并将所述映射关系存储至映射文件中。
  5. 如权利要求1所述的认证方法，其特征在于，所述待认证信息为加密的身份认证信息；
    所述认证客户端对所述待认证信息进行认证得到认证结果，包括：
    所述认证客户端对所述认证请求中包含的加密的身份认证信息进行解密，并对解密后的身份认证信息进行认证，得到认证结果。
  6. 一种认证方法，其特征在于，包括：
    浏览器确定向认证客户端发送认证请求的第一时间，以及在所述认证请求发出之后执行跳转操作后的第二时间，所述认证请求中包含待认证信息；
    所述浏览器在确定所述第一时间和所述第二时间之间的时间差大于设定阈值时，向所述认证客户端发送认证结果获取请求，所述认证结果获取请求用于获取所述待认证信息的认证结果；
    所述浏览器在接收到所述认证客户端发送的所述认证结果时，显示所述认证结果。
  7. 如权利要求6所述的认证方法，其特征在于，所述方法还包括：
    所述浏览器在确定所述第一时间和所述第二时间之间的时间差不大于设定阈值时，显示安装认证客户端的提示信息。
  8. 一种认证设备，其特征在于，包括：
    接收单元，接收通过目标浏览器发送的认证请求，所述认证请求中包含待认证信息和用于实现所述目标浏览器与所述认证设备之间跳转的跳转参数；
    查找单元，在对所述待认证信息进行认证得到认证结果后，根据所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，所述映射文件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系；
    发送单元，用于根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求，所述页面跳转请求中包含所述认证结果。
  9. 如权利要求8所述的认证设备，其特征在于，所述认证设备还包括：更新单元，其中：
    所述更新单元，在从映射文件中查找不到所述跳转参数匹配的所述目标浏览器的标识信息时，向服务器发送包含所述跳转参数的映射文件更新请求，所述映射文件更新请求用于所述服务器根据所述跳转参数确定与所述跳转参数匹配的浏览器的标识信息并更新所述映射文件。
  10. 如权利要求8所述的认证设备，其特征在于，所述查找单元根据所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，包括：
    根据映射文件中存储的浏览器的标识信息与跳转参数之间的映射关系，从所述映射 文件中查找与接收到的所述认证请求中包含的所述跳转参数之间存在映射关系的所述目标浏览器的标识信息。
  11. 如权利要求8至10任一项所述的认证设备，其特征在于，所述认证设备还包括：映射文件生成单元，其中：
    所述映射文件生成单元，通过以下方式得到所述映射文件：
    针对不同的浏览器，分别执行以下操作：
    获取浏览器的安装包，并从所述安装包中读取info.plist文件，所述info.plist文件中包含所述浏览器的至少一个键值对；
    从所述info.plist文件中查找包含所述浏览器的标识信息与所述浏览器的跳转参数的键值对；
    确定浏览器的标识信息与所述浏览器的跳转参数之间的映射关系，并将所述映射关系存储至映射文件中。
  12. 如权利要求8所述的认证设备，其特征在于，所述待认证信息为加密的身份认证信息；
    所述认证设备还包括：认证单元，其中：
    所述认证单元，对所述待认证信息进行认证得到认证结果，包括：
    对所述认证请求中包含的加密的身份认证信息进行解密，并对解密后的身份认证信息进行认证，得到认证结果。
  13. 一种认证设备，其特征在于，包括：
    确定单元，确定向认证客户端发送认证请求的第一时间，以及在所述认证请求发出之后执行跳转操作后的第二时间，所述认证请求中包含待认证信息；
    发送单元，在确定所述第一时间和所述第二时间之间的时间差大于设定阈值时，向所述认证客户端发送认证结果获取请求，所述认证结果获取请求用于获取所述待认证信息的认证结果；
    显示单元，在接收到所述认证客户端发送的所述认证结果时，显示所述认证结果。
  14. 如权利要求13所述的认证设备，其特征在于，
    所述显示单元，在确定所述第一时间和所述第二时间之间的时间差不大于设定阈值时，显示认证客户端的安装提示信息。
  15. 一种认证客户端，其特征在于，所述认证客户端包括：存储器、信号接收器、信号发射器和处理器，其中：
    存储器，存储执行认证操作的程序代码以及映射文件，所述映射文件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系；
    信号接收器，接收通过目标浏览器发送的认证请求，所述认证请求中包含待认证信息和用于实现所述目标浏览器与所述认证客户端之间跳转的跳转参数；
    处理器，运行所述存储器中存储的程序代码，执行以下操作：
    在对信号接收器接收到的所述待认证信息进行认证得到认证结果后，根据所述信号接收器接收到的所述跳转参数，从映射文件中查找与所述跳转参数匹配的所述目标浏览器的标识信息，所述映射文件中包含不同浏览器的标识信息与所述浏览器的跳转参数之间的映射关系；并指示信号发射器根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求，所述页面跳转请求中包含所述认证结果；
    信号发射器器，根据所述目标浏览器的标识信息，向所述目标浏览器发送页面跳转请求。
PCT/CN2017/095110 2016-08-12 2017-07-31 一种认证方法、设备以及认证客户端 Ceased WO2018028448A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
JP2019507769A JP6708784B2 (ja) 2016-08-12 2017-07-31 認証方法、装置及び認証クライアント
KR1020197007139A KR102175117B1 (ko) 2016-08-12 2017-07-31 인증 방법, 디바이스 및 인증 클라이언트
EP17838578.7A EP3499836B1 (en) 2016-08-12 2017-07-31 Authentication method, device and authentication client
SG11201901102SA SG11201901102SA (en) 2016-08-12 2017-07-31 Authentication method, device and authentication client
KR1020207031517A KR102289994B1 (ko) 2016-08-12 2017-07-31 인증 방법, 디바이스 및 인증 클라이언트
US16/272,852 US10686786B2 (en) 2016-08-12 2019-02-11 Authentication method, device and authentication client
PH12019500293A PH12019500293A1 (en) 2016-08-12 2019-02-12 Authentication method, device and authentication client
US16/867,527 US10798095B2 (en) 2016-08-12 2020-05-05 Authentication method, device and authentication client

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610663316.8 2016-08-12
CN201610663316.8A CN106899566B (zh) 2016-08-12 2016-08-12 一种认证方法、设备以及认证客户端

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/272,852 Continuation US10686786B2 (en) 2016-08-12 2019-02-11 Authentication method, device and authentication client

Publications (1)

Publication Number Publication Date
WO2018028448A1 true WO2018028448A1 (zh) 2018-02-15

Family

ID=59191666

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/095110 Ceased WO2018028448A1 (zh) 2016-08-12 2017-07-31 一种认证方法、设备以及认证客户端

Country Status (10)

Country Link
US (2) US10686786B2 (zh)
EP (1) EP3499836B1 (zh)
JP (1) JP6708784B2 (zh)
KR (2) KR102289994B1 (zh)
CN (2) CN111526152B (zh)
MY (1) MY181306A (zh)
PH (1) PH12019500293A1 (zh)
SG (1) SG11201901102SA (zh)
TW (1) TWI665575B (zh)
WO (1) WO2018028448A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111767030A (zh) * 2020-07-01 2020-10-13 中国银行股份有限公司 一种数据采集的方法及装置
CN112199713A (zh) * 2020-12-03 2021-01-08 成都中科大旗软件股份有限公司 一种ios系统软件运行算法的混淆加密方法
CN112579313A (zh) * 2019-09-30 2021-03-30 北京国双科技有限公司 对接系统的方法、装置、存储介质及电子设备
CN112612988A (zh) * 2020-12-28 2021-04-06 深圳壹账通智能科技有限公司 页面处理方法、装置、计算机设备及存储介质
CN113449213A (zh) * 2020-03-27 2021-09-28 北京沃东天骏信息技术有限公司 页面跳转的方法和装置

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111526152B (zh) * 2016-08-12 2022-02-11 创新先进技术有限公司 一种认证方法、设备以及认证客户端
WO2019060281A1 (en) 2017-09-19 2019-03-28 Abiomed, Inc. SYSTEMS AND METHODS FOR SINGLE USE TEMPORARY PASSWORD MANAGEMENT FOR A MEDICAL DEVICE
CN110704102A (zh) * 2019-09-12 2020-01-17 北京字节跳动网络技术有限公司 页面跳转协议接口文档生成方法、系统、介质和电子设备
CN110941484B (zh) * 2019-11-22 2022-12-09 马蜂窝(贵州)旅游集团有限公司 应用程序调起方法和设备
CN111428164A (zh) * 2020-03-27 2020-07-17 五八有限公司 页面显示方法、装置、移动终端、电子设备及存储介质
CN111881400B (zh) * 2020-07-31 2024-02-23 中国农业银行股份有限公司 网页跳转路径确定方法及装置
CN112073443B (zh) * 2020-11-12 2021-03-16 飞天诚信科技股份有限公司 一种基于浏览器访问认证设备的方法及系统
CN114598490B (zh) * 2021-04-09 2024-03-29 亚信科技（南京）有限公司 基于api网关重定向页面的方法、装置、设备及存储介质
CN114189718A (zh) * 2021-11-23 2022-03-15 贵阳朗玛视讯科技有限公司 一种iptv启动优化的方法及装置
CN114238802A (zh) * 2021-12-17 2022-03-25 深圳壹账通智能科技有限公司 共享Cookie的方法、装置、设备及存储介质
CN115150662B (zh) * 2022-06-20 2024-05-14 北京奇艺世纪科技有限公司 数据处理方法、系统、装置、可读存储介质及电子设备
CN115567583B (zh) * 2022-09-30 2025-07-01 杭州海康威视数字技术股份有限公司 一种设备通信方法、装置及电子设备
CN115713336A (zh) * 2022-11-08 2023-02-24 中国建设银行股份有限公司 一种业务处理的方法、装置、电子设备和存储介质
CN116627544B (zh) * 2023-07-24 2023-10-31 中化现代农业有限公司 页面启动方法、装置、电子设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102946314A (zh) * 2012-11-08 2013-02-27 成都卫士通信息产业股份有限公司 一种基于浏览器插件的客户端用户身份认证方法
US20150007299A1 (en) * 2012-09-19 2015-01-01 Secureauth Corporation Mobile multifactor single-sign-on authentication
CN104735066A (zh) * 2015-03-18 2015-06-24 百度在线网络技术（北京）有限公司 一种面向网页应用的单点登录方法、装置和系统
CN105262748A (zh) * 2015-10-19 2016-01-20 北京东方棱镜科技有限公司 广域网中对用户终端进行身份认证的方法和系统
CN106899566A (zh) * 2016-08-12 2017-06-27 阿里巴巴集团控股有限公司 一种认证方法、设备以及认证客户端

Family Cites Families (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2875827B2 (ja) 1989-11-21 1999-03-31 株式会社日立製作所 制御棒駆動水圧系
US5586260A (en) * 1993-02-12 1996-12-17 Digital Equipment Corporation Method and apparatus for authenticating a client to a server in computer systems which support different security mechanisms
US6892307B1 (en) 1999-08-05 2005-05-10 Sun Microsystems, Inc. Single sign-on framework with trust-level mapping to authentication requirements
US7143437B2 (en) * 2001-01-12 2006-11-28 Siemens Medical Solutions Health Services Corporation System and user interface for managing user access to network compatible applications
JP4393733B2 (ja) * 2001-11-27 2010-01-06 大日本印刷株式会社 携帯可能情報記録媒体
US7191467B1 (en) 2002-03-15 2007-03-13 Microsoft Corporation Method and system of integrating third party authentication into internet browser code
JP2003316743A (ja) * 2002-04-24 2003-11-07 Nippon Telegr & Teleph Corp <Ntt> ネットワークアクセス方法およびクライアント
US20040003287A1 (en) 2002-06-28 2004-01-01 Zissimopoulos Vasileios Bill Method for authenticating kerberos users from common web browsers
ATE391385T1 (de) * 2003-07-11 2008-04-15 Ibm Verfahren und system zur benutzerauthentifizierung in einer benutzer- anbieterumgebung
CN100442895C (zh) 2006-06-08 2008-12-10 中国移动通信集团公司 内嵌于移动终端的地图浏览器及手机地图移动终端系统
US9053063B2 (en) 2007-02-21 2015-06-09 At&T Intellectual Property I, Lp Method and apparatus for authenticating a communication device
CN101567893A (zh) 2009-05-26 2009-10-28 中兴通讯股份有限公司 一种实现在web应用中文件上传的方法及系统
CN101620635A (zh) * 2009-08-07 2010-01-06 中兴通讯股份有限公司 页面数据获取方法及服务器、页面更新方法及服务器
US20110191676A1 (en) 2010-01-29 2011-08-04 Microsoft Corporation Cross-Browser Interactivity Recording, Playback, and Editing
US8776169B2 (en) 2010-03-30 2014-07-08 Authentic8, Inc. Disposable browsers and authentication techniques for a secure online user environment
JP2012181601A (ja) * 2011-02-08 2012-09-20 Canon Inc 情報処理システム、情報処理装置、及び情報処理装置の制御方法
US20120323717A1 (en) * 2011-06-16 2012-12-20 OneID, Inc. Method and system for determining authentication levels in transactions
CN102333081B (zh) * 2011-08-03 2014-01-22 北京星网锐捷网络技术有限公司 认证方法、设备及系统
US8844013B2 (en) 2011-10-04 2014-09-23 Salesforce.Com, Inc. Providing third party authentication in an on-demand service environment
KR101367120B1 (ko) * 2012-03-09 2014-02-27 네이버비즈니스플랫폼 주식회사 웹브라우저와 프록시를 이용하여 웹페이지 로딩 시간을 측정하는 시스템 및 방법
US8763101B2 (en) 2012-05-22 2014-06-24 Verizon Patent And Licensing Inc. Multi-factor authentication using a unique identification header (UIDH)
JP5482841B2 (ja) * 2012-07-27 2014-05-07 株式会社セガ サーバ装置、サーバプログラム、および、端末プログラム
US9338007B1 (en) * 2012-10-26 2016-05-10 Google Inc. Secure delegated authentication for applications
JP6311214B2 (ja) 2013-01-30 2018-04-18 富士通株式会社 アプリケーション認証プログラム、認証サーバ、端末およびアプリケーション認証方法
JP6343900B2 (ja) * 2013-10-10 2018-06-20 富士通株式会社 通信端末、通信処理方法および通信処理プログラム
US10855760B2 (en) * 2013-11-07 2020-12-01 Cole Asher Ratias Systems and methods for synchronizing content and information on multiple computing devices
CN103702399A (zh) * 2013-12-25 2014-04-02 福建星网锐捷通讯股份有限公司 一种通过智能手机管理无线路由器的方法
WO2015130700A1 (en) * 2014-02-26 2015-09-03 Secureauth Corporation Security object creation, validation, and assertion for single sign on authentication
US10275421B1 (en) * 2014-04-30 2019-04-30 Facebook, Inc. Transmitting a state of a mobile application to an additional mobile application executing on a client device
SE538485C2 (en) * 2014-08-08 2016-08-02 Identitrade Ab Method and system for authenticating a user
CN104239775B (zh) * 2014-09-28 2016-11-30 北京奇虎科技有限公司 手机端与pc端通过短信息建立无线连接的方法和装置
US10182324B2 (en) * 2014-11-13 2019-01-15 Branch Metrics, Inc. Contextual deep linking of applications
US9781542B2 (en) * 2014-11-21 2017-10-03 Facebook, Inc. Techniques for predictive power management of a mobile device
CN104636455B (zh) * 2015-01-30 2018-03-02 腾讯科技（深圳）有限公司 应用程序映射信息的获取方法及装置
CN104821940A (zh) * 2015-04-16 2015-08-05 京信通信技术(广州)有限公司 一种发送portal重定向地址的方法及设备
US10425492B2 (en) * 2015-07-07 2019-09-24 Bitly, Inc. Systems and methods for web to mobile app correlation
US10503796B2 (en) * 2015-10-26 2019-12-10 Facebook, Inc. Searching for application content with social plug-ins
KR20170077425A (ko) * 2015-12-28 2017-07-06 삼성전자주식회사 전자 장치 및 전자 장치의 핸드오프를 이용한 결제 수행 방법
GB201603807D0 (en) * 2016-03-04 2016-04-20 Microsoft Technology Licensing Llc Communication between applications
US10257342B2 (en) * 2016-03-31 2019-04-09 Microsoft Technology Licensing, Llc Validating stateful dynamic links in mobile applications
US20170289338A1 (en) * 2016-03-31 2017-10-05 Microsoft Technology Licensing, Llc Enabling stateful dynamic links in mobile applications
US10135946B2 (en) * 2016-04-11 2018-11-20 Verizon Patent And Licensing Inc. Sending messages to mobile devices
US10574692B2 (en) * 2016-05-30 2020-02-25 Christopher Nathan Tyrwhitt Drake Mutual authentication security system with detection and mitigation of active man-in-the-middle browser attacks, phishing, and malware and other security improvements
US10542069B2 (en) * 2016-07-13 2020-01-21 Mobisave Llc System and method for providing a customized resource

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150007299A1 (en) * 2012-09-19 2015-01-01 Secureauth Corporation Mobile multifactor single-sign-on authentication
CN102946314A (zh) * 2012-11-08 2013-02-27 成都卫士通信息产业股份有限公司 一种基于浏览器插件的客户端用户身份认证方法
CN104735066A (zh) * 2015-03-18 2015-06-24 百度在线网络技术（北京）有限公司 一种面向网页应用的单点登录方法、装置和系统
CN105262748A (zh) * 2015-10-19 2016-01-20 北京东方棱镜科技有限公司 广域网中对用户终端进行身份认证的方法和系统
CN106899566A (zh) * 2016-08-12 2017-06-27 阿里巴巴集团控股有限公司 一种认证方法、设备以及认证客户端

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3499836A4

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112579313A (zh) * 2019-09-30 2021-03-30 北京国双科技有限公司 对接系统的方法、装置、存储介质及电子设备
CN113449213A (zh) * 2020-03-27 2021-09-28 北京沃东天骏信息技术有限公司 页面跳转的方法和装置
CN111767030A (zh) * 2020-07-01 2020-10-13 中国银行股份有限公司 一种数据采集的方法及装置
CN112199713A (zh) * 2020-12-03 2021-01-08 成都中科大旗软件股份有限公司 一种ios系统软件运行算法的混淆加密方法
CN112199713B (zh) * 2020-12-03 2021-03-16 成都中科大旗软件股份有限公司 一种ios系统软件运行算法的混淆加密方法
CN112612988A (zh) * 2020-12-28 2021-04-06 深圳壹账通智能科技有限公司 页面处理方法、装置、计算机设备及存储介质

Also Published As

Publication number Publication date
PH12019500293A1 (en) 2019-10-28
CN111526152B (zh) 2022-02-11
JP2019525350A (ja) 2019-09-05
JP6708784B2 (ja) 2020-06-10
MY181306A (en) 2020-12-21
TWI665575B (zh) 2019-07-11
US20190173881A1 (en) 2019-06-06
KR20190032603A (ko) 2019-03-27
CN106899566B (zh) 2020-03-24
KR102175117B1 (ko) 2020-11-06
CN111526152A (zh) 2020-08-11
SG11201901102SA (en) 2019-03-28
KR20200127058A (ko) 2020-11-09
US10798095B2 (en) 2020-10-06
EP3499836B1 (en) 2022-04-27
EP3499836A1 (en) 2019-06-19
EP3499836A4 (en) 2020-07-22
US20200267149A1 (en) 2020-08-20
CN106899566A (zh) 2017-06-27
US10686786B2 (en) 2020-06-16
TW201805847A (zh) 2018-02-16
KR102289994B1 (ko) 2021-08-17

Similar Documents

Publication Publication Date Title
WO2018028448A1 (zh) 一种认证方法、设备以及认证客户端
TWI688253B (zh) 授權方法、請求授權的方法及裝置
US8898764B2 (en) Authenticating user through web extension using token based authentication scheme
US10848310B2 (en) Method and device for identifying user identity
JP6438031B2 (ja) クライアントのダウンロード及びインストール方法及び装置
US8838679B2 (en) Providing state service for online application users
WO2018068631A1 (zh) 账户登录方法、设备和服务器
CN109359237B (zh) 一种用于搜索寄宿程序的方法与设备
TW201528844A (zh) 確定登錄網站的終端是否爲移動終端的方法及伺服器
JP2019505056A (ja) 電子決済サービス処理方法及びデバイス並びに電子決済方法及びデバイス
EP3313041B1 (en) Application download method and device
US20160050218A1 (en) Anonymous Server Based User Settings Protection
CN114448722A (zh) 跨浏览器登录方法、装置、计算机设备和存储介质
CN114003404A (zh) 一种基于宿主程序的应用服务提供方法及设备
HK40035504A (zh) 一种认证方法、设备以及认证客户端
CN117807618A (zh) 数据处理方法、装置、存储介质及电子设备
HK1226563B (zh) 一种标识用户身份的方法及装置
HK1188877B (zh) 一种登录多域名网站的方法、系统以及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17838578

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019507769

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20197007139

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017838578

Country of ref document: EP

Effective date: 20190312