WO2016078182A1 - 敏感数据的授权方法、装置和系统 - Google Patents

敏感数据的授权方法、装置和系统 Download PDF

Info

Publication number
WO2016078182A1
WO2016078182A1 PCT/CN2014/095384 CN2014095384W WO2016078182A1 WO 2016078182 A1 WO2016078182 A1 WO 2016078182A1 CN 2014095384 W CN2014095384 W CN 2014095384W WO 2016078182 A1 WO2016078182 A1 WO 2016078182A1
Authority
WO
WIPO (PCT)
Prior art keywords
sensitive data
identifier
user terminal
party server
cloud storage
Prior art date
Application number
PCT/CN2014/095384
Other languages
English (en)
French (fr)
Inventor
邱彼特
Original Assignee
邱彼特
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 邱彼特 filed Critical 邱彼特
Publication of WO2016078182A1 publication Critical patent/WO2016078182A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • 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/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0281—Proxies
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • 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

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, an apparatus (such as a server, a cloud storage server, a user terminal) and a system for authorizing sensitive data.
  • the related art provides a user identity verification method for scanning a two-dimensional code.
  • the two-dimensional code server provides a user with a two-dimensional code for verifying whether the user identity is legal, and the user can scan the two-dimensional code to
  • the authentication server no longer needs to verify the user's account and password, and directly confirms the user's identity based on the QR code and other information.
  • the method avoids the step of the user inputting the authentication information frequently by scanning the two-dimensional code, and simplifies the verification process to some extent, but it still cannot solve the cumbersome operation of the user registration and the user privacy information filling process.
  • an object of the embodiments of the present invention is to provide a method and device for authorizing sensitive data (such as a server, a cloud storage server, a user terminal) and a system to simplify user sensitive operations on the basis of secure communication.
  • sensitive data such as a server, a cloud storage server, a user terminal
  • an embodiment of the present invention provides a method for authorizing sensitive data, the method comprising: a third-party server receiving a request for a sensitive data request from a client, wherein the sensitive data request request carries a content request identifier; a third-party server After the validity check of the client is passed, a sensitive data request list is generated according to the content request identifier, wherein the sensitive data request list includes: a third-party server identifier, a session identifier, and a content request identifier; the third-party server requests the sensitive data request list.
  • the third terminal server receives the sensitive data and the session identifier from the cloud storage server; wherein the sensitive data is obtained by the cloud storage server according to the sensitive data request list uploaded by the user terminal; the third party server according to the session identifier The sensitive data performs the corresponding operation and sends the result of the operation to the client and/or the user terminal.
  • the embodiment of the present invention further provides a method for authorizing sensitive data, including: the cloud storage server receives a sensitive data request list uploaded by the user terminal, wherein the sensitive data request list is determined by the third party server according to the sensitive data of the client.
  • the sensitive data request list includes: the identifier of the third party server, the session identifier, and the content request identifier; the cloud storage server requests the third party in the list according to the sensitive data The identifier of the server and the content request identifier acquire sensitive data; the cloud storage server sends the sensitive data and the session identifier to the third-party server according to the identifier of the third-party server, so that the third-party server performs corresponding operations on the sensitive data according to the session identifier.
  • the embodiment of the present invention further provides a server, including: a request receiving module, configured to receive a sensitive data request request from a client, where the sensitive data request request carries a content request identifier; and a list generating module is configured to: After the validity check of the client is passed, a sensitive data request list is generated according to the content request identifier, wherein the sensitive data request list includes: a server identifier, a session identifier, and a content request identifier; and a list notification module is used to request sensitive data.
  • a server including: a request receiving module, configured to receive a sensitive data request request from a client, where the sensitive data request request carries a content request identifier; and a list generating module is configured to: After the validity check of the client is passed, a sensitive data request list is generated according to the content request identifier, wherein the sensitive data request list includes: a server identifier, a session identifier, and a content request identifier; and a list notification module is used
  • the list is notified to the user terminal by the client; the data receiving module is configured to receive the sensitive data and the session identifier from the cloud storage server; wherein the sensitive data is obtained by the cloud storage server according to the sensitive data request list uploaded by the user terminal; the sensitive data processing Module for Perform corresponding operations on the sensitive data according to the session identifier, and send the operation result to the client and/or the user terminal.
  • the embodiment of the present invention further provides a cloud storage server, comprising: a list receiving module, configured to receive a sensitive data request list uploaded by a user terminal, wherein the sensitive data request list is determined by the third party server according to the sensitive data of the client.
  • the sensitive data request list includes: a third-party server identifier, a session identifier, and a content request identifier; and a sensitive data acquisition module for requesting the list according to the sensitive data Obtaining sensitive data; the data sending module is configured to send the sensitive data and the session identifier to the third-party server according to the identifier of the third-party server, so that the third-party server performs corresponding operations on the sensitive data according to the session identifier.
  • the embodiment of the present invention further provides an authorization system for sensitive data, including: a third-party server and a cloud storage server; wherein the third-party server is the server provided in the third aspect; the cloud storage server is The cloud storage server provided in the above fourth aspect.
  • an embodiment of the present invention further provides a method for authorizing sensitive data, including: a third-party server receives a request for a sensitive data request from a client, where the sensitive data request request carries a content request identifier; After the client passes the legality check, the sensitive data request list is generated according to the content request identifier, wherein the sensitive data request list includes: a third-party server identifier, a session identifier, and a content request identifier; the third-party server passes the sensitive data request list.
  • the client notifies the user terminal; the third-party server receives the sensitive data and the session identifier from the user terminal; wherein the sensitive data is obtained by the user terminal from the local database or from the cloud storage server according to the sensitive data request list; the third-party server is identified according to the session identifier Perform corresponding operations on sensitive data and send the results of the operation to the client and/or user terminal.
  • the embodiment of the present invention further provides a method for authorizing sensitive data, including: receiving, by a client terminal, a sensitive data request list notified by a third-party server, where the sensitive data request list is determined by a third-party server according to a client The content request identifier in the sensitive data request request is generated; the sensitive data request list includes: a third-party server identifier, a session identifier, and a content request identifier; the user terminal obtains an identifier according to the identifier and content of the third-party server in the sensitive data request list.
  • the local database obtains sensitive data from the cloud storage server; the user terminal sends the sensitive data and the session identifier to the third-party server according to the identifier of the third-party server, so that the third-party server performs corresponding operations on the sensitive data according to the session identifier.
  • the embodiment of the present invention further provides a server, including: a request request receiving module, configured to receive a sensitive data request request from a client, where the sensitive data request request carries a content request identifier; After the legality check is performed on the client, the sensitive data request list is generated according to the content request identifier, wherein the sensitive data request list includes: a server identifier, a session identifier, and a content request identifier; and a request list notification module is used for Sending the sensitive data request list to the user terminal through the client; the data and identifier receiving module is configured to receive the sensitive data and the session identifier from the user terminal; wherein the sensitive data is requested by the user terminal according to the sensitive data from the local database or from the local database
  • the cloud storage server acquires a processing module, configured to perform corresponding operations on the sensitive data according to the session identifier, and send the operation result to the client and/or the user terminal.
  • the embodiment of the present invention further provides a user terminal, including: a request list receiving module, configured to receive, by using a client, a sensitive data request list notified by a third party server, where the sensitive data request list is a third party server The request is generated according to the content of the client's sensitive data request request; the sensitive data request list includes: a third-party server identifier, a session identifier, and a content request identifier; and a data acquisition module for requesting the list from the local database or based on the sensitive data.
  • a request list receiving module configured to receive, by using a client, a sensitive data request list notified by a third party server, where the sensitive data request list is a third party server The request is generated according to the content of the client's sensitive data request request; the sensitive data request list includes: a third-party server identifier, a session identifier, and a content request identifier; and a data acquisition module for requesting the list from the local database or based on the sensitive data.
  • the cloud storage server acquires sensitive data
  • the data and identifier sending module is configured to send the sensitive data and the session identifier to the third-party server according to the identifier of the third-party server, so that the third-party server performs corresponding operations on the sensitive data according to the session identifier.
  • the embodiment of the present invention further provides an authorization system for sensitive data, including a third-party server and a user terminal, wherein the third-party server is the server provided in the eighth aspect, and the user terminal is the ninth aspect as described above. User terminal provided.
  • the device, and the system (such as the server, the cloud storage server, and the user terminal) provided by the embodiment of the present invention
  • the third-party server after receiving the request for sensitive data from the client, the third-party server triggers the user by sending a sensitive data request list.
  • the terminal notifies the cloud storage server to obtain corresponding sensitive data according to the list or triggers the user terminal to obtain corresponding sensitive data according to the list, and sends the sensitive data to the third-party server, and the entire sensitive data transmission process does not involve the website, and is effective. Prevents malicious websites or viruses from intercepting sensitive data.
  • the process of transmitting sensitive data does not require excessive participation of users, nor does it require users to memorize the correspondence between sensitive data and third-party servers, simplifying user operations and improving sensitive operations. Convenience and security.
  • FIG. 1 is a flowchart of a method for authorizing sensitive data described from a third-party server side according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for authorizing sensitive data described from a cloud storage server side according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a method for authorizing sensitive data according to an embodiment of the present invention.
  • FIG. 4 is a structural block diagram of a server according to an embodiment of the present invention.
  • FIG. 5 is a structural block diagram of a cloud storage server according to an embodiment of the present invention.
  • FIG. 6 is a structural block diagram of an authorization system for sensitive data provided by an embodiment of the present invention.
  • FIG. 7 is a flowchart of a method for authorizing another sensitive data described by a third-party server side according to an embodiment of the present invention.
  • FIG. 8 is a flowchart of a method for authorizing sensitive data described from a user terminal side according to an embodiment of the present invention
  • FIG. 9 is a structural block diagram of another server according to an embodiment of the present invention.
  • FIG. 10 is a structural block diagram of a user terminal according to an embodiment of the present invention.
  • FIG. 11 is a structural block diagram of another authorization system for sensitive data according to an embodiment of the present invention.
  • FIG. 12 is a structural block diagram of an apparatus for authorizing sensitive data according to an embodiment of the present invention.
  • an embodiment of the present invention provides a method and device for authorizing sensitive data (such as a server, a cloud storage server, a user terminal) and a system.
  • the method is described by taking a description from a third-party server side as an example, including the following steps:
  • Step S102 The third-party server receives a sensitive data request request from the client, where the sensitive data request request carries a content request identifier;
  • the client sends a sensitive data request request carrying the content request identifier to the third-party server, and the content request identifier is used to indicate the current request scene of the user, for example, the request scene is one of the following: User identity registration scenario, login authentication scenario or authorization of user privacy information (such as filling in credit card information or filling in mailing address, etc.).
  • the client here is associated with a third-party server, which may be an application on the user terminal, or may be a stand-alone terminal device, such as an ATM machine or an access control, etc., through which the user can access the third-party server.
  • a third-party server which may be an application on the user terminal, or may be a stand-alone terminal device, such as an ATM machine or an access control, etc., through which the user can access the third-party server.
  • Step S104 After the third party server passes the legality check on the client, the third-party server generates a sensitive data request list according to the content request identifier, where the sensitive data request list includes: a third-party server identifier, a session identifier, and a content request identifier. .
  • the identifier of the third-party server may be a domain name, an IP address, or an application key AppKey of the third-party server; the session identifier may be a string of random numbers or a time hash value; and the sensitive data request list may further include a group.
  • Metadata the metadata may include: field names of sensitive data, format requirements, and the like.
  • a third-party server and a device that provides sensitive data may also adopt a pre-contracted manner, that is, each content request identifier corresponds to a respective field name and format requirement, and both of them can make the construction of sensitive data conform to the regulations as long as the content request identifier is determined. Therefore, the sensitive data request list may not carry the above metadata.
  • the third-party server can verify the validity of the client by using the existing authentication method. For the illegal client, the third-party server will directly terminate the service requested by the third-party server.
  • Step S106 The third-party server notifies the user terminal of the sensitive data request list through the client.
  • the specific way for a third-party server to notify a sensitive data request list can be one of the following:
  • the third-party server converts the sensitive data request list into a corresponding pattern, and the client displays the pattern to the user terminal, so that the user terminal parses the pattern to obtain a sensitive data request list;
  • the third-party server sends the sensitive data request list to the client in text form, and triggers the client to convert the received sensitive data request list in text form into a corresponding pattern display to the user terminal, so that the user
  • the terminal parses the pattern to obtain a list of sensitive data requests
  • the above pattern includes one of the following: a two-dimensional code, a three-dimensional code, a four-dimensional code or a barcode.
  • the conversion of the sensitive data request list into a two-dimensional code can be converted by a third-party server, that is, the third-party server converts the sensitive data request list into a two-dimensional code, and sends the two-dimensional code to the client, the client.
  • the two-dimensional code is displayed to the user, and the user scans the two-dimensional code through the user terminal to parse out the sensitive data request list; the other way is that the client converts, that is, the third-party server sends the sensitive data request list in text form.
  • the client After receiving the sensitive data request list in text form, the client converts the sensitive data request list in text form into a two-dimensional code and presents it to the user, and the user scans the two-dimensional code through the user terminal to parse the sensitive data request list.
  • the two methods may be used in the actual application, which is not limited in the embodiment of the present invention.
  • the user can scan the pattern through a user terminal (such as a mobile phone).
  • a user terminal such as a mobile phone
  • the user terminal can scan the pattern before scanning the pattern.
  • the identity of the user is verified.
  • the verification method may include one of the following verification methods: (1) whether the user terminal verifies whether the biometric information of the user is legal; (2) the user terminal verifies whether the user name and password input by the user are legal; (3) whether the user terminal verifies whether the graphic input by the user is legitimate.
  • Step S108 The third-party server receives the sensitive data and the session identifier from the cloud storage server, where the sensitive data is obtained by the cloud storage server according to the sensitive data request list uploaded by the user terminal.
  • the cloud storage server receives the sensitive data request list uploaded by the user terminal, obtains the corresponding sensitive data according to the identifier and the content request identifier of the third-party server in the sensitive data request list, and obtains the sensitive data and the session identifier according to the identifier of the third-party server. Send to a third-party server.
  • Step S110 The third-party server performs a corresponding operation on the sensitive data according to the session identifier, and sends the operation result to the client and/or the user terminal.
  • the third-party server in the above method triggers the user terminal to notify the cloud storage server to send the sensitive data corresponding to the list to the third-party server by sending a sensitive data request list.
  • the data transmission process does not involve the website, which effectively prevents malicious websites or viruses from intercepting sensitive data.
  • the process of transmitting sensitive data does not require excessive participation of users, nor does it require the user to memorize the correspondence between sensitive data and third-party servers, simplifying The user's operation improves the convenience and security of sensitive operations.
  • the foregoing third-party server performing corresponding operations on the sensitive data according to the session identifier may include: the third-party server verifies whether the service logic of the sensitive data is correct according to the session identifier, and if correct, performs the session on the sensitive data. Identifies the corresponding operation.
  • the business logic mainly refers to the business rule.
  • the request scenario for determining the sensitive data according to the session identifier is the user identity registration scenario or the user privacy information authorization scenario
  • the third party server checks whether the fields of the sensitive data are legal; if legal, The service logic of the sensitive data is determined to be correct.
  • the request scenario of determining the sensitive data according to the session identifier is the identity login authentication
  • the third party server checks whether the login account and password of the sensitive data are legal. If legal, the business logic of the sensitive data is determined to be correct. .
  • the third-party server verifies that the business logic of the sensitive data is incorrect, the current operation is terminated, and the prompt information of the sensitive data is sent to the cloud storage server, or the prompt information is sent to the client or the user terminal.
  • the third-party server can determine whether the received sensitive data is authentic and reliable, and provide protection for subsequent sensitive operations.
  • the operation corresponding to the session identifier is performed on the sensitive data. For example, when the request scene is determined to be the user identity registration according to the session identifier, the third-party server fills the corresponding sensitive data into the corresponding entry one by one according to the preset filling format, and if a certain item is missing in the sensitive data, The content can be skipped, or the third-party server automatically generates a content to fill in the entry. If it is automatically generated, the automatically generated content can be fed back to the cloud storage server.
  • the cloud storage server can directly The information can be saved to the user terminal and saved by the user.
  • the third-party server sets the client to release the login operation of the user;
  • the third-party server uses the received sensitive data to set the corresponding operation on the client, such as filling in credit card information.
  • Step S202 The cloud storage server receives the sensitive data request list uploaded by the user terminal, where the sensitive data request list is generated by the third-party server according to the content request identifier in the sensitive data request request of the client, and is notified to the user terminal by the client;
  • the sensitive data request list includes: an identifier of a third-party server, a session identifier, and a content request identifier; the specific content of each identifier is as described above, and details are not described herein again.
  • Step S204 The cloud storage server acquires the sensitive data according to the identifier and the content request identifier of the third-party server in the sensitive data request list.
  • the sensitive data of each user terminal corresponding to different third-party servers is different.
  • the sensitive data corresponding to the content request identifier is used as the login authentication data (account and login password).
  • the user terminal 001 is in Baidu.
  • the login information of the (third-party server) is Zhang San, the login password is 123456, and the account of the user terminal 001 in Tencent is Zhang San 1 and the login password is 654321; therefore, the cloud storage server needs to be current for the user terminal.
  • Step S206 The cloud storage server sends the sensitive data and the session identifier to the third-party server according to the identifier of the third-party server, so that the third-party server performs corresponding operations on the sensitive data according to the session identifier.
  • the cloud storage server in the above method After receiving the sensitive data request list uploaded by the user terminal, the cloud storage server in the above method obtains the corresponding sensitive data according to the content carried in the list, and sends the sensitive data to the third-party server, and the entire sensitive data is not transmitted.
  • the process of transmitting sensitive data does not require excessive participation of users, nor does it require users to memorize the correspondence between sensitive data and third-party servers, which simplifies user operations. Improve the convenience and security of sensitive operations.
  • the cloud storage server obtains the sensitive data according to the identifier and the content request identifier of the third-party server in the sensitive data request list. For example, the cloud storage server obtains the third-party server in the list according to the sensitive data.
  • the identification and content request identifiers determine whether there is corresponding sensitive data in the cloud storage database, and if so, extract sensitive data from the cloud storage database; if not, the cloud storage server obtains the identifier and content of the third-party server in the sensitive data request list.
  • the identifier generates corresponding sensitive data or acquires corresponding sensitive data from the user terminal.
  • the cloud storage server can also obtain sensitive data according to the specific request scenario, for example: (1) when the content request identifier indicates that the sensitive data requested is the user identity registration data, the cloud storage Server generates login password from cloud storage Select the account of the corresponding user terminal in the database, and the registration information other than the login password and the account number, and use the account number, the login password, and the registration information other than the login password and the account as the sensitive data corresponding to the sensitive data request list; (2) When the content request identifier indicates that the requested sensitive data is the login authentication data, the cloud storage server searches the cloud storage database for the account and the login password of the identifier corresponding to the third-party server of the user terminal, and the account and the login password are used as the sensitive data request list.
  • Sensitive data When the content request identifier indicates that the requested sensitive data is privacy authorization data, the cloud storage server searches for the corresponding privacy authorization data from the cloud storage database, and uses the privacy authorization data as a sensitivity corresponding to the sensitive data request list. data.
  • the method further includes: the cloud storage server sending the acquired sensitive data to the user terminal, Upon receiving the confirmation information returned by the user terminal, the step of transmitting the sensitive data and the session identifier to the third party server according to the identity of the third party server is performed. If the user's confirmation information is not received, the user terminal is sent a prompt message or other processing methods are adopted.
  • the method may further include: the cloud storage server Sending the acquired sensitive data to the user terminal for modification; the cloud storage server receives the sensitive data modified by the user returned by the user terminal, and uses the modified sensitive data as the sensitive data corresponding to the final acquired sensitive data request list, and the modified sensitive data Synchronize to the cloud storage database.
  • the embodiment of the present invention provides a targeted and sensitive data acquisition optimization method for different request scenarios:
  • the cloud storage server When the content request identifier indicates that the request scene of the sensitive data is registered as the user identity, the cloud storage server generates a login password, and selects an account number of the corresponding user terminal and other registration information except the login password and the account number from the cloud storage database. (e.g., gender, date of birth, education, mobile phone number, ID number, etc.), the account, the login password, and other registration information are sent to the user terminal as the initial sensitive data corresponding to the identifier of the third-party server;
  • a login password e.g., gender, date of birth, education, mobile phone number, ID number, etc.
  • the user terminal displays the initial sensitive data to the user, waiting for the user to modify or confirm the initial sensitive data
  • the user terminal When receiving the modification operation of the user, the user terminal uploads the modified sensitive data to the cloud storage server; the cloud storage server receives the modified sensitive data, and the modified sensitivity is Sensing data as sensitive data corresponding to the identity and content request identifier of the third-party server, and synchronizing the modified sensitive data to the cloud storage database;
  • the user terminal uses the initial sensitive data as sensitive data corresponding to the identifier and content request identifier of the third party server, and synchronizes the initial sensitive data to the cloud storage database.
  • the user can modify the sensitive data sent by the cloud storage server, or modify the direct confirmation without modifying the data.
  • the registered sensitive data on the third-party server will be synchronized to the cloud storage database. It can be bound and saved according to the identifier of the third-party server, the identifier of the user terminal, and the sensitive data related to the registration.
  • the cloud storage server selects the account and the login password of the identifier corresponding to the third-party server of the user terminal from the cloud storage database, and the account and the login password are obtained. Sent to the user terminal;
  • the user terminal displays the account and the login password to the user, and after receiving the confirmation operation of the user, uploads the notification that the user has confirmed to the cloud storage server;
  • the cloud storage server After receiving the above notification, uses the account number and the login password as sensitive data corresponding to the identifier and content request identifier of the third-party server.
  • the cloud storage server selects the privacy authorization information of the identifier corresponding to the third-party server of the user terminal from the cloud storage database, and sends the privacy authorization information to the user terminal.
  • the user terminal displays the privacy authorization information to the user, and waits for the user to modify or confirm the privacy authorization information
  • the user terminal When receiving the modification operation of the user, the user terminal uploads the modified privacy authorization information to the cloud storage server; the cloud storage server receives the modified privacy authorization information, and uses the modified privacy authorization information as the third-party server.
  • the identification and content request sensitive data corresponding to the identifier, and synchronize the modified privacy authorization information to the cloud storage database;
  • the user terminal uses the above-mentioned privacy authorization information (ie, the information selected by the cloud storage server in step (1) and sent to the user terminal) as the identifier and content request identifier of the third-party server. Corresponding sensitive data.
  • the method includes the following steps:
  • step S302 the user accesses the third-party client and enters a sensitive data request scenario (such as logging in, registering, filling in credit card information, filling in a mailing address, etc.).
  • a sensitive data request scenario such as logging in, registering, filling in credit card information, filling in a mailing address, etc.
  • Step S304 The third-party client sends the sensitive data request scenario to the third-party server through HTTP or Socket (equivalent to sending a sensitive data request request to the third-party server).
  • Step S306 The third-party server verifies the legality of the third-party client (the phishing website, the cottage website, etc.), and if the third-party client is not legal, the process is directly terminated; if it is legal, step S308 is performed.
  • the third-party server verifies the legality of the third-party client (the phishing website, the cottage website, etc.), and if the third-party client is not legal, the process is directly terminated; if it is legal, step S308 is performed.
  • Step S308 the third-party server generates a sensitive data request list according to the above scenario (such as requesting the content identifier), the list includes at least the identifier (domain name, IP address, AppKey, etc.) of the third-party server, and the identification code of the list (equivalent to the above)
  • the session identifier may be a string of random numbers, or a time hash value, etc., indicating the metadata of the request scene (corresponding to the above-mentioned request content identifier), and the metadata may also include the field name and format requirement of the sensitive data.
  • step S310 the third-party server sends a list of sensitive data requests in the form of text or two-dimensional code (stacked, matrix, etc.) to the third-party client.
  • Step S312 the third party client displays the two-dimensional code of the sensitive data request list to the user. Specifically, the third-party client loads the received two-dimensional code (or the received text into a two-dimensional code) and loads it into the page for display to the user.
  • step S314 the user logs in to the user's personal terminal (account password login, biometric login, gesture login, etc.), and scans and parses the above two-dimensional code to obtain a sensitive data request list.
  • Step S316 the user personal terminal sends a sensitive data request list to the cloud storage server.
  • Step S318, the cloud storage server acquires the required sensitive data according to the identifier and metadata of the third-party server in the foregoing list (the data may be incomplete at this time); for example, by retrieving the required sensitive data in the cloud storage database, if It is a scenario where the user is registered.
  • the cloud storage server can also automatically generate a login password and add the generated login password to the sensitive data.
  • Step S320 The cloud storage server sends the foregoing sensitive data to the user personal terminal.
  • Step S322 the user personal terminal presents the sensitive data to the user, and the user checks the data and makes necessary modifications or additions (for sensitive data such as the net name and the motto, there may be a process of intelligently generating default data to reduce the time for the user to think). It can also be modified.
  • Step S324 the user checks the sensitive data and clicks the confirmation, and the user personal terminal sends the sensitive data updated and confirmed by the user to the cloud storage server.
  • step S326 the cloud storage server synchronizes the updated sensitive data (modified, added) to the cloud storage database.
  • Step S328 the cloud storage server retrieves the interface address (Web API, Web Service, etc.) of the third-party server according to the identification code in the above list.
  • Web API Web API, Web Service, etc.
  • Step S330 the cloud storage server sends the required sensitive data to the third-party server through the interface address.
  • Step S332 the third-party server receives the sensitive data and checks its business logic according to the scenario (if the login is made, the account information is checked, and if the registration or the form is filled, the field is checked), after the verification is passed, the above scenario is performed on the sensitive data. The operations required for the business.
  • step S334 the third-party server sends the operation result to the third-party client (only the third-party client is notified of a result, but the sensitive data is not leaked to the third-party client).
  • Step S336 the third party client completes the whole process of the sensitive data request scenario after receiving the result of the third-party server.
  • the above third party server may also send the verification result to the user's personal terminal (possibly transferred through the cloud storage server).
  • the website has not been exposed to sensitive data, which effectively prevents the interception of sensitive data of users such as phishing websites, keyboard recording Trojans, viruses, etc., and the user can not touch the keyboard (including the virtual keyboard) or touch the confirmation key only during the whole process.
  • sensitive data phishing websites, keyboard recording Trojans, viruses, etc.
  • the cloud storage server acts as a centralized user sensitive data storage. Server, if the user terminal is lost, the user can purchase a new user terminal and then recover its sensitive data from the cloud storage server, which has strong practicability.
  • the embodiment of the present invention further provides a server, where the server corresponds to the third-party server, as shown in FIG. 4, the server includes the following modules:
  • the request receiving module 41 is configured to receive a sensitive data request request from the client, where the sensitive data request request carries a content request identifier; the content request identifier is used to indicate the current request scene of the user, for example, requesting the scene as one of the following : User identity registration scenario, login authentication scenario or authorization of user privacy information (such as filling in credit card information or filling in mailing address, etc.).
  • the list generating module 42 is configured to generate a sensitive data request list according to the content request identifier after the legality check is performed on the client, where the sensitive data request list includes: the identifier of the server, the session identifier, and the content request identifier. ;
  • the list notification module 43 is configured to notify the user terminal of the sensitive data request list by using the foregoing client;
  • the data receiving module 44 is configured to receive the sensitive data and the session identifier from the cloud storage server, where the sensitive data is obtained by the cloud storage server according to the sensitive data request list uploaded by the user terminal;
  • the sensitive data processing module 45 is configured to perform a corresponding operation on the sensitive data according to the session identifier, and send the operation result to the client and/or the user terminal.
  • the server After receiving the sensitive data request request from the client, the server sends a sensitive data request list to trigger the user terminal to notify the cloud storage server to send the sensitive data corresponding to the list to the server, and the entire sensitive data transmission process is not involved. To the website, it effectively prevents malicious websites or viruses from intercepting sensitive data. At the same time, the process of transmitting sensitive data does not require excessive participation of users, nor does it require users to memorize the correspondence between sensitive data and servers, simplifying user operations and enhancing sensitivity. Convenience and security of operation.
  • the above-mentioned list notification module 43 includes: a pattern conversion and delivery unit, configured to convert the sensitive data request list into a corresponding pattern, and display the pattern to the user terminal through the client, so that the user terminal parses the pattern to obtain A list of sensitive data requests; or comprising: a list text issuing unit for transmitting the above-mentioned sensitive data request list to the client in text form, triggering the client to convert the received sensitive data request list in text form into corresponding
  • the pattern is displayed to the user terminal, so that the user terminal parses the pattern to obtain a sensitive data request list; wherein the pattern includes one of the following: a two-dimensional code, a three-dimensional code, a four-dimensional code or a barcode.
  • the sensitive data processing module includes: a service logic checking unit, configured to check whether the business logic of the sensitive data is correct according to the session identifier; and a sensitive data processing unit, configured to perform a session on the sensitive data when the verification result of the business logic checking unit is correct Identifies the corresponding operation.
  • the embodiment of the present invention further provides a cloud storage server.
  • the cloud storage server includes the following modules:
  • the list receiving module 51 is configured to receive a sensitive data request list uploaded by the user terminal, where the sensitive data request list is generated by the third-party server according to the content request identifier in the client's sensitive data request request, and is notified to the user terminal by the client.
  • the sensitive data request list includes: an identifier of a third-party server, a session identifier, and a content request identifier;
  • the sensitive data obtaining module 52 is configured to obtain sensitive data according to the sensitive data request list
  • the data sending module 53 is configured to send the sensitive data and the session identifier to the third-party server according to the identifier of the third-party server, so that the third-party server performs a corresponding operation on the sensitive data according to the session identifier.
  • the cloud server of the embodiment After receiving the sensitive data request list uploaded by the user terminal, the cloud server of the embodiment obtains the corresponding sensitive data according to the content carried in the list, and sends the sensitive data to the third-party server, and the entire sensitive data transmission process is not involved. To the website, it effectively prevents malicious websites or viruses from intercepting sensitive data. At the same time, the process of transmitting sensitive data does not require excessive participation of users, nor does it require users to memorize the correspondence between sensitive data and third-party servers, simplifying user operations and improving The convenience and security of sensitive operations.
  • the sensitive data obtaining module 52 includes: a sensitive data determining unit, configured to determine, according to the sensitive data request list, whether there is corresponding sensitive data in the cloud storage database; and the sensitive data extracting unit is configured to: when the sensitive data determining unit determines Sometimes, the sensitive data is extracted from the cloud storage database; the sensitive data obtaining unit is configured to generate corresponding sensitive data according to the sensitive data request list or obtain a sensitive data request list from the user terminal when the judgment result of the sensitive data determining unit is not available. Sensitive data.
  • the sensitive data obtaining module 52 includes: a registration data obtaining unit, configured to generate a login password when the content request identifier indicates that the requested sensitive data is user identity registration data, and select an account of the corresponding user terminal from the cloud storage database, And registration information other than the login password and the account number, the account number, the login password, and the registration information other than the login password and the account number are used as sensitive data corresponding to the sensitive data request list; the login authentication data obtaining unit is used to obtain the content identification identifier When the sensitive data requested is the login authentication data, the account and the login password of the identifier corresponding to the third-party server of the user terminal are searched from the cloud storage database, and the account and the login password are used as sensitive data corresponding to the sensitive data request list; the privacy authorization data is obtained.
  • the obtaining unit is configured to: when the content request identifier indicates that the requested sensitive data is the privacy authorization data, search for the corresponding privacy authorization data from the cloud storage database, and use the privacy authorization data as the sensitive data corresponding to the sensitive data
  • the sensitive data in the embodiment of the present invention is stored in the cloud storage server.
  • the cloud storage server obtains the corresponding sensitive data through the sensitive data request list sent by the third-party server, and Provided to a third-party server, the operation is simple and convenient, and the process of transmitting sensitive data does not reach the website, so it is safe and reliable.
  • the embodiment of the present invention further provides an authorization system for sensitive data.
  • the system includes: a third-party server 40 and a cloud storage server 50;
  • the specific structure of the third-party server may adopt the server structure shown in FIG. 4, and the structure of the cloud storage server 50 may refer to the cloud storage server structure shown in FIG. 5.
  • the third-party server in the system After receiving the request for sensitive data from the client, the third-party server in the system sends a sensitive data request list to trigger the user terminal to notify the cloud storage server to send the sensitive data corresponding to the list to the third-party server.
  • the process of transmitting sensitive data does not involve the website, effectively preventing malicious websites or viruses from intercepting sensitive data.
  • the process of transmitting sensitive data does not require excessive participation of users, nor does the user need to memorize the correspondence between sensitive data and third-party servers. Simplifies user operations and improves the convenience and security of sensitive operations.
  • the sensitive data is transmitted through the cloud storage server, and in the actual application, the sensitive data can be directly transmitted through the user terminal.
  • the embodiment of the present invention further provides a method for authorizing sensitive data. Referring to the flowchart of the authorization method for sensitive data shown in FIG. 7, the method is described by using a third-party server side description as an example, including the following steps:
  • Step S702 The third-party server receives a sensitive data request request from the client, where the sensitive data request request carries a content request identifier.
  • Step S704 After the third-party server passes the legality check on the client, the third-party server generates a sensitive data request list according to the content request identifier, where the sensitive data request list includes: an identifier of the third-party server, a session identifier, and a content request identifier;
  • Step S706 the third-party server notifies the user terminal to the sensitive data request list through the client;
  • Step S708 The third-party server receives the sensitive data and the session identifier from the user terminal, where the sensitive data is obtained by the user terminal from the local database or from the cloud storage server according to the sensitive data request list;
  • Step S710 The third-party server performs a corresponding operation on the sensitive data according to the session identifier, and sends the operation result to the client and/or the user terminal.
  • the third-party server after receiving the sensitive data request request from the client, the third-party server triggers the user terminal to obtain the sensitive data corresponding to the list by sending the sensitive data request list, and sends the sensitive data to the third-party server.
  • the entire process of transmitting sensitive data does not involve the website, effectively preventing malicious websites or viruses from intercepting sensitive data, and sensitive data.
  • the transfer process does not require excessive user participation, nor does the user need to memorize the correspondence between sensitive data and third-party servers, simplifying user operations and improving the convenience and security of sensitive operations.
  • the method is described by taking the description from the user terminal side as an example, and includes the following steps:
  • Step S802 the user terminal receives the sensitive data request list notified by the third-party server through the client, where the sensitive data request list is generated by the third-party server according to the content request identifier in the sensitive data request request of the client; the sensitive data request list includes : the identity, session identifier, and content request identifier of the third-party server;
  • Step S804 the user terminal acquires sensitive data from the local database or from the cloud storage server according to the identifier and the content request identifier of the third-party server in the sensitive data request list.
  • Step S806 The user terminal sends the sensitive data and the session identifier to the third-party server according to the identifier of the third-party server, so that the third-party server performs corresponding operations on the sensitive data according to the session identifier.
  • the user terminal after receiving the sensitive data request list notified by the third-party server, acquires corresponding sensitive data according to the content carried in the list, and sends the sensitive data to the third-party server, and the entire sensitive data.
  • the delivery process does not involve the website, which effectively prevents malicious websites or viruses from intercepting sensitive data.
  • the process of transmitting sensitive data does not require excessive participation of users, nor does it require users to memorize the correspondence between sensitive data and third-party servers, simplifying users. The operation enhances the convenience and security of sensitive operations.
  • the foregoing user terminal receiving the sensitive data request list notified by the third-party server by the client may include: receiving, by the client, a pattern of the sensitive data request list through the client; wherein the pattern is a third-party server or a client according to the The sensitive data request list is generated, including one of the following: a two-dimensional code, a three-dimensional code, a four-dimensional code, or a barcode; and the user terminal parses the pattern to obtain a sensitive data request list.
  • the user terminal receives the sensitive data request list sent by the third-party server through the client, and includes: when the user terminal receives the indication of the user opening the scanning application, verifying whether the identity of the user is legal, and if it is legal, scanning The pattern displayed on the client.
  • the user terminal verifies whether the identity of the user is legal, including one of the following authentication methods: (1) the user terminal verifies whether the biometric information of the user is legal; (2) the user terminal verifies whether the user name and password input by the user are legal; (3) the user terminal Verify that the graphics entered by the user are legal.
  • the obtaining, by the user terminal, the sensitive data from the cloud storage server may include: the user terminal sending the sensitive data request list to the cloud storage server, so that the cloud storage server searches for the sensitive data according to the identifier and the content request identifier of the third-party server in the sensitive data request list. Or the sensitive data is generated according to the identifier and content request identifier of the third-party server in the sensitive data request list; the user terminal receives the sensitive data sent by the cloud storage server.
  • the embodiment of the present invention further provides a server.
  • the server includes the following modules:
  • the request request receiving module 91 is configured to receive a sensitive data request request from the client, where the sensitive data request request carries a content request identifier;
  • the request list generating module 92 is configured to generate a sensitive data request list according to the content request identifier after the legality check is performed on the client, where the sensitive data request list includes: the identifier of the server, the session identifier, and the content request identifier;
  • the request list notification module 93 is configured to notify the user terminal of the sensitive data request list by using the client;
  • the data and identifier receiving module 94 is configured to receive sensitive data and a session identifier from the user terminal, where the sensitive data is obtained by the user terminal from the local database or from the cloud storage server according to the sensitive data request list;
  • the processing module 95 is configured to perform corresponding operations on the sensitive data according to the session identifier, and send the operation result to the client and/or the user terminal.
  • the server of the embodiment After receiving the sensitive data request request from the client, the server of the embodiment triggers the user terminal to obtain the sensitive data corresponding to the list by sending the sensitive data request list, and sends the sensitive data to the server, and transmits the entire sensitive data.
  • the process does not involve the website, effectively preventing malicious websites or viruses from intercepting sensitive data.
  • the process of transmitting sensitive data does not require excessive participation of users, nor does it require the user to memorize the correspondence between sensitive data and the server, which simplifies the operation of the user. Improves the convenience and security of sensitive operations.
  • the embodiment of the present invention further provides a user terminal.
  • the user terminal includes the following modules:
  • the request list receiving module 12 is configured to receive, by the client, a sensitive data request list notified by the third party server, wherein the sensitive data request list is generated by the third party server according to the content request identifier in the sensitive data request request of the client; the sensitive data
  • the request list includes: the identity of the third-party server, the session identifier, and the content request identifier;
  • the data obtaining module 14 is configured to obtain sensitive data from a local database or from a cloud storage server according to the sensitive data request list;
  • the data and identifier sending module 16 is configured to send the sensitive data and the session identifier to the third-party server according to the identifier of the third-party server, so that the third-party server performs corresponding operations on the sensitive data according to the session identifier.
  • the user terminal of the embodiment After receiving the sensitive data request list notified by the third-party server, the user terminal of the embodiment obtains the corresponding sensitive data according to the content carried in the list, and sends the sensitive data to the third-party server, and the entire sensitive data is not transmitted.
  • the process of transmitting sensitive data does not require excessive participation of users, nor does it require users to memorize the correspondence between sensitive data and third-party servers, which simplifies user operations. Improve the convenience and security of sensitive operations.
  • the user terminal may further include: a user identity verification module, configured to verify whether the identity of the user is legal when receiving the scan indication of the user; and a scanning module, configured to scan the sensitive data request list when the user identity verification module verifies that the user is legitimate A pattern; a parsing module for parsing the pattern to obtain a list of sensitive data requests.
  • the user authentication module can adopt the specific verification mode in the foregoing method when verifying the identity of the user, and details are not described herein again.
  • an embodiment of the present invention further provides an authorization system for sensitive data, the system comprising a third-party server and a user terminal, wherein the authorization system for sensitive data as shown in FIG.
  • the third-party server 90 can be implemented by using the server structure shown in FIG. 9.
  • the user terminal 100 can be implemented by using the structure of the user terminal shown in FIG. 10, and the specific functions of the third-party server and the user terminal in the system are the same as the above.
  • the embodiments are similar and will not be described in detail herein.
  • the technology provided in the foregoing embodiment can be applied to user identity registration, login, and other private information authorization.
  • the user is prevented from inputting sensitive data through the keyboard, and the possibility of being attacked by phishing is improved to some extent.
  • the technology also converts the filling of sensitive data such as login, registration, and personal privacy information into the transmission of sensitive data.
  • the user does not need to learn the input method of the keyboard to realize the corresponding operation, which reduces the learning cost and is convenient for various users to use. User experience.
  • each block of the flowchart or block diagram can represent a module, a program segment, or a portion of code that includes one or more of the Executable instructions.
  • the functions noted in the blocks may also occur in a different order than that illustrated in the drawings. For example, two consecutive blocks may be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending upon the functionality involved.
  • each block of the block diagrams and/or flowcharts, and combinations of blocks in the block diagrams and/or flowcharts can be implemented in a dedicated hardware-based system that performs the specified function or function. Or it can be implemented by a combination of dedicated hardware and computer instructions.
  • an embodiment of the present invention further provides an authorization device 120 for sensitive data, including: a processor 20, a memory 21, a bus 22, and a communication interface 23.
  • the processor 20, the communication interface 23, and the memory 21 pass through the bus 22.
  • the processor 20 is configured to execute an executable module, such as a computer program, stored in the memory 21.
  • the memory 21 may include a high speed random access memory (RAM: Random Access Memory), and may also include a non-volatile memory, such as at least one disk storage.
  • RAM Random Access Memory
  • the communication connection between the system network element and at least one other network element is implemented by at least one communication interface 23 (which may be wired or wireless), and may use an Internet, a wide area network, a local network, a metropolitan area network, or the like.
  • the bus 22 can be an ISA bus, a PCI bus, or an EISA bus.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one double-headed arrow is shown in Figure 12, but it does not mean that there is only one bus or one type of bus.
  • the memory 21 is configured to store a program, and the processor 20 executes the program after receiving the execution instruction, and the device (server, cloud server or user terminal) defined by the process disclosed in any embodiment of the present invention. The method performed may be applied to processor 20 or implemented by processor 20.
  • Processor 20 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 20 or an instruction in the form of software.
  • the processor 20 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP processor, etc.), or a digital signal processor (DSP), an application specific integrated circuit. (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention may be implemented or carried out.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as a hardware decoding processor, or may be performed by using a combination of hardware and software modules in the decoding processor. to make.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 21, and the processor 20 reads the information in the memory 21 and performs the steps of the above method in combination with its hardware.
  • the embodiment of the invention further provides a computer program product for performing a method for authorizing sensitive data, comprising a computer readable storage medium storing program code, the program code comprising instructions for executing the method described in the foregoing method embodiment
  • a computer program product for performing a method for authorizing sensitive data, comprising a computer readable storage medium storing program code, the program code comprising instructions for executing the method described in the foregoing method embodiment
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some communication interface, device or unit, and may be electrical, mechanical or otherwise.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read only memory (ROM, Read-Only) Memory, random access memory (RAM), disk or optical disk, and other media that can store program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Computer And Data Communications (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本发明提供了一种敏感数据的授权方法、装置和系统，其中，该方法包括：第三方服务器接收来自客户端的敏感数据索取请求，其中，该敏感数据索取请求携带有内容索取标识；第三方服务器对客户端进行合法性检验通过后，根据内容索取标识生成敏感数据索取清单；第三方服务器将敏感数据索取清单通过客户端通知给用户终端；第三方服务器接收来自云存储服务器的敏感数据和会话标识；其中，该敏感数据由云存储服务器根据用户终端上传的敏感数据索取清单获取；第三方服务器根据会话标识对敏感数据执行相应的操作，并将操作结果发送给客户端和/或用户终端。通过本发明，简化了用户的操作，提升了敏感操作的便利性和安全性。

Description

敏感数据的授权方法、装置和系统 技术领域
本发明涉及通信领域，具体而言，涉及敏感数据的授权方法、装置(如服务器、云存储服务器、用户终端)和系统。
背景技术
随着网络技术的发展，具有各种应用功能的网站越来越多，通常这些网站的应用功能仅对已注册的用户开放，导致用户在不同网站注册的用户名(也称账号)和密码等信息也越来越多。
在进行注册时，需要填写很多个人资料，并且每次登录，都需要输入正确的用户名和密码，有的网站甚至还需要输入其它认证信息，这些步骤涉及到频繁的键盘操作，学习成本高，许多网民(尤其是老年网民)至今不具备独立完成这些步骤的能力。其次，登录、注册、个人资料填写是高频操作，但每一次操作都需要填写重复的信息，过程非常繁琐、用户体验很差。其三，一个网民往往拥有几十甚至上百个网络账户，为了记忆方便，许多网民只使用一组(或有限的几组)账号密码，这带来了巨大的安全隐患，一旦账号在A网站丢失，B网站也会受到牵连。此外，钓鱼网站，键盘记录软件、木马等攻击手段使得把账户及个人资料直接提交给网站客户端变成一项高危操作。
相关技术中提供了一种扫描二维码的用户身份验证方法，该方法中，二维码服务器会向用户提供一个专门用户验证用户身份是否合法的二维码，用户可以扫描该二维码给验证服务器，验证服务器不再需要验证用户的账号和密码，直接根据二维码等信息确认用户身份。该方法通过扫描二维码的方式避免了用户频繁输入身份验证信息的步骤，一定程度上简化了验证流程，但其仍无法解决用户注册与用户隐私信息填写过程的繁琐操作。
发明人在研究中发现，现有通信中的敏感数据操作存在用户频繁参与的问题。
发明内容
有鉴于此，本发明实施例的目的在于提供一种敏感数据的授权方法、装置(如服务器、云存储服务器、用户终端)和系统，以在安全通信的基础上简化用户的敏感操作。
第一方面，本发明实施例提供了一种敏感数据的授权方法，该方法包括：第三方服务器接收来自客户端的敏感数据索取请求，其中，该敏感数据索取请求携带有内容索取标识；第三方服务器对客户端进行合法性检验通过后，根据内容索取标识生成敏感数据索取清单，其中，该敏感数据索取清单包括：第三方服务器的标识、会话标识和内容索取标识；第三方服务器将敏感数据索取清单通过客户端通知给用户终端；第三方服务器接收来自云存储服务器的敏感数据和会话标识；其中，该敏感数据由云存储服务器根据用户终端上传的敏感数据索取清单获取；第三方服务器根据会话标识对敏感数据执行相应的操作，并将操作结果发送给客户端和/或用户终端。
第二方面，本发明实施例还提供了一种敏感数据的授权方法，包括：云存储服务器接收用户终端上传的敏感数据索取清单，其中，该敏感数据索取清单由第三方服务器根据客户端的敏感数据索取请求中的内容索取标识生成，并且通过客户端通知给用户终端；该敏感数据索取清单包括：第三方服务器的标识、会话标识和内容索取标识；云存储服务器根据敏感数据索取清单中的第三方服务器的标识和内容索取标识获取敏感数据；云存储服务器根据第三方服务器的标识将敏感数据和会话标识发送给第三方服务器，以使第三方服务器根据会话标识对敏感数据执行相应的操作。
第三方面，本发明实施例还提供了一种服务器，包括：请求接收模块，用于接收来自客户端的敏感数据索取请求，其中，敏感数据索取请求携带有内容索取标识；清单生成模块，用于对客户端进行合法性检验通过后，根据内容索取标识生成敏感数据索取清单，其中，该敏感数据索取清单包括：服务器的标识、会话标识和内容索取标识；清单通知模块，用于将敏感数据索取清单通过客户端通知给用户终端；数据接收模块，用于接收来自云存储服务器的敏感数据和会话标识；其中，该敏感数据由云存储服务器根据用户终端上传的敏感数据索取清单获取；敏感数据处理模块，用于 根据会话标识对敏感数据执行相应的操作，并将操作结果发送给客户端和/或用户终端。
第四方面，本发明实施例还提供了一种云存储服务器，包括：清单接收模块，用于接收用户终端上传的敏感数据索取清单，其中，敏感数据索取清单由第三方服务器根据客户端的敏感数据索取请求中的内容索取标识生成，并且通过客户端通知给用户终端；该敏感数据索取清单包括：第三方服务器的标识、会话标识和内容索取标识；敏感数据获取模块，用于根据敏感数据索取清单获取敏感数据；数据发送模块，用于根据第三方服务器的标识将敏感数据和会话标识发送给第三方服务器，以使第三方服务器根据会话标识对敏感数据执行相应的操作。
第五方面，本发明实施例还提供了一种敏感数据的授权系统，包括：第三方服务器和云存储服务器；其中，第三方服务器为如上述第三方面中提供的服务器；云存储服务器为如上述第四方面中提供的云存储服务器。
第六方面，本发明实施例还提供了一种敏感数据的授权方法，包括：第三方服务器接收来自客户端的敏感数据索取请求，其中，该敏感数据索取请求携带有内容索取标识；第三方服务器对客户端进行合法性检验通过后，根据内容索取标识生成敏感数据索取清单，其中，该敏感数据索取清单包括：第三方服务器的标识、会话标识和内容索取标识；第三方服务器将敏感数据索取清单通过客户端通知给用户终端；第三方服务器接收来自用户终端的敏感数据和会话标识；其中，该敏感数据由用户终端根据敏感数据索取清单从本地数据库或者从云存储服务器获取；第三方服务器根据会话标识对敏感数据执行相应的操作，将操作结果发送给客户端和/或用户终端。
第七方面，本发明实施例还提供了一种敏感数据的授权方法，包括：用户终端通过客户端接收第三方服务器通知的敏感数据索取清单，其中，该敏感数据索取清单由第三方服务器根据客户端的敏感数据索取请求中的内容索取标识生成；敏感数据索取清单包括：第三方服务器的标识、会话标识和内容索取标识；用户终端根据敏感数据索取清单中的第三方服务器的标识和内容索取标识从本地数据库或者从云存储服务器获取敏感数据；用户终端根据第三方服务器的标识将敏感数据和会话标识发送给第三方服务器，以使第三方服务器根据会话标识对敏感数据执行相应的操作。
第八方面，本发明实施例还提供了一种服务器，包括：索取请求接收模块，用于接收来自客户端的敏感数据索取请求，其中，该敏感数据索取请求携带有内容索取标识；索取清单生成模块，用于对客户端进行合法性检验通过后，根据内容索取标识生成敏感数据索取清单，其中，该敏感数据索取清单包括：服务器的标识、会话标识和内容索取标识；索取清单通知模块，用于将敏感数据索取清单通过客户端通知给用户终端；数据和标识接收模块，用于接收来自用户终端的敏感数据和会话标识；其中，该敏感数据由用户终端根据敏感数据索取清单从本地数据库或者从云存储服务器获取；处理模块，用于根据会话标识对敏感数据执行相应的操作，并将操作结果发送给客户端和/或用户终端。
第九方面，本发明实施例还提供了一种用户终端，包括：索取清单接收模块，用于通过客户端接收第三方服务器通知的敏感数据索取清单，其中，该敏感数据索取清单为第三方服务器根据客户端的敏感数据索取请求中的内容索取标识生成的；敏感数据索取清单包括：第三方服务器的标识、会话标识和内容索取标识；数据获取模块，用于根据敏感数据索取清单从本地数据库或者从云存储服务器获取敏感数据；数据和标识发送模块，用于根据第三方服务器的标识将敏感数据和会话标识发送给第三方服务器，以使第三方服务器根据会话标识对敏感数据执行相应的操作。
第十方面，本发明实施例还提供了一种敏感数据的授权系统，包括第三方服务器和用户终端，其中，第三方服务器为如上述第八方面提供的服务器，用户终端为如上述第九方面提供的用户终端。
本发明实施例提供的方法、装置和系统(如服务器、云存储服务器、用户终端)中，第三方服务器在接收到客户端的敏感数据索取请求后，通过下发敏感数据索取清单的方式，触发用户终端通知云存储服务器根据该清单获取对应的敏感数据或者触发用户终端根据该清单获取对应的敏感数据，并将该敏感数据发送给该第三方服务器，整个敏感数据的传递过程没有涉及到网站，有效防止了恶意网站或病毒截获敏感数据，同时，敏感数据的传递过程不需要用户过多参与，也不需要用户记忆敏感数据与第三方服务器的对应关系，简化了用户的操作，提升了敏感操作的便利性和安全性。
为使本发明的上述目的、特征和优点能更明显易懂，下文特举较佳实施例，并配合所附附图，作详细说明如下。
附图说明
为了更清楚地说明本发明实施例的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，应当理解，以下附图仅示出了本发明的某些实施例，因此不应被看作是对范围的限定
图1示出了本发明实施例提供的从第三方服务器侧描述的敏感数据的授权方法流程图；
图2示出了本发明实施例提供的从云存储服务器侧描述的敏感数据的授权方法流程图；
图3示出了本发明实施例提供的敏感数据的授权方法的示意图；
图4示出了本发明实施例提供的服务器的结构框图；
图5示出了本发明实施例提供的云存储服务器的结构框图；
图6示出了本发明实施例提供的敏感数据的授权系统的结构框图；
图7示出了本发明实施例提供的从第三方服务器侧描述的另一种敏感数据的授权方法流程图；
图8示出了本发明实施例提供的从用户终端侧描述的敏感数据的授权方法流程图；
图9示出了本发明实施例提供的另一种服务器的结构框图；
图10示出了本发明实施例提供的用户终端的结构框图；
图11示出了本发明实施例提供的另一种敏感数据的授权系统的结构框图；
图12示出了本发明实施例提供的敏感数据的授权装置的结构框图。
具体实施方式
下面将结合本发明实施例中附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。通常在此处附图中描述和示出的本发明实施例的组件可以以各种不同的配置来布置和设计。
考虑到用户经常需要在各个网站注册、登录和填写一些个人隐私信息(例如：填写银行卡或信用卡信息、填写邮寄地址等信息)，这些数据如 果均由用户手动完成，不但效率低下，而且也容易被恶意网站截获，安全性和操作的便利性均比较低。基于此，本发明实施例提供了一种敏感数据的授权方法、装置(如服务器、云存储服务器、用户终端)和系统。
参见图1所示的敏感数据的授权方法流程图，该方法以从第三方服务器侧描述为例进行说明，包括以下步骤：
步骤S102，第三方服务器接收来自客户端的敏感数据索取请求，其中，该敏感数据索取请求携带有内容索取标识；
用户通过客户端打开敏感数据索取场景后，客户端向第三方服务器发送携带内容索取标识的敏感数据索取请求，该内容索取标识用以指明用户当前的索取场景，例如：索取场景为以下之一：用户身份注册场景、登录认证场景或用户隐私信息授权(如填写信用卡信息或填写邮寄地址等)场景等。
这里的客户端是与第三方服务器相关联的，其可以是用户终端上的一个应用，也可以是独立的终端设备，例如：ATM机或者门禁等，用户通过该客户端可以访问第三方服务器。
步骤S104，第三方服务器对所述客户端进行合法性检验通过后，根据上述内容索取标识生成敏感数据索取清单，其中，该敏感数据索取清单包括：第三方服务器的标识、会话标识和内容索取标识。
第三方服务器的标识可以采用第三方服务器的域名、IP地址或应用密钥AppKey等；会话标识可以是一串随机数或者一个时间哈希值等；另外，该敏感数据索取清单还可以包括一组元数据，该元数据可以包括：敏感数据的字段名称、格式要求等信息。或者第三方服务器与提供敏感数据的设备间也可以采用预先约定方式，即每个内容索取标识对应各自的字段名称和格式要求，二者只要确定内容索取标识，就可以使敏感数据的构建符合规定，因此敏感数据索取清单也可以不携带上述元数据。
第三方服务器可以采用现有的验证方式验证客户端的合法性，对于不合法的客户端，第三方服务器将直接终止其请求的服务。
步骤S106，第三方服务器将敏感数据索取清单通过上述客户端通知给用户终端；
第三方服务器通知敏感数据索取清单的具体方式可以采用如下方式之一：
(1)第三方服务器将所述敏感数据索取清单转换为对应的码型，通过所述客户端向用户终端展示所述码型，以使该用户终端解析该码型得到敏感数据索取清单；
(2)第三方服务器将所述敏感数据索取清单以文本形式下发给客户端，触发客户端将接收到的文本形式的敏感数据索取清单转换为对应的码型展示给用户终端，以使用户终端解析该码型得到敏感数据索取清单；
其中，上述码型包括以下中的一个：二维码、三维码、四维码或条形码等。
以敏感数据索取清单转换为二维码为例，该转换操作可以由第三方服务器进行转换，即第三方服务器将敏感数据索取清单转换为二维码，向客户端下发二维码，客户端将二维码展示给用户，用户通过用户终端扫描该二维码，解析出敏感数据索取清单；另一种方式是由客户端进行转换，即第三方服务器将敏感数据索取清单以文本形式下发给客户端，客户端接收到文本形式的敏感数据索取清单后，将文本形式的敏感数据索取清单转换为二维码展示给用户，用户通过用户终端扫描该二维码，解析出敏感数据索取清单。实际应用中这两种方式可以任选一种，本发明实施例不对其进行限定。
当客户端向用户展示敏感数据索取清单的码型时，用户可以通过一个用户终端(如：手机)扫描该码型，为了增加操作的安全性，在扫描该码型之前，用户终端可以对该用户的身份进行验证。验证方式可以包括以下验证方式之一：(1)用户终端验证用户的生物特征信息是否合法；(2)用户终端验证用户输入的用户名和密码是否合法；(3)用户终端验证用户输入的图形是否合法。
步骤S108，第三方服务器接收来自云存储服务器的敏感数据和会话标识；其中，该敏感数据由云存储服务器根据用户终端上传的敏感数据索取清单获取。
云存储服务器接收用户终端上传的敏感数据索取清单，根据敏感数据索取清单中的第三方服务器的标识和内容索取标识获取对应的敏感数据，并根据第三方服务器的标识将获取的敏感数据和会话标识发送给第三方服务器。
步骤S110，第三方服务器根据会话标识对上述敏感数据执行相应的操作，并将操作结果发送给上述客户端和/或用户终端。
上述方法中的第三方服务器在接收到客户端的敏感数据索取请求后，通过下发敏感数据索取清单的方式，触发用户终端通知云存储服务器将该清单对应的敏感数据发送给第三方服务器，整个敏感数据的传递过程没有涉及到网站，有效防止了恶意网站或病毒截获敏感数据，同时，敏感数据的传递过程不需要用户过多参与，也不需要用户记忆敏感数据与第三方服务器的对应关系，简化了用户的操作，提升了敏感操作的便利性和安全性。
为了增强操作的有效性，上述第三方服务器根据会话标识对上述敏感数据执行相应的操作可以包括：第三方服务器根据会话标识检验上述敏感数据的业务逻辑是否正确，如果正确，对敏感数据执行该会话标识对应的操作。例如：业务逻辑主要是指业务规则，例如：当根据会话标识确定敏感数据的索取场景为用户身份注册场景或用户隐私信息授权场景时，第三方服务器检验敏感数据的各个字段是否合法；如果合法，则确定敏感数据的业务逻辑正确；当根据会话标识确定敏感数据的索取场景为身份登录认证时，第三方服务器检验敏感数据的登录账号和密码是否合法，如果合法，确定该敏感数据的业务逻辑正确。
如果第三方服务器检验敏感数据的业务逻辑不正确，则终止当前操作，还可以向云存储服务器发送敏感数据有误的提示信息，或者向客户端或用户终端发送该提示信息。通过上述业务逻辑的检验方式，第三方服务器能够判断出接收到的敏感数据是否真实可靠，为后续的敏感操作提供保障。
第三方服务器检验敏感数据的业务逻辑正确后，对敏感数据执行会话标识对应的操作。例如：当根据会话标识确定索取场景为用户身份注册时，第三方服务器将获取的敏感数据按照预先设定的填写格式逐一填入对应的表项，如果发现敏感数据中缺失某一表项的相关内容时，可以跳过该表项不填，或者第三方服务器自动生成一个内容填入该表项，若是自动生成的方式，还可以将自动生成的内容反馈给云存储服务器，云存储服务器可以直接保存该信息，也可以发给用户终端，由用户确认后保存；当根据会话标识确定索取场景为用户身份登录认证时，第三方服务器设置客户端放行该用户的登录操作；当根据会话标识确定索取场景为用户隐私信息授权时，第三方服务器使用接收到的敏感数据设置客户端上对应的操作，例如填写信用卡信息等。
参见图2所示的敏感数据的授权方法流程图，该方法以从云服务器侧描述为例进行说明，包括以下步骤：
步骤S202，云存储服务器接收用户终端上传的敏感数据索取清单，其中，该敏感数据索取清单由第三方服务器根据客户端的敏感数据索取请求中的内容索取标识生成，并且通过客户端通知给用户终端；该敏感数据索取清单包括：第三方服务器的标识、会话标识和内容索取标识；各个标识的具体内容如上所述，这里不再赘述。
步骤S204，云存储服务器根据敏感数据索取清单中的第三方服务器的标识和内容索取标识获取敏感数据；
在云存储服务器上，每个用户终端对应不同的第三方服务器的敏感数据会有所不同，以内容索取标识对应的敏感数据为登录认证数据(账号和登录密码)为例，用户终端001在百度(第三方服务器)的登录信息的账号为张三，登录密码为123456；而用户终端001在腾讯的登录信息的账号为张三1，登录密码为654321；所以云存储服务器需要针对该用户终端当前对应的第三方服务器的标识和内容索取标识获取敏感数据。
步骤S206，云存储服务器根据第三方服务器的标识将敏感数据和会话标识发送给第三方服务器，以使第三方服务器根据会话标识对敏感数据执行相应的操作。
上述方法中的云存储服务器在接收到用户终端上传的敏感数据索取清单后，根据清单中携带的内容获取对应的敏感数据，并将该敏感数据发送给第三方服务器，整个敏感数据的传递过程没有涉及到网站，有效防止了恶意网站或病毒截获敏感数据，同时，敏感数据的传递过程不需要用户过多参与，也不需要用户记忆敏感数据与第三方服务器的对应关系，简化了用户的操作，提升了敏感操作的便利性和安全性。
本发明实施例中，云存储服务器根据敏感数据索取清单中的第三方服务器的标识和内容索取标识获取敏感数据可以有多种形式，例如：云存储服务器根据敏感数据索取清单中的第三方服务器的标识和内容索取标识判断云存储数据库中是否有对应的敏感数据，如果有，从云存储数据库中提取敏感数据；如果没有，云存储服务器根据敏感数据索取清单中的第三方服务器的标识和内容索取标识生成对应的敏感数据或者从用户终端获取对应的敏感数据。
考虑到实际应用中会有多种敏感数据索取场景，云存储服务器也可以根据具体索取场景获取敏感数据，例如：(1)当内容索取标识指明索取的敏感数据为用户身份注册数据时，云存储服务器生成登录密码，从云存储 数据库中选取对应用户终端的账号，以及除登录密码和账号之外的注册信息，将账号、登录密码以及除登录密码和账号之外的注册信息作为敏感数据索取清单对应的敏感数据；(2)当内容索取标识指明索取的敏感数据为登录认证数据时，云存储服务器从云存储数据库中查找用户终端对应第三方服务器的标识的账号和登录密码，将该账号和登录密码作为敏感数据索取清单对应的敏感数据；(3)当内容索取标识指明索取的敏感数据为隐私授权数据时，云存储服务器从云存储数据库中查找对应的隐私授权数据，将该隐私授权数据作为敏感数据索取清单对应的敏感数据。
为了增强用户的互动性，上述云存储服务器根据第三方服务器的标识将敏感数据和会话标识发送给第三方服务器的步骤之前，该方法还包括：云存储服务器将获取的敏感数据发送给用户终端，在接收到用户终端返回的确认信息时，执行根据第三方服务器的标识将敏感数据和会话标识发送给第三方服务器的步骤。如果没有接收到用户的确认信息，则向用户终端发送提示信息或采取其它处理方式。
考虑到有时可能需要用户对云存储服务器获取的敏感数据进行更新或修改，云存储服务器根据第三方服务器的标识将敏感数据和会话标识发送给第三方服务器之前，该方法还可以包括：云存储服务器将获取的敏感数据发送给用户终端进行修改；云存储服务器接收用户终端返回的经用户修改的敏感数据，将修改的敏感数据作为最终获取的敏感数据索取清单对应的敏感数据，将修改的敏感数据同步至云存储数据库。
考虑到敏感数据的索取场景有多种情况，本发明实施例在具体实现时，针对不同的索取场景，提供了有针对性的敏感数据获取优化方式：
索取场景一、用户身份注册
(1)当内容索取标识指明敏感数据的索取场景为用户身份注册时，云存储服务器生成登录密码，并从云存储数据库中选取对应用户终端的账号和除登录密码和账号之外的其它注册信息(例如：性别、出生日期、学历、手机号、身份证号等)，将账号、登录密码以及其它注册信息作为与第三方服务器的标识对应的初始敏感数据下发给用户终端；
(2)用户终端向用户展示上述初始敏感数据，等待用户对初始敏感数据进行修改或确认操作；
(3)当接收到用户的修改操作时，用户终端将修改后的敏感数据上传给云存储服务器；云存储服务器接收修改后的敏感数据，并将修改后的敏 感数据作为与第三方服务器的标识和内容索取标识对应的敏感数据，以及将修改后的敏感数据同步至云存储数据库；
(4)当接收到用户的确认操作时，用户终端将上述初始敏感数据作为与第三方服务器的标识和内容索取标识对应的敏感数据，以及将初始敏感数据同步至云存储数据库。
由该方式可知，用户可以对云存储服务器下发的敏感数据进行修改，也可以不修改直接确认，这些关于在第三方服务器上的注册敏感数据将会同步至云存储数据库，在该数据库中，可以对应第三方服务器的标识、用户终端的标识和注册相关的敏感数据进行绑定保存。
索取场景二、身份登录认证
(1)当内容索取标识指明敏感数据的索取场景为用户身份登录认证时，云存储服务器从云存储数据库中选取用户终端对应第三方服务器的标识的账号和登录密码，并将该账号和登录密码发送给用户终端；
(2)用户终端向用户展示账号和登录密码，当接收到用户的确认操作后，向云存储服务器上传用户已确认的通知；
(3)云存储服务器接收上述通知后，将账号和登录密码作为与第三方服务器的标识和内容索取标识对应的敏感数据。
索取场景三、用户隐私信息授权
(1)当内容索取标识指明敏感数据的索取场景为用户隐私信息授权时，云存储服务器从云存储数据库中选取用户终端对应第三方服务器的标识的隐私授权信息，将隐私授权信息发送给用户终端；
(2)用户终端向用户展示隐私授权信息，等待用户对隐私授权信息的修改或确认操作；
(3)当接收到用户的修改操作时，用户终端将修改后的隐私授权信息上传给云存储服务器；云存储服务器接收修改后的隐私授权信息，将修改后的隐私授权信息作为与第三方服务器的标识和内容索取标识对应的敏感数据，以及将修改后的隐私授权信息同步至云存储数据库；
(4)当接收到用户的确认操作时，用户终端将上述隐私授权信息(即云存储服务器在步骤(1)中选取并发送给用户终端的信息)作为与第三方服务器的标识和内容索取标识对应的敏感数据。
参见图3所示的敏感数据的授权方法的示意图，该方法包括以下步骤：
步骤S302，用户访问第三方客户端，进入敏感数据索取场景(如登陆、注册、填写信用卡信息、填写邮寄地址等)。
步骤S304，第三方客户端将敏感数据索取场景通过HTTP或者Socket发送给第三方服务器(相当于向第三方服务器发送敏感数据索取请求)。
步骤S306，第三方服务器检验第三方客户端的合法性(钓鱼网站、山寨网站等)，若第三方客户端不合法则直接终止流程；若合法，则执行步骤S308。
步骤S308，第三方服务器根据上述场景(如索取内容标识)生成敏感数据索取清单，该清单至少包含第三方服务器的识别码(域名、IP地址、AppKey等)、该清单的识别码(相当于上述会话标识，可以是一串随机数，或者一个时间哈希值等)、指明索取场景的元数据(相当于上述索取内容标识)，该元数据可能还包括敏感数据的字段名称、格式要求等。
步骤S310，第三方服务器向第三方客户端发送文本形式或二维码(堆叠式、矩阵式等)形式的敏感数据索取清单。
步骤S312，第三方客户端向用户展示敏感数据索取清单的二维码。具体地，第三方客户端将接收到的二维码(或者接收到文本再转换成二维码)加载到页面中展示给用户。
步骤S314，用户登陆用户个人终端(账号密码登陆、生物信息登陆、手势登陆等)，并扫描解析上述二维码，获得敏感数据索取清单。
步骤S316，用户个人终端向云存储服务器发送敏感数据索取清单。
步骤S318，云存储服务器根据上述清单中的第三方服务器的识别码和元数据获取所需的敏感数据(此时数据可能不完整)；例如通过在云存储数据库中检索所需的敏感数据，如果是用户身份注册的场景，云存储服务器还可以自动生成登录密码，将生成的登录密码添加到敏感数据中。
步骤S320，云存储服务器向用户个人终端发送上述敏感数据；
步骤S322，用户个人终端将敏感数据展示给用户，用户检查数据并作必要的修改或增补(对于网名、座右铭等敏感数据可能会有智能生成缺省数据的流程以减少用户思考的时间)，也可以不修改。
步骤S324，用户检验敏感数据无误后点击确认，用户个人终端将由用户更新并确认过的敏感数据发送给云存储服务器。
步骤S326，云存储服务器将更新的敏感数据(被修改的、增加的)同步到云存储数据库中。
步骤S328，云存储服务器根据上述清单中的识别码检索出第三方服务器的接口地址(Web API、Web Service等)。
步骤S330，云存储服务器通过上述接口地址向第三方服务器发送所需的敏感数据。
步骤S332，第三方服务器接收敏感数据并根据场景检验其业务逻辑(如果是登陆则审核账号信息，如果是注册或表单填写则检查字段是否合法)，检验通过后，对上述敏感数据执行上述场景和业务所需的操作。
步骤S334，第三方服务器将操作结果发送给第三方客户端(只通知第三方客户端一个结果，但不会将敏感数据透漏给第三方客户端)。
步骤S336，第三方客户端接收到第三方服务器的结果后完成敏感数据索取场景的全过程。
上述第三方服务器还可以将检验结果发送给用户个人终端(可能通过云存储服务器转送)。
上述方法中，网站全程未接触到敏感数据，有效防止了像钓鱼网站、键盘记录木马、病毒等隐患对用户敏感数据的截取，用户可以全程不接触键盘(包括虚拟键盘)或仅点触确认键来完成敏感数据的授权，方便快捷，用户不需要记忆敏感数据跟网站的对应关系，只需要管理自己在云存储服务器中的敏感数据即可，同时，云存储服务器作为一个集中式用户敏感数据存储服务器，如果用户终端丢失，用户可以采购新的用户终端，然后从云存储服务器恢复其敏感数据，具有较强的实用性。
对应于上述方法中的第三方服务器，本发明实施例还提供了一种服务器，该服务器对应上述第三方服务器，参见图4所示，该服务器包括以下模块：
请求接收模块41，用于接收来自客户端的敏感数据索取请求，其中，该敏感数据索取请求携带有内容索取标识；该内容索取标识用以指明用户当前的索取场景，例如：索取场景为以下之一：用户身份注册场景、登录认证场景或用户隐私信息授权(如填写信用卡信息或填写邮寄地址等)场景等。
清单生成模块42，用于对上述客户端进行合法性检验通过后，根据上述内容索取标识生成敏感数据索取清单，其中，该敏感数据索取清单包括：该服务器的标识、会话标识和上述内容索取标识；
清单通知模块43，用于将上述敏感数据索取清单通过上述客户端通知给用户终端；
数据接收模块44，用于接收来自云存储服务器的敏感数据和会话标识；其中，该敏感数据为云存储服务器根据上述用户终端上传的敏感数据索取清单获取的；
敏感数据处理模块45，用于根据上述会话标识对上述敏感数据执行相应的操作，并将操作结果发送给上述客户端和/或用户终端。
上述服务器在接收到客户端的敏感数据索取请求后，通过下发敏感数据索取清单的方式，触发用户终端通知云存储服务器将该清单对应的敏感数据发送给该服务器，整个敏感数据的传递过程没有涉及到网站，有效防止了恶意网站或病毒截获敏感数据，同时，敏感数据的传递过程不需要用户过多参与，也不需要用户记忆敏感数据与服务器的对应关系，简化了用户的操作，提升了敏感操作的便利性和安全性。
上述清单通知模块43包括：码型转换与下发单元，用于将敏感数据索取清单转换为对应的码型，通过上述客户端向用户终端展示码型，以使该用户终端解析该码型得到敏感数据索取清单；或者包括：清单文本下发单元，用于将上述敏感数据索取清单以文本形式下发给客户端，触发该客户端将接收到的文本形式的敏感数据索取清单转换为对应的码型展示给用户终端，以使该用户终端解析码型得到敏感数据索取清单；其中，上述码型包括以下之一：二维码、三维码、四维码或条形码等。
上述敏感数据处理模块包括：业务逻辑检验单元，用于根据会话标识检验敏感数据的业务逻辑是否正确；敏感数据处理单元，用于当业务逻辑检验单元的检验结果为正确时，对敏感数据执行会话标识对应的操作。
对应于上述方法中的云存储服务器，本发明实施例还提供了一种云存储服务器，参见图5所示，该云存储服务器包括以下模块：
清单接收模块51，用于接收用户终端上传的敏感数据索取清单，其中，该敏感数据索取清单为第三方服务器根据客户端的敏感数据索取请求中的内容索取标识生成的，通过客户端通知给用户终端的；该敏感数据索取清单包括：第三方服务器的标识、会话标识和内容索取标识；
敏感数据获取模块52，用于根据该敏感数据索取清单获取敏感数据；
数据发送模块53，用于根据第三方服务器的标识将敏感数据和会话标识发送给第三方服务器，以使第三方服务器根据该会话标识对敏感数据执行相应的操作。
本实施例的云服务器在接收到用户终端上传的敏感数据索取清单后，根据清单中携带的内容获取对应的敏感数据，并将该敏感数据发送给第三方服务器，整个敏感数据的传递过程没有涉及到网站，有效防止了恶意网站或病毒截获敏感数据，同时，敏感数据的传递过程不需要用户过多参与，也不需要用户记忆敏感数据与第三方服务器的对应关系，简化了用户的操作，提升了敏感操作的便利性和安全性。
优选地，敏感数据获取模块52包括：敏感数据判断单元，用于根据敏感数据索取清单判断云存储数据库中是否有对应的敏感数据；敏感数据提取单元，用于当敏感数据判断单元的判断结果为有时，从云存储数据库中提取敏感数据；敏感数据获取单元，用于当敏感数据判断单元的判断结果为没有时，根据敏感数据索取清单生成对应的敏感数据或者向用户终端获取敏感数据索取清单对应的敏感数据。
优选地，敏感数据获取模块52包括：注册数据获取单元，用于当内容索取标识指明索取的敏感数据为用户身份注册数据时，生成登录密码，并从云存储数据库中选取对应用户终端的账号，以及除登录密码和账号之外的注册信息，将账号、登录密码以及除登录密码和账号之外的注册信息作为敏感数据索取清单对应的敏感数据；登录认证数据获取单元，用于当内容索取标识指明索取的敏感数据为登录认证数据时，从云存储数据库中查找用户终端对应第三方服务器的标识的账号和登录密码，并将账号和登录密码作为敏感数据索取清单对应的敏感数据；隐私授权数据获取单元，用于当内容索取标识指明索取的敏感数据为隐私授权数据时，从云存储数据库中查找对应的隐私授权数据，并将隐私授权数据作为敏感数据索取清单对应的敏感数据。
本发明实施例中的敏感数据保存在云存储服务器中，用户在交互过程中，需要提供敏感数据时，云存储服务器通过第三方服务器下发的敏感数据索取清单获取对应的敏感数据，并将其提供给第三方服务器，操作简单便捷，且敏感数据的传递过程没有接触到网站，因此安全可靠。
对应于上述方法和服务器，本发明实施例还提供了一种敏感数据的授权系统，参见图6，该系统包括：第三方服务器40和云存储服务器50；其中， 第三方服务器的具体结构可以采用图4所示的服务器结构，云存储服务器50的结构可以参考图5所示的云存储服务器结构。
该系统中的第三方服务器在接收到客户端的敏感数据索取请求后，通过下发敏感数据索取清单的方式，触发用户终端通知云存储服务器将该清单对应的敏感数据发送给该第三方服务器，整个敏感数据的传递过程没有涉及到网站，有效防止了恶意网站或病毒截获敏感数据，同时，敏感数据的传递过程不需要用户过多参与，也不需要用户记忆敏感数据与第三方服务器的对应关系，简化了用户的操作，提升了敏感操作的便利性和安全性。
上述方法和系统中，是通过云存储服务器完成敏感数据传递的，在实际应用中，还可以直接通过用户终端完成敏感数据的传递。基于此，本发明实施例还提供了一种敏感数据的授权方法，参见图7所示的敏感数据的授权方法流程图，该方法以从第三方服务器侧描述为例进行说明，包括以下步骤：
步骤S702，第三方服务器接收来自客户端的敏感数据索取请求，其中，该敏感数据索取请求携带有内容索取标识；
步骤S704，第三方服务器对客户端进行合法性检验通过后，根据内容索取标识生成敏感数据索取清单，其中，该敏感数据索取清单包括：第三方服务器的标识、会话标识和内容索取标识；
步骤S706，第三方服务器将敏感数据索取清单通过客户端通知给用户终端；
步骤S708，第三方服务器接收来自用户终端的敏感数据和会话标识；其中，该敏感数据由用户终端根据敏感数据索取清单从本地数据库或者从云存储服务器获取；
步骤S710，第三方服务器根据会话标识对敏感数据执行相应的操作，将操作结果发送给客户端和/或用户终端。
该方法中各个标识的具体内容与上述实施例中的内容相同，这里不再赘述。
本实施例的方法中，第三方服务器在接收到客户端的敏感数据索取请求后，通过下发敏感数据索取清单的方式，触发用户终端获取该清单对应的敏感数据，并将其发送给第三方服务器，整个敏感数据的传递过程没有涉及到网站，有效防止了恶意网站或病毒截获敏感数据，同时，敏感数据 的传递过程不需要用户过多参与，也不需要用户记忆敏感数据与第三方服务器的对应关系，简化了用户的操作，提升了敏感操作的便利性和安全性。
参见图8所示的敏感数据的授权方法流程图，该方法以从用户终端侧描述为例进行说明，包括以下步骤：
步骤S802，用户终端通过客户端接收第三方服务器通知的敏感数据索取清单，其中，该敏感数据索取清单由第三方服务器根据客户端的敏感数据索取请求中的内容索取标识生成；该敏感数据索取清单包括：第三方服务器的标识、会话标识和内容索取标识；
步骤S804，用户终端根据敏感数据索取清单中的第三方服务器的标识和内容索取标识从本地数据库或者从云存储服务器获取敏感数据；
步骤S806，用户终端根据第三方服务器的标识将敏感数据和会话标识发送给第三方服务器，以使第三方服务器根据会话标识对敏感数据执行相应的操作。
本实施例的方法中，用户终端在接收到第三方服务器通知的敏感数据索取清单后，根据清单中携带的内容获取对应的敏感数据，并将该敏感数据发送给第三方服务器，整个敏感数据的传递过程没有涉及到网站，有效防止了恶意网站或病毒截获敏感数据，同时，敏感数据的传递过程不需要用户过多参与，也不需要用户记忆敏感数据与第三方服务器的对应关系，简化了用户的操作，提升了敏感操作的便利性和安全性。
具体实现时，上述用户终端通过客户端接收第三方服务器通知的敏感数据索取清单可以包括：用户终端通过客户端接收敏感数据索取清单的码型；其中，该码型为第三方服务器或客户端根据敏感数据索取清单生成的，包括以下中的一个：二维码、三维码、四维码或条形码等；用户终端解析该码型得到敏感数据索取清单。
为了增强安全性，用户终端通过客户端接收第三方服务器下发的敏感数据索取清单的码型包括：用户终端接收到用户的开启扫描应用的指示时，验证用户的身份是否合法，如果合法，扫描客户端上展示的码型。用户终端验证用户的身份是否合法，包括以下验证方式之一：(1)用户终端验证用户的生物特征信息是否合法；(2)用户终端验证用户输入的用户名和密码是否合法；(3)用户终端验证用户输入的图形是否合法。通过增设该身份验证步骤，可以有效地防止他人操作合法的用户终端，窃取通信过程中的相关信息。
上述用户终端从云存储服务器获取敏感数据可以包括：用户终端将敏感数据索取清单发送给云存储服务器，以使云存储服务器根据敏感数据索取清单中的第三方服务器的标识和内容索取标识查找敏感数据或者根据敏感数据索取清单中的第三方服务器的标识和内容索取标识生成敏感数据；用户终端接收云存储服务器下发的敏感数据。
对应于上述方法中的第三方服务器，本发明实施例还提供了一种服务器，参见图9，该服务器包括以下模块：
索取请求接收模块91，用于接收来自客户端的敏感数据索取请求，其中，该敏感数据索取请求携带有内容索取标识；
索取清单生成模块92，用于对客户端进行合法性检验通过后，根据内容索取标识生成敏感数据索取清单，其中，该敏感数据索取清单包括：该服务器的标识、会话标识和内容索取标识；
索取清单通知模块93，用于将上述敏感数据索取清单通过客户端通知给用户终端；
数据和标识接收模块94，用于接收来自用户终端的敏感数据和会话标识；其中，该敏感数据由用户终端根据敏感数据索取清单从本地数据库或者从云存储服务器获取；
处理模块95，用于根据上述会话标识对敏感数据执行相应的操作，并将操作结果发送给客户端和/或用户终端。
本实施例的服务器在接收到客户端的敏感数据索取请求后，通过下发敏感数据索取清单的方式，触发用户终端获取该清单对应的敏感数据，并将其发送给该服务器，整个敏感数据的传递过程没有涉及到网站，有效防止了恶意网站或病毒截获敏感数据，同时，敏感数据的传递过程不需要用户过多参与，也不需要用户记忆敏感数据与该服务器的对应关系，简化了用户的操作，提升了敏感操作的便利性和安全性。
对应于上述方法，本发明实施例还提供了一种用户终端，参见图10所示的用户终端的结构框图，该用户终端包括以下模块：
索取清单接收模块12，用于通过客户端接收第三方服务器通知的敏感数据索取清单，其中，该敏感数据索取清单由第三方服务器根据客户端的敏感数据索取请求中的内容索取标识生成；该敏感数据索取清单包括：第三方服务器的标识、会话标识和内容索取标识；
数据获取模块14，用于根据敏感数据索取清单从本地数据库或者从云存储服务器获取敏感数据；
数据和标识发送模块16，用于根据第三方服务器的标识将敏感数据和会话标识发送给第三方服务器，以使第三方服务器根据会话标识对敏感数据执行相应的操作。
本实施例的用户终端在接收到第三方服务器通知的敏感数据索取清单后，根据清单中携带的内容获取对应的敏感数据，并将该敏感数据发送给第三方服务器，整个敏感数据的传递过程没有涉及到网站，有效防止了恶意网站或病毒截获敏感数据，同时，敏感数据的传递过程不需要用户过多参与，也不需要用户记忆敏感数据与第三方服务器的对应关系，简化了用户的操作，提升了敏感操作的便利性和安全性。
该用户终端还可以包括：用户身份验证模块，用于接收到用户的开启扫描指示时，验证用户的身份是否合法；扫描模块，用于当用户身份验证模块验证用户合法时，扫描敏感数据索取清单的码型；解析模块，用于解析该码型得到敏感数据索取清单。用户身份验证模块在验证用户身份时，可以采用上述方法中的具体验证方式，这里不再赘述。
对应于上述方法和装置(服务器和用户终端)本发明实施例还提供了一种敏感数据的授权系统，该系统包括第三方服务器和用户终端，其中，如图11所示的敏感数据的授权系统的结构框图，第三方服务器90可以采用图9所示的服务器结构实现，用户终端100可以采用图10所示的用户终端的结构实现，该系统中第三方服务器和用户终端具有的具体功能同以上实施例类似，这里不再详述。
上述实施例提供的技术可以应用于用户身份注册、登录及其它隐私信息授权等，应用过程中避免了用户通过键盘输入敏感数据的操作，一定程度上改善了被钓鱼攻击的可能性，同时，上述技术还使得登录、注册、个人隐私信息等敏感数据的填写转换为敏感数据的传递，用户不需要学习键盘的输入法即可实现相应的操作，降低了学习成本，便于各类用户使用，提升了用户体验度。
附图中的流程图和框图显示了根据本发明的多个实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段或代码的一部分，所述模块、程序段或代码的一部分包含一个或多个用于实现规定的逻辑功能的 可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个连续的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行规定的功能或动作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
参见图12，本发明实施例还提供一种敏感数据的授权装置120，包括：处理器20，存储器21，总线22和通信接口23，所述处理器20、通信接口23和存储器21通过总线22连接；处理器20用于执行存储器21中存储的可执行模块，例如计算机程序。
其中，存储器21可能包含高速随机存取存储器(RAM：Random Access Memory)，也可能还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。通过至少一个通信接口23(可以是有线或者无线)实现该系统网元与至少一个其他网元之间的通信连接，可以使用互联网，广域网，本地网，城域网等。
总线22可以是ISA总线、PCI总线或EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图12中仅用一个双向箭头表示，但并不表示仅有一根总线或一种类型的总线。
其中，存储器21用于存储程序，所述处理器20在接收到执行指令后，执行所述程序，前述本发明实施例任一实施例揭示的过程定义的装置(服务器、云服务器或用户终端)所执行的方法可以应用于处理器20中，或者由处理器20实现。
处理器20可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器20中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器20可以是通用处理器，包括中央处理器(Central Processing Unit，简称CPU)、网络处理器(Network Processor，简称NP)等；还可以是数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本发明实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完 成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器21，处理器20读取存储器21中的信息，结合其硬件完成上述方法的步骤。
本发明实施例还提供了一种进行敏感数据授权方法的计算机程序产品，包括存储了程序代码的计算机可读存储介质，所述程序代码包括的指令可用于执行前面方法实施例中所述的方法，具体实现可参见方法实施例，在此不再赘述。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所公开的系统、装置和方法，可以通过其它的方式实现。以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，又例如，多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些通信接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only  Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应所述以权利要求的保护范围为准。

Claims (24)

  1. 一种敏感数据的授权方法，其特征在于，包括：
    第三方服务器接收来自客户端的敏感数据索取请求，其中，所述敏感数据索取请求携带有内容索取标识；
    所述第三方服务器对所述客户端进行合法性检验通过后，根据所述内容索取标识生成敏感数据索取清单，其中，所述敏感数据索取清单包括：所述第三方服务器的标识、会话标识和所述内容索取标识；
    所述第三方服务器将所述敏感数据索取清单通过所述客户端通知给用户终端；
    所述第三方服务器接收来自云存储服务器的敏感数据和所述会话标识；其中，所述敏感数据为所述云存储服务器根据所述用户终端上传的所述敏感数据索取清单获取的；
    所述第三方服务器根据所述会话标识对所述敏感数据执行相应的操作，并将操作结果发送给所述客户端和/或所述用户终端。
  2. 根据权利要求1所述的方法，其特征在于，所述第三方服务器将所述敏感数据索取清单通过所述客户端通知给用户终端包括：
    所述第三方服务器将所述敏感数据索取清单转换为对应的码型，通过所述客户端向用户终端展示所述码型，以使所述用户终端解析所述码型得到所述敏感数据索取清单；或者，所述第三方服务器将所述敏感数据索取清单以文本形式下发给所述客户端，触发所述客户端将接收到的所述文本形式的敏感数据索取清单转换为对应的码型展示给用户终端，以使所述用户终端解析所述码型得到所述敏感数据索取清单；
    其中，所述码型包括以下中的一个：二维码、三维码、四维码或条形码。
  3. 根据权利要求1所述的方法，其特征在于，所述第三方服务器根据所述会话标识对所述敏感数据执行相应的操作包括：
    所述第三方服务器根据所述会话标识检验所述敏感数据的业务逻辑是否正确，如果正确，对所述敏感数据执行与所述会话标识对应的操作。
  4. 一种敏感数据的授权方法，其特征在于，包括：
    云存储服务器接收用户终端上传的敏感数据索取清单，其中，所述敏感数据索取清单由第三方服务器根据客户端的敏感数据索取请求中的内容 索取标识生成并且通过所述客户端通知给所述用户终端；所述敏感数据索取清单包括：第三方服务器的标识、会话标识和所述内容索取标识；
    所述云存储服务器根据所述敏感数据索取清单中的第三方服务器的标识和所述内容索取标识获取敏感数据；
    所述云存储服务器根据所述第三方服务器的标识将所述敏感数据和所述会话标识发送给所述第三方服务器，以使所述第三方服务器根据所述会话标识对所述敏感数据执行相应的操作。
  5. 根据权利要求4所述的方法，其特征在于，所述云存储服务器根据所述敏感数据索取清单获取敏感数据包括：
    所述云存储服务器根据所述敏感数据索取清单中的第三方服务器的标识和所述内容索取标识判断云存储数据库中是否有对应的敏感数据，如果有，则从所述云存储数据库中提取所述敏感数据；如果没有，所述云存储服务器根据所述敏感数据索取清单中的第三方服务器的标识和所述内容索取标识生成对应的敏感数据或者从所述用户终端获取对应的敏感数据。
  6. 根据权利要求4所述的方法，其特征在于，所述云存储服务器根据所述敏感数据索取清单获取敏感数据包括：
    当所述内容索取标识指明索取的所述敏感数据为用户身份注册数据时，所述云存储服务器生成登录密码，从云存储数据库中选取对应所述用户终端的账号，以及除所述登录密码和账号之外的注册信息，将所述账号、所述登录密码以及所述除所述登录密码和账号之外的注册信息作为所述敏感数据索取清单对应的敏感数据；
    当所述内容索取标识指明索取的所述敏感数据为登录认证数据时，所述云存储服务器从所述云存储数据库中查找所述用户终端对应所述第三方服务器的标识的账号和登录密码，将所述账号和登录密码作为所述敏感数据索取清单对应的敏感数据；
    当所述内容索取标识指明索取的所述敏感数据为隐私授权数据时，所述云存储服务器从所述云存储数据库中查找对应的隐私授权数据，将所述隐私授权数据作为所述敏感数据索取清单对应的敏感数据。
  7. 根据权利要求5或6所述的方法，其特征在于，所述云存储服务器根据所述第三方服务器的标识将所述敏感数据和所述会话标识发送给所述第三方服务器之前，所述方法还包括：
    所述云存储服务器将获取的所述敏感数据发送给所述用户终端，在接收到所述用户终端返回的确认信息时，执行所述根据所述第三方服务器的标识将所述敏感数据和所述会话标识发送给所述第三方服务器的步骤。
  8. 根据权利要求5或6所述的方法，其特征在于，所述云存储服务器根据所述第三方服务器的标识将所述敏感数据和所述会话标识发送给所述第三方服务器之前，所述方法还包括：
    所述云存储服务器将获取的所述敏感数据发送给所述用户终端进行修改；
    所述云存储服务器接收所述用户终端返回的经用户修改的敏感数据，将所述修改的敏感数据作为最终获取的所述敏感数据索取清单对应的敏感数据，将所述修改的敏感数据同步至所述云存储数据库。
  9. 一种服务器，其特征在于，包括：
    请求接收模块，用于接收来自客户端的敏感数据索取请求，其中，所述敏感数据索取请求携带有内容索取标识；
    清单生成模块，用于对所述客户端进行合法性检验通过后，根据所述内容索取标识生成敏感数据索取清单，其中，所述敏感数据索取清单包括：所述服务器的标识、会话标识和所述内容索取标识；
    清单通知模块，用于将所述敏感数据索取清单通过所述客户端通知给用户终端；
    数据接收模块，用于接收来自云存储服务器的敏感数据和所述会话标识；其中，所述敏感数据为所述云存储服务器根据所述用户终端上传的所述敏感数据索取清单获取的；
    敏感数据处理模块，用于根据所述会话标识对所述敏感数据执行相应的操作，并将操作结果发送给所述客户端和/或所述用户终端。
  10. 根据权利要求9所述的服务器，其特征在于，所述清单通知模块包括：
    码型转换与下发单元，用于将所述敏感数据索取清单转换为对应的码型，通过所述客户端向用户终端展示所述码型，以使所述用户终端解析所述码型得到所述敏感数据索取清单；或者，
    清单文本下发单元，用于将所述敏感数据索取清单以文本形式下发给所述客户端，触发所述客户端将接收到的所述文本形式的敏感数据索取清 单转换为对应的码型展示给用户终端，以使所述用户终端解析所述码型得到所述敏感数据索取清单；
    其中，所述码型包括以下中的一个：二维码、三维码、四维码或条形码。
  11. 根据权利要求9所述的服务器，其特征在于，所述敏感数据处理模块包括：
    业务逻辑检验单元，用于根据所述会话标识检验所述敏感数据的业务逻辑是否正确；
    敏感数据处理单元，用于当所述业务逻辑检验单元的检验结果为正确时，对所述敏感数据执行与所述会话标识对应的操作。
  12. 一种云存储服务器，其特征在于，包括：
    清单接收模块，用于接收用户终端上传的敏感数据索取清单，其中，所述敏感数据索取清单为第三方服务器根据客户端的敏感数据索取请求中的内容索取标识生成的，通过所述客户端通知给所述用户终端的；所述敏感数据索取清单包括：第三方服务器的标识、会话标识和所述内容索取标识；
    敏感数据获取模块，用于根据所述敏感数据索取清单获取敏感数据；
    数据发送模块，用于根据所述第三方服务器的标识将所述敏感数据和所述会话标识发送给所述第三方服务器，以使所述第三方服务器根据所述会话标识对所述敏感数据执行相应的操作。
  13. 根据权利要求12所述的云存储服务器，其特征在于，所述敏感数据获取模块包括：
    敏感数据判断单元，用于根据所述敏感数据索取清单判断云存储数据库中是否有对应的敏感数据；
    敏感数据提取单元，用于当所述敏感数据判断单元的判断结果为有时，从所述云存储数据库中提取所述敏感数据；
    敏感数据获取单元，用于当所述敏感数据判断单元的判断结果为没有时，根据所述敏感数据索取清单生成对应的敏感数据或者向所述用户终端获取所述敏感数据索取清单对应的敏感数据。
  14. 根据权利要求12所述的云存储服务器，其特征在于，所述敏感数据获取模块包括：
    注册数据获取单元，用于当所述内容索取标识指明索取的所述敏感数据为用户身份注册数据时，生成登录密码，并从云存储数据库中选取对应所述用户终端的账号，以及除所述登录密码和账号之外的注册信息，将所述账号、所述登录密码以及所述除所述登录密码和账号之外的注册信息作为所述敏感数据索取清单对应的敏感数据；
    登录认证数据获取单元，用于当所述内容索取标识指明索取的所述敏感数据为登录认证数据时，从云存储数据库中查找所述用户终端对应所述第三方服务器的标识的账号和登录密码，并将所述账号和登录密码作为所述敏感数据索取清单对应的敏感数据；
    隐私授权数据获取单元，用于当所述内容索取标识指明索取的所述敏感数据为隐私授权数据时，从云存储数据库中查找对应的隐私授权数据，并将所述隐私授权数据作为所述敏感数据索取清单对应的敏感数据。
  15. 一种敏感数据的授权系统，其特征在于，包括：第三方服务器和云存储服务器；其中，所述第三方服务器为如权利要求9至11中任一项所述的服务器；所述云存储服务器为如权利要求12至14中任一项所述的云存储服务器。
  16. 一种敏感数据的授权方法，其特征在于，包括：
    第三方服务器接收来自客户端的敏感数据索取请求，其中，所述敏感数据索取请求携带有内容索取标识；
    所述第三方服务器对所述客户端进行合法性检验通过后，根据所述内容索取标识生成敏感数据索取清单，其中，所述敏感数据索取清单包括：所述第三方服务器的标识、会话标识和所述内容索取标识；
    所述第三方服务器将所述敏感数据索取清单通过所述客户端通知给用户终端；
    所述第三方服务器接收来自所述用户终端的敏感数据和所述会话标识；其中，所述敏感数据由所述用户终端根据所述敏感数据索取清单从本地数据库或者从云存储服务器获取；
    所述第三方服务器根据所述会话标识对所述敏感数据执行相应的操作，将操作结果发送给所述客户端和/或所述用户终端。
  17. 一种敏感数据的授权方法，其特征在于，包括：
    用户终端通过客户端接收第三方服务器通知的敏感数据索取清单，其中，所述敏感数据索取清单由第三方服务器根据客户端的敏感数据索取请 求中的内容索取标识生成；所述敏感数据索取清单包括：第三方服务器的标识、会话标识和所述内容索取标识；
    所述用户终端根据所述敏感数据索取清单中的所述第三方服务器的标识和所述内容索取标识从本地数据库或者从云存储服务器获取敏感数据；
    所述用户终端根据所述第三方服务器的标识将所述敏感数据和所述会话标识发送给所述第三方服务器，以使所述第三方服务器根据所述会话标识对所述敏感数据执行相应的操作。
  18. 根据权利要求17所述的方法，其特征在于，所述用户终端通过客户端接收第三方服务器通知的敏感数据索取清单包括：
    所述用户终端通过所述客户端接收敏感数据索取清单的码型；其中，所述码型由第三方服务器或所述客户端根据所述敏感数据索取清单生成，包括以下中的一个：二维码、三维码、四维码或条形码；
    所述用户终端解析所述码型得到所述敏感数据索取清单。
  19. 根据权利要求18所述的方法，其特征在于，所述用户终端通过客户端接收第三方服务器下发的敏感数据索取清单的码型包括：
    所述用户终端接收到用户的开启扫描应用的指示时，验证所述用户的身份是否合法，如果合法，则扫描所述客户端上展示的码型。
  20. 根据权利要求19所述的方法，其特征在于，所述用户终端验证所述用户的身份是否合法，包括以下验证方式之一：
    所述用户终端验证用户的生物特征信息是否合法；
    所述用户终端验证用户输入的用户名和密码是否合法；
    所述用户终端验证用户输入的图形是否合法。
  21. 根据权利要求17所述的方法，其特征在于，所述用户终端从云存储服务器获取敏感数据包括：
    所述用户终端将所述敏感数据索取清单发送给云存储服务器，以使所述云存储服务器根据所述敏感数据索取清单中的所述第三方服务器的标识和所述内容索取标识查找敏感数据或者根据所述敏感数据索取清单中的所述第三方服务器的标识和所述内容索取标识生成敏感数据；
    所述用户终端接收所述云存储服务器下发的敏感数据。
  22. 一种服务器，其特征在于，包括：
    索取请求接收模块，用于接收来自客户端的敏感数据索取请求，其中，所述敏感数据索取请求携带有内容索取标识；
    索取清单生成模块，用于对所述客户端进行合法性检验通过后，根据所述内容索取标识生成敏感数据索取清单，其中，所述敏感数据索取清单包括：所述服务器的标识、会话标识和所述内容索取标识；
    索取清单通知模块，用于将所述敏感数据索取清单通过所述客户端通知给用户终端；
    数据和标识接收模块，用于接收来自所述用户终端的敏感数据和所述会话标识；其中，所述敏感数据为所述用户终端根据所述敏感数据索取清单从本地数据库或者从云存储服务器获取的；
    处理模块，用于根据所述会话标识对所述敏感数据执行相应的操作，并将操作结果发送给所述客户端和/或所述用户终端。
  23. 一种用户终端，其特征在于，包括：
    索取清单接收模块，用于通过客户端接收第三方服务器通知的敏感数据索取清单，其中，所述敏感数据索取清单由第三方服务器根据客户端的敏感数据索取请求中的内容索取标识生成；所述敏感数据索取清单包括：第三方服务器的标识、会话标识和所述内容索取标识；
    数据获取模块，用于根据所述敏感数据索取清单从本地数据库或者从云存储服务器获取敏感数据；
    数据和标识发送模块，用于根据所述第三方服务器的标识将所述敏感数据和所述会话标识发送给所述第三方服务器，以使所述第三方服务器根据所述会话标识对所述敏感数据执行相应的操作。
  24. 一种敏感数据的授权系统，其特征在于，包括第三方服务器和用户终端，其中，所述第三方服务器为如权利要求22所述的服务器，所述用户终端为如权利要求23所述的用户终端。
PCT/CN2014/095384 2014-11-18 2014-12-29 敏感数据的授权方法、装置和系统 WO2016078182A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410659741.0 2014-11-18
CN201410659741.0A CN104468531B (zh) 2014-11-18 2014-11-18 敏感数据的授权方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2016078182A1 true WO2016078182A1 (zh) 2016-05-26

Family

ID=52913903

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/095384 WO2016078182A1 (zh) 2014-11-18 2014-12-29 敏感数据的授权方法、装置和系统

Country Status (2)

Country Link
CN (1) CN104468531B (zh)
WO (1) WO2016078182A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10311245B2 (en) * 2016-03-08 2019-06-04 Kalpesh S. Patel Cyber security system and method for transferring data between servers without a continuous connection
CN111182015A (zh) * 2018-11-12 2020-05-19 北京场景互娱传媒科技有限公司 用户信息的获取及统一方法、装置和电子设备
CN114679317A (zh) * 2019-12-26 2022-06-28 支付宝(杭州)信息技术有限公司 数据查看方法以及装置
CN117390687A (zh) * 2023-12-11 2024-01-12 闪捷信息科技有限公司 敏感数据查询方法、装置、存储介质和电子设备

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105610637A (zh) * 2015-09-24 2016-05-25 百度在线网络技术（北京）有限公司 敏感信息的获取方法及装置
TWI560555B (en) * 2016-02-05 2016-12-01 Synology Inc Cloud service server and method for managing cloud service server
CN106161095B (zh) * 2016-07-15 2020-09-08 北京奇虎科技有限公司 数据泄露的预警方法及装置
CN106330871A (zh) * 2016-08-17 2017-01-11 成都聚美优品科技有限公司 一种敏感数据保护方法
CN107623671B (zh) * 2016-12-05 2020-12-11 上海辉冠信息科技有限公司 一种软件许可服务实现方法
CN108270719A (zh) * 2016-12-30 2018-07-10 广东精点数据科技股份有限公司 一种基于数字签名的数据安全传输方法及装置
CN107196943B (zh) * 2017-05-26 2019-09-20 浙江大学 一种隐私数据在第三方平台的安全展示实现方法
CN107222509A (zh) * 2017-07-17 2017-09-29 郑州云海信息技术有限公司 一种基于云存储的网络Web服务数据保护方法和装置
CN110119632B (zh) * 2018-02-05 2021-01-15 中国移动通信有限公司研究院 敏感数据请求方法、装置、系统和计算机可读存储介质
CN108664802B (zh) * 2018-03-20 2021-10-08 西安烽火软件科技有限公司 一种敏感数据保护的方法和系统
CN108632258B (zh) * 2018-04-16 2020-12-18 新华三信息安全技术有限公司 一种访问报文处理方法及装置
CN108848117A (zh) * 2018-09-14 2018-11-20 南京理工技术转移中心有限公司 一种养殖环境监控系统及其工作方法
CN109186040A (zh) * 2018-09-14 2019-01-11 南京理工技术转移中心有限公司 一种地铁环境远程监控系统及其工作方法
CN112329049A (zh) * 2020-01-23 2021-02-05 北京沃东天骏信息技术有限公司 业务数据管理方法、装置、电子设备和介质
CN112513854B (zh) * 2020-07-08 2023-02-28 华为技术有限公司 一种高精度地图、高精度地图生成方法和使用方法
CN112671786B (zh) * 2020-12-29 2022-06-28 科来网络技术股份有限公司 一种基于第三方认证的安全登陆的系统及方法
CN114222301B (zh) * 2021-12-13 2024-04-12 奇安盘古(上海)信息技术有限公司 诈骗站点处理方法、装置及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120131341A1 (en) * 2010-11-22 2012-05-24 Network Appliance, Inc. Method and system for improving storage security in a cloud computing environment
CN103095720A (zh) * 2013-01-30 2013-05-08 中国科学院自动化研究所 一种基于会话管理服务器的云存储系统的安全管理方法
CN103152330A (zh) * 2013-02-07 2013-06-12 百度在线网络技术（北京）有限公司 登录方法、系统和云端服务器
CN103795690A (zh) * 2012-10-31 2014-05-14 华为技术有限公司 一种云访问控制的方法、代理服务器和系统
CN104113534A (zh) * 2014-07-02 2014-10-22 百度在线网络技术（北京）有限公司 应用程序app的登录系统及方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120131341A1 (en) * 2010-11-22 2012-05-24 Network Appliance, Inc. Method and system for improving storage security in a cloud computing environment
CN103795690A (zh) * 2012-10-31 2014-05-14 华为技术有限公司 一种云访问控制的方法、代理服务器和系统
CN103095720A (zh) * 2013-01-30 2013-05-08 中国科学院自动化研究所 一种基于会话管理服务器的云存储系统的安全管理方法
CN103152330A (zh) * 2013-02-07 2013-06-12 百度在线网络技术（北京）有限公司 登录方法、系统和云端服务器
CN104113534A (zh) * 2014-07-02 2014-10-22 百度在线网络技术（北京）有限公司 应用程序app的登录系统及方法

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10311245B2 (en) * 2016-03-08 2019-06-04 Kalpesh S. Patel Cyber security system and method for transferring data between servers without a continuous connection
CN111182015A (zh) * 2018-11-12 2020-05-19 北京场景互娱传媒科技有限公司 用户信息的获取及统一方法、装置和电子设备
CN114679317A (zh) * 2019-12-26 2022-06-28 支付宝(杭州)信息技术有限公司 数据查看方法以及装置
CN117390687A (zh) * 2023-12-11 2024-01-12 闪捷信息科技有限公司 敏感数据查询方法、装置、存储介质和电子设备
CN117390687B (zh) * 2023-12-11 2024-04-02 闪捷信息科技有限公司 敏感数据查询方法、装置、存储介质和电子设备

Also Published As

Publication number Publication date
CN104468531B (zh) 2017-11-21
CN104468531A (zh) 2015-03-25

Similar Documents

Publication Publication Date Title
WO2016078182A1 (zh) 敏感数据的授权方法、装置和系统
US11854003B2 (en) Signature verification method, apparatus, and system
CN111935094B (zh) 数据库访问方法、装置、系统及计算机可读存储介质
US10904007B2 (en) Authentication device based on biometric information, control server connected to the same, and login method based on biometric information thereof
US20170331634A1 (en) Detecting and preventing man-in-the-middle attacks on an encrypted connection
US9246897B2 (en) Method and system of login authentication
EP3709567B1 (en) Electronic signature authentication system on the basis of biometric information and electronic signature authentication method thereof
TWI587672B (zh) Login authentication method, client, server and system
US20200067705A1 (en) Methods, apparatuses, and computer program products for frictionless electronic signature management
US20150222435A1 (en) Identity generation mechanism
CN107046544B (zh) 一种识别对网站的非法访问请求的方法和装置
US9294479B1 (en) Client-side authentication
JP2018501567A (ja) 装置検証方法及び機器
WO2019095856A1 (zh) 一种网络身份认证方法、系统及其使用的用户代理设备
AU2014262138A1 (en) User authentication
KR20130107188A (ko) 사운드 코드를 이용한 인증 서버 및 인증방법
KR101940310B1 (ko) 웹 사이트 검증 장치 및 그 방법
CN109729045B (zh) 单点登录方法、系统、服务器以及存储介质
CN115941217B (zh) 用于安全通信的方法和其相关产品
CN107645473B (zh) 数据安全保护的方法和装置
CN105933356A (zh) 一种检测客户端dns劫持的方法及装置
JP2008176709A (ja) パスワード管理装置、マルチログインシステム、Ｗｅｂサービスシステム、及びこれらの方法
TW201437840A (zh) 透過檔案比對進行驗證之方法
WO2017006905A1 (ja) 認証システム、認証方法及びプログラム記憶媒体
KR20200139642A (ko) 집단 검증에 기반하는 부분 데이터 검증 방법

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: 14906483

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14906483

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 21/11/2017)