WO2020020008A1

WO2020020008A1 - Authentication method and authentication system

Info

Publication number: WO2020020008A1
Application number: PCT/CN2019/096040
Authority: WO
Inventors: 符爱花; 杨邺
Original assignee: 北京岸思信息科技有限公司
Priority date: 2018-05-17
Filing date: 2019-07-15
Publication date: 2020-01-30
Also published as: CN108900309B; CN108900309A; CN109547503A

Abstract

Disclosed are an authentication method and an authentication system. The method is used for implementing the authentication, requested by an authentication module, by means of an authentication center, the authentication module runs on a client, and the authentication center runs on a server. The method comprises: the authentication center generating an authentication identifier based on one or more authentication factors, wherein the authentication factors are sent to the authentication center by the authentication module or are generated by the authentication center; the authentication center generating a private authentication key based on the authentication identifier, and sending the authentication identifier and the private authentication key to the authentication module; the authentication center and the authentication module performing the operation of complete storage, partial storage, or complete deletion on the authentication identifier according to the content of the authentication identifier; and the authentication module sending an authentication request to the authentication center, and the authentication center verifying the authentication request. On the premise that the usability thereof is not reduced, the authentication method and system in the present invention achieve higher security, and also control the efficiency and costs at a better level.

Description

Authentication method and authentication system

Technical field

The present invention relates to the field of computer technology, and in particular, to an authentication method and an authentication system.

Background technique

In the 1980s, American scholars proposed the concept of PKI (Public Key Facility), which is a universally applicable network security infrastructure. Some American scholars call the infrastructure that provides comprehensive security services, including software, hardware, people, and policies, called PKI. PKI provides security services for various applications through interfaces that extend to the user's locality, including authentication, identity recognition, digital signatures, and encryption. On the one hand, as the infrastructure, PKI is separated from the application system using PKI, so it has the feature of "public"; on the other hand, without PKI application system, PKI itself has no use. It is the characteristics of this infrastructure that greatly improve the efficiency of PKI system design and development, because the design, development, production, and management of PKI systems can be carried out independently without considering the specificity of the application.

In order to solve the problem of difficult management of public keys in the PKI system, in 1984, Israeli scientist Shamir proposed the concept of an identity-based cryptosystem. In an identity-based system, each entity has an identity. The ID can be any meaningful string. But the biggest difference from the traditional public key system is that in the identity-based system, the identity of the entity itself is the entity's public key. Since the identity itself is the entity's public key, such systems no longer rely on certificates and certificate management systems such as PKI, which greatly simplifies the complexity of managing cryptographic systems. While proposing the concept of IBC, Shamir proposed an identity-based signature algorithm (IBS) based on large number decomposition.

Identity-Based Cryptography (IBC) is a new type of asymmetric cryptography. Its feature is that the user's public key is naturally related to the user's identity, and no additional mechanism (such as a digital certificate) is needed to check this.

The IBC system uses an authority—the private key generator (PKG). PKG is mainly responsible for the following two steps:

initialization:

(IBC_Master_Key, IBC_Common_Para) = IBC_Setup ();

The initialization phase generates a master key (IBC_Master_Key) and a set of public parameters (IBC_Common_Para). The master key is kept by the administrator, cannot be leaked, and public parameters are made public.

Private key generation:

Private_KeyID = IBC_PKG (IBC_Master_Key, ID, IBC_Common_Para);

The administrator operates PKG, enters IBC_Master_Key and ID (signature party identification information) and IBC_Common_Para, and generates a private key (Private_KeyID) for the user. Then, this private key is sent to the corresponding signing party through credible and confidential means.

After the signing party obtains the private key, they can digitally sign:

IBC_Signature = IBC_Sign (Message, Private_KeyID, IBC_Common_Para);

The signing party can directly use the signer's ID for signing:

Result = IBC_Verify (Message, IBC_Signature, ID, IBC_Common_Para);

The existing authentication methods usually have the following three implementation methods:

(1) The password method requires a database to store the password, which is not only costly, but also has a high risk of database leakage. Database breaches have led to widespread password breaches. Even in the form of a password hash value, there is still a risk of being attacked by a dictionary after the leak. And this way is difficult to bind the device or client.

(2) The challenge-response method still requires a database to store the authentication key, so the risks of high cost and easy leakage of confidential information still exist. And because the authentication key needs to be stored on the client, when the device falls into the hands of the attacker, the attacker can be unblocked.

(3) The certificate-based digital signature method does not require a database to store user-related keys, but requires PKI support. This is a high-cost facility in itself, and it often requires verification of the certificate chain, which greatly reduces efficiency. The authentication private key needs to be stored on the client. When the device falls into the hands of the attacker, the attacker can be unblocked.

Assume an attacker has the following five capabilities:

1. The attacker has the ability to steal any data from the database of a general server (such as a normal server), but the attacker cannot steal any data from a high-security server (such as a CA). Because authentication is a high-frequency operation, both the authentication operation itself and the storage of authentication-related data can only be performed by the general server.

2. After obtaining the client device, the attacker has the ability to obtain any data stored in it.

3. The attacker has the ability to eavesdrop on all communications on non-secure channels (such as the HTTP protocol without SSL), but cannot eavesdrop on communications on secure channels (such as the HTTP protocol using SSL, cellular mobile communications, etc.)

4. The attacker has the ability to imitate the client device to communicate with the server.

5. The attacker has the ability to obtain the details of the authentication scheme.

Based on the attacker's assumption above, none of the three aforementioned authentication methods can be resisted.

Most of the existing authentication schemes rely on a database to implement. The specific approach is summarized as follows:

1. The server stores several authentication factors or related information for authentication to the server's database;

2. During authentication, the server fetches some or all of the authentication factors or related information from the database, and then directly or indirectly compares the authentication factors or related information sent by the client. Necessary conditions. The server can also retrieve some authentication factors or related information from the database, and determine whether it is valid according to some current environmental information. The judgment result is valid is a necessary condition for authentication to pass.

E.g:

1. The server stores the device information of the client, the hash value of the password, and the expiration time into the database as authentication factors.

2. During authentication, the client sends device information and password to the client. The verification steps are as follows:

2.1. The server retrieves the corresponding device information from the database and compares it with the device information sent by the client. (Direct comparison)

2.2 The server retrieves the corresponding hash value of the password from the database, calculates the hash value of the password sent by the client, and compares the two. (Indirect comparison)

2.3. The server retrieves the corresponding expiration time from the database, and determines whether the current time (environmental information) is less than the aging time. If it is less than the effective time, it is invalid. (Environmental information judgment)

2.4. Determine whether the authentication is passed based on the verification results of 2.1 to 2.3 above. If and only if the comparison results of 2.1 and 2.2 are consistent, and the judgment result of 2.3 is valid, the authentication is passed.

The problems with the above database-based authentication method are: the cost of database establishment, operation, management, and maintenance is high, and the use method is cumbersome. Database security is low and vulnerable to various attacks.

Document [1] (CN101964039B: a method and system for the protection and protection of copyright objects), document [2] (CN102523563B: an MMS encryption method based on identification password technology), document [3] (CN102970144B: identity-based Authentication method), document [4] (CN103326853A, a method and device for key update) and document [5] (CN104065487A: a digital fingerprint random secret value IBC identity authentication method) all provide an authentication method , But none of them can solve the above technical problems.

Summary of the Invention

The purpose of the present invention is to overcome the above-mentioned shortcomings of the prior art by applying the IBC system to authentication, thereby providing an authentication method and an authentication system that can improve the security and reliability of the authentication process.

In order to achieve the above object, the present invention proposes an authentication method for implementing authentication requested by an authentication center to an authentication module, where the authentication module runs on a client, and the authentication center runs on a server, It is characterized in that the method includes:

The authentication center generates an authentication identifier based on one or more authentication factors, and the authentication factor is sent to the authentication center by the authentication module or is generated by the authentication center;

The authentication center generates an authentication private key based on the authentication identifier, and sends the authentication identifier and the authentication private key to the authentication module;

The authentication center and the authentication module perform all operations of storing, partially storing, or deleting the authentication identifier according to the content of the authentication identifier;

The authentication module sends an authentication request to the authentication center, and the authentication center verifies the authentication request.

As an improvement to the above method, the initialization step of the authentication center and the authentication module: The IBC initialization unit of the authentication center establishes a PKG of the IBC algorithm based on the selected IBC algorithm, and uses the PKG to generate a set of master keys and A set of public parameters. The second storage unit of the authentication center stores the master key generated by the IBC initialization unit; the IBC load unit of the authentication module loads the set of public parameters.

As an improvement of the above method, the client device hardware information, password, expiration time, account name, or client tag.

As an improvement of the above method, the method specifically includes:

Step A1) The authentication module initiates a private key and authentication ID generation request to an authentication center, and sends client device hardware information to the authentication center; the authentication ID generation unit of the authentication center generates a client device Hardware information authentication identifier, and the authentication private key generation unit of the authentication center generates the authentication private key according to the authentication identifier;

Step A2) The authentication center sends an authentication identifier and an authentication private key to the authentication module, and the authentication center deletes the authentication identifier and the authentication private key. After the authentication module receives the authentication module, the authentication module deletes Client device hardware information in the authentication identifier, and the first storage unit of the authentication module stores the authentication identifier and the authentication private key;

Step A3) The authentication request unit of the authentication module sends an authentication request to the authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.

As an improvement of the above method, the step A3) specifically includes:

Step A3-1) The authentication request unit of the authentication module sends an authentication request to the authentication center;

Step A3-2) The authentication verification unit of the authentication center sends a challenge to the authentication module; the challenge is a random number or specific information;

Step A3-3) The authentication module obtains the hardware information of the device and assembles a complete authentication identification; the authentication private key is used to sign the challenge using the IBC signature algorithm to obtain the challenge digital signature, and then the authentication identification and digital signature are sent To the authentication center;

Step A3-4) The authentication verification unit of the authentication center uses the authentication identifier as the ID to verify the digital signature using the IBC signature verification algorithm; obtain the authentication result;

Step A3-5) The authentication verification unit of the authentication center sends the authentication result to the authentication module.

As an improvement of the above method, when the authentication center sets a device lock list, the step A3-4) further includes: judging whether the device hardware information in the authentication identifier is in the device lock list, and if the determination result is positive , The inspection fails, otherwise, the inspection passes.

As an improvement of the above method, the step A3) specifically includes:

Step A3-1 ′) The authentication module obtains client device hardware information and assembles a complete authentication identifier; the authentication request unit of the authentication module generates a challenge, and the challenge is performed using the IBC signature algorithm using the authentication private key Sign, get a digital signature, and then send the authentication ID, challenge, and digital signature to the authentication center;

Step A3-2 ′) The authentication verification unit of the authentication center uses the authentication identifier as the ID to verify the digital signature using the IBC signature verification algorithm; obtains the authentication result;

Step A3-3 ′) The first authentication verification unit of the authentication center sends the authentication result to the authentication module.

As an improvement of the above method, the method specifically includes:

Step B1) The authentication module initiates a private key and authentication ID generation request to the authentication center, and the authentication module sends a password to the authentication center; the authentication ID generation unit of the authentication center generates a password including the password. An authentication identifier, and an authentication private key generating unit of an authentication center generates an authentication private key according to the authentication identifier;

Step B2) The authentication center sends the authentication identifier and the authentication private key to the authentication module, and the authentication center deletes the authentication identifier and the authentication private key. After receiving the authentication module, the authentication module deletes The password in the authentication ID, and the first storage unit of the authentication module stores the authentication ID and the authentication private key;

Step B3) The authentication request unit of the authentication module sends an authentication request to the authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.

As an improvement of the above method, the method specifically includes:

Step C1) The account generation unit of the authentication module generates an account name, the authentication module initiates a private key and authentication ID generation request to the authentication center, and sends the account name to the authentication center;

Step C2) The authentication identifier generation unit of the authentication center generates an authentication identifier including an account name, and the authentication private key generation unit of the authentication center generates an authentication private key according to the authentication identifier;

Step C3) The authentication center sends the authentication identifier and the authentication private key to the authentication module, and the authentication center deletes the authentication identifier and the authentication private key; after the authentication module receives the authentication module, The first storage unit stores an authentication identifier and an authentication private key;

Step C4) The authentication request unit of the authentication module sends an authentication request to the authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.

As an improvement of the above method, the method specifically includes:

Step D1) The authentication module initiates a request for generating a private key and an authentication identifier to the authentication center, and the authentication module sends a client tag to the authentication center; the generation of the authentication identifier generating unit of the authentication center includes An authentication identifier of a client label, and an authentication private key generating unit of the authentication center generates an authentication private key according to the authentication identifier;

Step D2) The authentication center sends the authentication identifier and the authentication private key to the authentication module, and the authentication center deletes the authentication identifier and the authentication private key. After the authentication module receives the authentication module, The first storage unit stores an authentication identifier and an authentication private key;

Step D3) The authentication request unit of the authentication module sends an authentication request to an authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.

As an improvement of the above method, the step D3) specifically includes:

Step D3-1) The authentication request unit of the authentication module sends an authentication request to the authentication center;

Step D3-2) The authentication verification unit of the authentication center sends a challenge to the authentication module; the challenge is a random number or specific information;

Step D3-3) The authentication module obtains the authentication ID from the first storage unit; uses the authentication private key to sign the challenge using the IBC signature algorithm to obtain the digital signature of the challenge, and then sends the authentication ID and digital signature to the authentication center;

Step D3-4) The authentication verification unit of the authentication center uses the authentication identifier as the ID to verify the digital signature using the IBC signature verification algorithm; obtains the authentication result;

Step D3-5) The authentication verification unit of the authentication center sends the authentication result to the authentication module.

As an improvement of the above method, when the authentication center sets a client lock list, the step D3-4) further includes: judging whether the client tag in the authentication identifier is in the client lock list, and if the judgment result is positive If yes, the inspection fails, otherwise, the inspection passes.

As an improvement of the above method, the method specifically includes:

Step E1) The authentication identifier generation unit of the authentication center generates an authentication identifier including a time of expiration, and the authentication private key generation unit of the authentication center generates an authentication private key according to the authentication identifier;

Step E2) The authentication center sends an authentication identifier and an authentication private key to the authentication module, and the authentication center deletes the authentication identifier and the authentication private key. After the authentication module receives the authentication module, The first storage unit stores an authentication identifier and an authentication private key;

Step E3) The authentication request unit of the authentication module sends an authentication request to the authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.

As an improvement of the above method, the step E3) specifically includes:

Step E3-1) The authentication request unit of the authentication module sends an authentication request to the authentication center;

Step E3-2) The authentication verification unit of the authentication center sends a challenge to the authentication module; the challenge is a random number or specific information;

Step E3-3) The authentication module obtains the authentication ID from the first storage unit; uses the authentication private key to sign the challenge using the IBC signature algorithm to obtain the digital signature of the challenge, and then sends the authentication ID and digital signature to the authentication center;

Step E3-4) The authentication verification unit of the authentication center uses the authentication identifier as the ID to verify the digital signature using the IBC sign verification algorithm; obtain the authentication result;

Step E3-5) The authentication verification unit of the authentication center sends the authentication result to the authentication module.

As an improvement of the above method, the step E3-4) further includes: judging whether the current time is less than the expiration time in the authentication identifier, and if the judgment result is positive, the verification is passed; otherwise, the verification is not passed.

As an improvement of the above method, when the authentication factor includes client device hardware information and a password, the method specifically includes:

Step F1) The authentication module initiates a private key and authentication ID generation request to the authentication center, and sends the client device hardware information and password to the authentication center; the authentication ID generation unit of the authentication center includes the client End device hardware information and password authentication ID, and the authentication private key generation unit of the authentication center generates the authentication private key according to the authentication ID;

Step F2) The authentication center sends the authentication identifier and the authentication private key to the authentication module, and the authentication center deletes the authentication identifier; after the authentication module receives, the authentication module deletes the authentication identifier In the password, the first storage unit of the authentication module stores an authentication identifier and an authentication private key;

Step F3) The authentication request unit of the authentication module sends an authentication request to the authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.

As an improvement of the above method, when the authentication factor includes client device hardware information, password, and account name, the method specifically includes:

Step G1) The account generating unit of the authentication module generates an account name, and sends the account name to the authentication center; and stores the account name in a storage unit of the authentication center;

Step G2) The authentication module initiates a private key and authentication ID generation request to the authentication center, and sends the client device hardware information and password to the authentication center; the generation of the authentication ID generation unit of the authentication center includes at least The authentication ID of the account name, client device hardware information, and password, and the authentication private key generation unit of the authentication center generates the authentication private key according to the authentication ID;

Step G3) The authentication center sends an authentication identifier and an authentication private key to the authentication module, and the authentication center deletes the authentication identifier; after the authentication module receives, the authentication module deletes the authentication identifier In the password, the first storage unit of the authentication module stores an authentication identifier and an authentication private key;

Step G4) The authentication request unit of the authentication module sends an authentication request to the authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.

As an improvement of the above method, the step G2) specifically includes:

Step G2-1) The authentication module initiates a private key and authentication identifier generation request to the authentication center, and the authentication module sends the client device hardware information and password to the authentication center;

Step G2-2) The authentication center generates an authentication identifier for the authentication module; the authentication identifier consists of at least an account name, client device hardware information, and a password;

Step G2-3) The authentication center uses the authentication ID as the ID, and uses the PKG generated in the initialization step to generate the authentication private key through the master key.

As an improvement of the above method, when the authentication factor includes client device hardware information, password, client label, and expiration time, the method specifically includes:

Step H1) The authentication module initiates a private key and authentication ID generation request to the authentication center, and sends the client device hardware information, password, and client label to the authentication center; the authentication ID generation of the authentication center The unit generates an authentication identifier including account name, client device hardware information, password, client label, and expiration time, and the authentication private key generation unit of the authentication center generates an authentication private key according to the authentication identifier;

Step H2) The authentication center sends an authentication identifier and an authentication private key to the authentication module, and the authentication center deletes the authentication identifier; after receiving the authentication module, the authentication module deletes the authentication identifier The password and the client device hardware information, the first storage unit of the authentication module stores the authentication identifier and the authentication private key;

Step H3) The authentication request unit of the authentication module sends an authentication request to the authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.

As an improvement of the above method, when the authentication factor includes client device hardware information, password, account name, client label, and expiration time, the method specifically includes:

Step R1) The account generating unit of the authentication module generates an account name, and sends the account name to the authentication center; and stores the account name in a storage unit of the authentication center;

Step R2) The authentication module initiates a private key and authentication ID generation request to the authentication center, and sends client device hardware information, password, and client label to the authentication center; the authentication ID generation of the authentication center The unit generates an authentication identifier including account name, client device hardware information, password, client label, and expiration time, and the authentication private key generation unit of the authentication center generates an authentication private key according to the authentication identifier;

Step R3) The authentication center sends the authentication identifier and the authentication private key to the authentication module, and the authentication center deletes the authentication identifier; after receiving the authentication module, the authentication module deletes the authentication identifier The password and the client device hardware information, the first storage unit of the authentication module stores the authentication identifier and the authentication private key;

Step R4) The authentication request unit of the authentication module sends an authentication request to the authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.

As an improvement of the above method, when the authentication center saves the device information list, the method further includes the step of reporting the loss:

Step S1) The user authenticates the identity of the user through the new device using the second authentication method or other identity authentication means;

Step S2) The authentication center verifies the identity of the user. After the authentication is passed, the authentication center displays the device information list to the user;

Step S3) The user selects a device to be reported from the device information list, and informs the authentication center;

Step S4) The authentication center stores the corresponding device hardware information in the device lock list, and the storage period is permanent or expiration date.

As an improvement of the above method, when the authentication center stores device hardware information, the method further includes the step of reporting the loss:

Step S1 ′) The user authenticates the user identity through the new device using the second authentication mode or other identity authentication means;

Step S2 ′) The authentication center verifies the identity of the user. After the authentication is passed, the authentication center deletes all the device hardware information and client tags corresponding to the user account in the database;

Step S3 ′) All device bindings of the account have been invalidated, and all devices perform the device binding process again.

As an improvement of the above method, after the step of reporting the loss is performed, when the time has expired, the device will automatically report the loss; when the client tag list is set in the authentication center, the method also will It further includes the steps of lifting the loss report:

Step T1)) The user uses the new device to use the second authentication method or other identity authentication means to authenticate the user's identity;

Step T2) The authentication center verifies the identity of the user. After the authentication is passed, the authentication center displays the device lock list to the user;

Step T3) The user selects a device from the device lock list to report loss, and informs the authentication center;

Step T4) The authentication center puts the corresponding device hardware information and client label in the client lock list, the storage period is permanent or expiration date, and simultaneously deletes the corresponding device hardware information from the device lock list;

Step T5) The device to be reported is completely deleted from the original client label, then a new client label is generated, and then the device binding is performed again.

In addition, the present invention also provides an authentication system, the system includes: an authentication module and an authentication center; the authentication module runs on a client, and the authentication center runs on a server;

The authentication center is configured to generate an authentication identifier based on one or more authentication factors, and the authentication factor is sent to the authentication center by the authentication module or is generated by the authentication center; and is further used based on the authentication identifier. Generate an authentication private key, and send the authentication ID and the authentication private key to the authentication module; it is also used to perform all operations of storing, partially storing, or deleting the authentication ID based on the content of the authentication ID; Verifying the authentication request sent by the authentication module;

The authentication module is configured to perform all operations of storing, partially storing, or deleting the authentication identifier according to the content of the authentication identifier, and is further configured to send an authentication request to the authentication center.

As an improvement of the above system, the authentication module includes: an IBC load unit, an account generation unit, a private key request unit, a first storage unit, and an authentication request unit;

The IBC loading unit is used to load the public parameters disclosed by the authentication center;

The account generating unit is configured to generate an account name of an authentication module;

The first storage unit is configured to store an authentication identifier and / or an authentication private key;

The private key requesting unit is configured to send an authentication factor to an authentication center;

The authentication request unit is configured to send an authentication request to an authentication center, and is also used to receive an authentication result sent by the authentication center.

As an improvement of the above system, the authentication center includes: an IBC initialization unit, an authentication identifier generation unit, an authentication private key generation unit, a second storage unit, and an authentication verification unit;

The IBC initialization unit is used to select an IBC algorithm and establish a private key generator PKG for the algorithm, use the PKG for initialization, generate a set of master keys and public parameters, and publicize the public parameters;

The authentication identifier generating unit is configured to generate an authentication identifier according to an authentication factor sent by an authentication module;

The authentication private key generation unit is configured to generate an authentication private key by using the authentication identifier as an ID and the PKG and the master key generated by the IBC initialization unit; and then send the authentication identifier and the authentication private key to the authentication module. ;

The second storage unit is configured to store a master key generated by an IBC initialization unit;

The authentication verification unit is configured to receive an authentication request from an authentication module, use an authentication identifier as an ID to verify a digital signature using an IBC signature verification algorithm, and send an authentication result to the authentication module.

The advantages of the present invention are:

1. The use of open authentication identification improves the flexibility and scalability of the authentication method.

2. In the authentication method of the present invention, neither the client nor the server saves the password, and only the user knows the password, thereby avoiding the security problem caused by theft of the password;

3. On the premise that ease of use is not reduced, the authentication method and system of the present invention achieve higher security, and at the same time, efficiency and cost are controlled at a better level;

4. The authentication method of the present invention not only solves the disadvantages of database-based authentication, but also solves the disadvantages of using PKI system for authentication.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flowchart of an authentication method according to Embodiment 1 of the present invention; FIG.

2 is a flowchart of an authentication method provided by Application Example 1 of the present invention;

3 is a flowchart of an authentication method provided by Application Example 2 of the present invention;

4 is a schematic diagram of an authentication system provided by Application Example 3 of the present invention;

5 is a schematic diagram of an authentication module in an authentication system provided by Application Example 3 of the present invention;

6 is a schematic diagram of an authentication center in an authentication system provided by Application Example 3 of the present invention;

7 is a schematic diagram of an authentication system provided by Application Example 4 of the present invention;

8 is a schematic diagram of an IoT device in an authentication system provided by Application Example 4 of the present invention;

FIG. 9 is a schematic diagram of an IoT platform in an authentication system provided by Application Example 4 of the present invention.

detailed description

To enable those skilled in the art to better understand the technical solution of the present invention, an authentication method and an authentication system provided by the present invention are described in detail below with reference to the accompanying drawings and specific embodiments.

The following "authentication module" refers to: the party that needs to be authenticated, such as the client during a mailbox login operation.

The following "authentication center" refers to: the party that authenticates the authentication module, such as the server during mailbox login operations.

The following "second authentication method" refers to: other methods that the authentication center can use to authenticate the authentication module, such as a short message verification code.

Embodiment 1: General authentication process (as shown in Figure 1):

1. System establishment:

The authentication center selects an IBC algorithm and establishes a private key generator PKG for the algorithm. Use PKG for initialization to generate a set of IBC_Master_Key and IBC_Common_Para. The IBC_Common_Para is made public, and the authentication module is loaded into the IBC_Common_Para. The IBC_Master_Key should be stored in the high-security server and cannot be leaked. The PKG also runs on the high-security server. Operations that do not involve IBC_Master_Key and PKG can be completed using a general server.

The initialization phase of PKG:

(IBC_Master_Key, IBC_Common_Para) = IBC_Setup ();

All connections between the server and client related to authentication should always be based on a secure channel (such as a channel encrypted using the SS1 protocol), and the client has the ability to authenticate the server, such as using the SSL protocol.

2. Private key and authentication identification generation:

The authentication module initiates a private key generation request.

The authentication center generates an authentication token Token, and uses the Token as the ID, uses PKG to generate the authentication private key Token_Private_Key through the master keys IBC_Master_Key and IBC_Common_Para, and then uses trusted and confidential means (such as using the SSL protocol) to exchange Token_Private_Key and Token Send to the corresponding authentication module.

Token_Private_Key = IBC_PKG (IBC_Master_Key, Token, IBC_Common_Para);

3. Handling of private key and authentication ID:

The authentication center completely deletes the private key, and the authentication module completely stores the private key.

The authentication center and the authentication module perform operations of storing, partially storing, or deleting the authentication ID in accordance with the content of the authentication ID.

4. Authentication:

The authentication module sends an authentication request to the authentication center.

The authentication center sends a Challenge to the authentication module, or the authentication module generates a challenge on its own. The challenge is a random number or other specific information.

The authentication module uses the complete authentication ID (if the stored authentication ID is incomplete, it will be restored by the corresponding method), and uses the authentication private key Token_Private_Key to sign the challenge Challenge using the IBC signature algorithm to obtain Digitally sign Challenge_Sign, and then send Challenge (if Challenge is generated by the authentication module itself), Token, and Challenge_Sign to the authentication center;

Challenge_Sign = IBC_Sign (Challenge, Token_Private_Key, IBC_Common_Para);

The authentication center uses the authentication token Token as the ID to verify the Challenge_Sign using the IBC signature verification algorithm; obtains the authentication result;

The signing party can directly use the signing party's authentication ID Token as the ID for signing:

Result = IBC_Verify (Challenge, Challenge_Sign, ID, IBC_Common_Para);

One of the necessary conditions for authentication is to pass the verification check. Other necessary conditions depend on the content of the authentication mark.

The authentication center sends the authentication result to the authentication module.

Embodiment 2: Authentication process (device information):

1. System establishment:

The initialization phase of PKG:

(IBC_Master_Key, IBC_Common_Para) = IBC_Setup ();

2. Private key and authentication identification generation:

The authentication module initiates a private key generation request, and the private key generation request includes the current device information of the authentication module.

The authentication center generates an authentication token Token, which contains 1 authentication factor: device information (from the private key generation request). The authentication center uses Token as the ID, and uses PKG to generate the authentication private key Token_Private_Key through the master keys IBC_Master_Key and IBC_Common_Para, and then sends the Token_Private_Key and Token to the corresponding authentication module through trusted and confidential means (such as using the SSL protocol). in.

Token_Private_Key = IBC_PKG (IBC_Master_Key, Token, IBC_Common_Para);

3. Handling of private key and authentication ID:

The authentication center completely deletes the entire token.

The authentication module completely deletes the device information in the token.

4. Authentication:

The authentication module obtains the current device information in real time, thereby assembling a complete authentication identification. The authentication module uses a complete authentication identifier, uses the authentication private key Token_Private_Key to sign the challenge Challenge using the IBC signature algorithm, obtains the digital signature Challenge_Sign, and then challenges (if Challenge is generated by the authentication module itself), Token and Challenge_Sign is sent to the authentication center;

Challenge_Sign = IBC_Sign (Challenge, Token_Private_Key, IBC_Common_Para);

Result = IBC_Verify (Challenge, Challenge_Sign, ID, IBC_Common_Para);

One of the necessary conditions for passing the verification is to pass the inspection. If a device lock list exists in the authentication center, the necessary conditions for authentication to pass are: the device information in the token is not in the device lock list.

Embodiment 3: Authentication process (password):

1. System establishment:

The initialization phase of PKG:

(IBC_Master_Key, IBC_Common_Para) = IBC_Setup ();

2. Private key and authentication identification generation:

The authentication module initiates a private key generation request, and the private key generation request includes a password.

The authentication center generates an authentication token Token, which contains an authentication factor: a password (from a private key generation request). The authentication center uses Token as the ID, uses PKG to generate the authentication private key Token_Private_Key through the master keys IBC_Master_Key and IBC_Common_Para, and then sends the Token_Private_Key and Token to the corresponding authentication module through trusted and confidential means (such as using the SSL protocol) in.

Token_Private_Key = IBC_PKG (IBC_Master_Key, Token, IBC_Common_Para);

3. Handling of private key and authentication ID:

The authentication center completely deletes the token.

The authentication module completely deletes the password in the Token (account-based application scenario) or stores the entire Token (device-based application scenario).

4. Authentication:

The authentication module obtains the password entered by the user in real time, thereby assembling a complete authentication identifier (account-based application scenario), or directly obtaining a stored authentication identifier (device-based application scenario). The authentication module uses a complete authentication identifier, uses the authentication private key Token_Private_Key to sign the challenge Challenge using the IBC signature algorithm, obtains the digital signature Challenge_Sign, and then challenges (if Challenge is generated by the authentication module itself), Token and Challenge_Sign is sent to the authentication center;

Challenge_Sign = IBC_Sign (Challenge, Token_Private_Key, IBC_Common_Para);

Result = IBC_Verify (Challenge, Challenge_Sign, ID, IBC_Common_Para);

One of the necessary conditions for passing the verification is to pass the inspection. No other necessary conditions.

Embodiment 4: Authentication process (time to failure):

1. System establishment:

The initialization phase of PKG:

(IBC_Master_Key, IBC_Common_Para) = IBC_Setup ();

2. Private key and authentication identification generation:

The authentication module initiates a private key generation request.

The authentication center generates an authentication token Token, which contains 1 authentication factor: the expiration time (set by the authentication center). The authentication center uses Token as the ID, uses PKG to generate the authentication private key Token_Private_Key through the master keys IBC_Master_Key and IBC_Common_Para, and then sends the Token_Private_Key and Token to the corresponding authentication module through trusted and confidential means (such as using the SSL protocol) in.

Token_Private_Key = IBC_PKG (IBC_Master_Key, Token, IBC_Common_Para);

3. Handling of private key and authentication ID:

The authentication center completely deletes the token.

The authentication module stores the entire token.

4. Authentication:

The authentication module directly obtains the stored authentication identifier. The authentication module uses a complete authentication identifier, uses the authentication private key Token_Private_Key to sign the challenge Challenge using the IBC signature algorithm, obtains the digital signature Challenge_Sign, and then challenges (if Challenge is generated by the authentication module itself), Token and Challenge_Sign is sent to the authentication center;

Challenge_Sign = IBC_Sign (Challenge, Token_Private_Key, IBC_Common_Para);

Result = IBC_Verify (Challenge, Challenge_Sign, ID, IBC_Common_Para);

One of the necessary conditions for passing the verification is to pass the inspection. Another necessary condition is that the current time is not greater than the expiration time in the authentication identification.

Embodiment 5: Authentication process (account name):

1. System establishment:

The initialization phase of PKG:

(IBC_Master_Key, IBC_Common_Para) = IBC_Setup ();

2. Private key and authentication identification generation:

The authentication module initiates a private key generation request, and the private key generation request includes an account name.

The authentication center generates an authentication token Token, which contains 1 authentication factor: the account name (from the private key generation request). The authentication center uses Token as the ID, uses PKG to generate the authentication private key Token_Private_Key through the master keys IBC_Master_Key and IBC_Common_Para, and then sends the Token_Private_Key and Token to the corresponding authentication module through trusted and confidential means (such as using the SSL protocol) in.

Token_Private_Key = IBC_PKG (IBC_Master_Key, Token, IBC_Common_Para);

3. Handling of private key and authentication ID:

The authentication center completely deletes the token.

The authentication module stores the entire token.

4. Authentication:

Challenge_Sign = IBC_Sign (Challenge, Token_Private_Key, IBC_Common_Para);

Result = IBC_Verify (Challenge, Challenge_Sign, ID, IBC_Common_Para);

Embodiment 6: Authentication process (client tag):

1. System establishment:

The initialization phase of PKG:

(IBC_Master_Key, IBC_Common_Para) = IBC_Setup ();

2. Private key and authentication identification generation:

The authentication module initiates a private key generation request, and the private key generation request includes a client label.

The authentication center generates an authentication token Token, which contains an authentication factor: the client label (from the private key generation request). The authentication center uses Token as the ID, uses PKG to generate the authentication private key Token_Private_Key through the master keys IBC_Master_Key and IBC_Common_Para, and then sends the Token_Private_Key and Token to the corresponding authentication module through trusted and confidential means (such as using the SSL protocol) in.

Token_Private_Key = IBC_PKG (IBC_Master_Key, Token, IBC_Common_Para);

3. Handling of private key and authentication ID:

The authentication center completely deletes the token.

The authentication module stores the entire token.

4. Authentication:

Challenge_Sign = IBC_Sign (Challenge, Token_Private_Key, IBC_Common_Para);

Result = IBC_Verify (Challenge, Challenge_Sign, ID, IBC_Common_Para);

One of the necessary conditions for passing the verification is to pass the inspection. If there is a client lock list in the authentication center, the necessary conditions for authentication to pass are: the client tag in the token is not in the client lock list.

Embodiment 7: Authentication process (device information + password):

1. System establishment:

The initialization phase of PKG:

(IBC_Master_Key, IBC_Common_Para) = IBC_Setup ();

2. Private key and authentication identification generation:

The authentication module initiates a private key generation request, and the private key generation request includes the current device information and password of the authentication module.

The authentication center generates an authentication token Token, which contains 2 authentication factors: device information (from the private key generation request) and password (from the private key generation request). The authentication center uses Token as the ID, uses PKG to generate the authentication private key Token_Private_Key through the master keys IBC_Master_Key and IBC_Common_Para, and then sends the Token_Private_Key and Token to the corresponding authentication module through trusted and confidential means (such as using the SSL protocol) in.

Token_Private_Key = IBC_PKG (IBC_Master_Key, Token, IBC_Common_Para);

3. Handling of private key and authentication ID:

The authentication center completely deletes the entire token.

The authentication module completely deletes the password in the Token (account-based application scenarios) or stores the rest of the Token (device-based application scenarios).

4. Authentication:

The authentication module obtains the current device information in real time, the authentication module obtains the password entered by the user in real time (account-based application scenarios) or directly obtains the remaining part of the stored token (device-based application scenarios), thereby assembling a complete authentication identifier . The authentication module uses a complete authentication identifier, uses the authentication private key Token_Private_Key to sign the challenge Challenge using the IBC signature algorithm, obtains the digital signature Challenge_Sign, and then challenges (if Challenge is generated by the authentication module itself), Token and Challenge_Sign is sent to the authentication center;

Challenge_Sign = IBC_Sign (Challenge, Token_Private_Key, IBC_Common_Para);

Result = IBC_Verify (Challenge, Challenge_Sign, ID, IBC_Common_Para);

Embodiment 8: Authentication process (equipment information + expiration time):

1. System establishment:

The initialization phase of PKG:

(IBC_Master_Key, IBC_Common_Para) = IBC_Setup ();

2. Private key and authentication identification generation:

The authentication center generates an authentication token Token, which contains two authentication factors: device information (from the private key generation request), and the expiration time (set by the authentication center). The authentication center uses Token as the ID, uses PKG to generate the authentication private key Token_Private_Key through the master keys IBC_Master_Key and IBC_Common_Para, and then sends the Token_Private_Key and Token to the corresponding authentication module through trusted and confidential means (such as using the SSL protocol) in.

Token_Private_Key = IBC_PKG (IBC_Master_Key, Token, IBC_Common_Para);

3. Handling of private key and authentication ID:

The authentication center completely deletes the entire token.

The authentication module completely deletes the device information in the token and stores the rest of the token.

4. Authentication:

Challenge_Sign = IBC_Sign (Challenge, Token_Private_Key, IBC_Common_Para);

Result = IBC_Verify (Challenge, Challenge_Sign, ID, IBC_Common_Para);

One of the necessary conditions for passing the verification is to pass the inspection. If a device lock list exists in the authentication center, the necessary conditions for authentication to pass are: the device information in the token is not in the device lock list. Another necessary condition is that the current time is not greater than the expiration time in the authentication identification.

Embodiment 9: Authentication process (password + expiration time):

1. System establishment:

The initialization phase of PKG:

(IBC_Master_Key, IBC_Common_Para) = IBC_Setup ();

2. Private key and authentication identification generation:

The authentication center generates an authentication token Token, which contains two authentication factors: the password (from the private key generation request), and the expiration time (set by the authentication center). The authentication center uses Token as the ID, uses PKG to generate the authentication private key Token_Private_Key through the master keys IBC_Master_Key and IBC_Common_Para, and then sends the Token_Private_Key and Token to the corresponding authentication module through trusted and confidential means (such as using the SSL protocol) in.

Token_Private_Key = IBC_PKG (IBC_Master_Key, Token, IBC_Common_Para);

3. Handling of private key and authentication ID:

The authentication center completely deletes the token.

After the authentication module completely deletes the password in the Token, it stores the remaining part of the Token (account-based application scenario) or directly stores the remaining part of the Token (device-based application scenario).

4. Authentication:

Challenge_Sign = IBC_Sign (Challenge, Token_Private_Key, IBC_Common_Para);

Result = IBC_Verify (Challenge, Challenge_Sign, ID, IBC_Common_Para);

Embodiment 10: Authentication process (device information + password + expiration time):

1. System establishment:

The initialization phase of PKG:

(IBC_Master_Key, IBC_Common_Para) = IBC_Setup ();

2. Private key and authentication identification generation:

The authentication center generates an authentication token Token, which contains three authentication factors: device information (from the private key generation request), password (from the private key generation request), and expiration time (set by the authentication center). The authentication center uses Token as the ID, uses PKG to generate the authentication private key Token_Private_Key through the master keys IBC_Master_Key and IBC_Common_Para, and then sends the Token_Private_Key and Token to the corresponding authentication module through trusted and confidential means (such as using the SSL protocol) in.

Token_Private_Key = IBC_PKG (IBC_Master_Key, Token, IBC_Common_Para);

3. Handling of private key and authentication ID:

The authentication center completely deletes the entire token.

4. Authentication:

Challenge_Sign = IBC_Sign (Challenge, Token_Private_Key, IBC_Common_Para);

Result = IBC_Verify (Challenge, Challenge_Sign, ID, IBC_Common_Para);

Embodiment 11: Authentication process (device information + password + expiration time + client label):

1. System establishment:

The initialization phase of PKG:

(IBC_Master_Key, IBC_Common_Para) = IBC_Setup ();

2. Private key and authentication identification generation:

The authentication module initiates a private key generation request, and the private key generation request includes the current device information, password, and client label of the authentication module.

The authentication center generates an authentication token Token, which contains 4 authentication factors: device information (from the private key generation request), password (from the private key generation request), client label (from the private key generation request), and expiration time (Set by the authentication center). The authentication center uses Token as the ID, uses PKG to generate the authentication private key Token_Private_Key through the master keys IBC_Master_Key and IBC_Common_Para, and then sends the Token_Private_Key and Token to the corresponding authentication module through trusted and confidential means (such as using the SSL protocol) in.

Token_Private_Key = IBC_PKG (IBC_Master_Key, Token, IBC_Common_Para);

3. Handling of private key and authentication ID:

The authentication center completely deletes the entire token.

4. Authentication:

Challenge_Sign = IBC_Sign (Challenge, Token_Private_Key, IBC_Common_Para)

Result = IBC_Verify (Challenge, Challenge_Sign, ID, IBC_Common_Para)

One of the necessary conditions for passing the verification is to pass the inspection. If a device lock list exists in the authentication center, the necessary conditions for authentication to pass are: the device information in the token is not in the device lock list. Another necessary condition is that the current time is not greater than the expiration time in the authentication identification. If there is a client lock list in the authentication center, the necessary conditions for authentication to pass are: the client tag in the token is not in the client lock list.

Embodiment 12: Authentication process (device information + password + expiration time + account name + client label):

1. System establishment:

The initialization phase of PKG:

(IBC_Master_Key, IBC_Common_Para) = IBC_Setup ();

2. Private key and authentication identification generation:

The authentication module initiates a private key generation request. The private key generation request includes the current device information, password, account name, and client label of the authentication module.

The authentication center generates an authentication token Token, which contains 5 authentication factors: device information (from the private key generation request), password (from the private key generation request), expiration time (set by the authentication center), and account name (From the private key generation request), client tag (from the private key generation request). The authentication center uses Token as the ID, uses PKG to generate the authentication private key Token_Private_Key through the master keys IBC_Master_Key and IBC_Common_Para, and then sends the Token_Private_Key and Token to the corresponding authentication module through trusted and confidential means (such as using the SSL protocol) in.

Token_Private_Key = IBC_PKG (IBC_Master_Key, Token, IBC_Common_Para);

3. Handling of private key and authentication ID:

The authentication center completely deletes the entire token.

4. Authentication:

Challenge_Sign = IBC_Sign (Challenge, Token_Private_Key, IBC_Common_Para);

Result = IBC_Verify (Challenge, Challenge_Sign, ID, IBC_Common_Para);

One of the necessary conditions for passing the verification is to pass the inspection. If a device lock list exists in the authentication center, the necessary conditions for authentication to pass are: the device information in the token is not in the device lock list. If there is a client lock list in the authentication center, the necessary conditions for authentication to pass are: the client tag in the token is not in the client lock list. Another necessary condition is that the current time is not greater than the expiration time in the authentication identification.

For different application scenarios, Embodiment 12 includes the following four application examples:

Application Example 1:

The application scenario is an application scenario based on user accounts. The authentication module refers to various hardware, software, or firmware that performs account authentication operations, such as certain online banking clients and electronic locks. The authentication center runs on the server and is used to process the client's authentication request.

As shown in FIG. 2, an authentication method includes the following steps:

Step 11) The authentication center selects an IBC algorithm and establishes a private key generator PKG for the algorithm. Use PKG for initialization to generate a set of IBC_Master_Key and IBC_Common_Para. The IBC_Common_Para is made public, and the authentication module is loaded into the IBC_Common_Para. The IBC_Master_Key should be stored in the high-security server and cannot be leaked. The PKG also runs on the high-security server. Operations that do not involve IBC_Master_Key and PKG can be completed using a general server.

The initialization phase of PKG:

(IBC_Master_Key, IBC_Common_Para) = IBC_Setup ();

All connections between the server and the client related to authentication should always be based on a secure channel, and the client has the ability to authenticate the server, such as using the SSL protocol.

Step 12) The authentication module generates an account name and sets a second authentication method, and sends the account name and the second authentication method to the authentication center; the authentication center binds the account name and the second authentication method to the database and stores it in the database. in;

Each account corresponds to a unique account name Account. The account name is selected by the user, or specified by the authentication center of the server, or generated through negotiation between the two parties. When generating an account, the user needs to leave a reliable second authentication method, such as the mobile phone number used to receive the SMS verification code.

Step 13) The authentication module performs device binding, and sends device hardware information and password to the authentication center; the authentication center generates an authentication identifier, and generates an authentication private key based on the authentication identifier; specifically including:

Step 13-1) The user initiates a binding application on the authentication module of the device and uses the second authentication method for authentication;

Step 13-2) After passing the authentication using the second authentication method, the authentication module sends information such as device hardware information Dev_Info, password Psw, and client tag Client_Tag to the authentication center;

Step 13-3) The authentication center generates an authentication token Token for the authentication module;

Token consists of at least account name Account, hardware information Dev_Info, and password Psw, and can also contain information such as client tag Client_Tag and expiry date Expire_Date. See Table 1:

Table 1

among them:

Dev_Info is information that can uniquely identify the current device.

Psw: The password is entered by the user. After the device binding is completed, neither the client nor the server saves the Psw. The Psw must be saved by the user and cannot be leaked. The password is not limited to the character form. It can also be deterministic information such as a gesture password, and vague information such as a fingerprint cannot be used.

Client_Tag: When the client is started for the first time, a random number is generated as Client_Tag. The user can also delete and regenerate Client_Tag.

Expire_Date: The expiration date of the token, which is determined by the server.

Step 13-4) The authentication center uses Token as the ID, and uses the PKG of step 11) to generate the authentication private key Token_Private_Key from the master key;

Token_Private_Key = IBC_PKG (IBC_Master_Key, Token, IBC_Common_Para);

The administrator operates PKG, inputs IBC_Master_Key and ID (authentication identifier) and IBC_Common_Para, and generates a private key (Token_Private_Key) for the authentication module. Then, the private key is sent to the corresponding signatory through trusted and confidential means (such as using the SSL protocol).

Step 14) The authentication center sends the authentication ID and the authentication private key to the authentication module, and then deletes the password in the authentication ID; after receiving the authentication module, the authentication ID and the authentication private key with the password deleted are stored; These include:

Step 14-1) The authentication center sends the Token and Token_Private_Key to the authentication module, and then deletes the Token or saves only some information other than Psw in the Token to the database (be sure to completely delete the Psw information)

Step 14-2) After receiving the Token and Token_Private_Key, the authentication module saves the Token_Private_Key, and at the same time saves all information in the Token except Psw (be sure to completely delete the Psw information).

Step 15) The authentication module sends an authentication request to the authentication center, and the authentication center returns the authentication result to the authentication module after processing; specifically including:

Step 15-1) The authentication module sends an authentication request to the authentication center;

Step 15-2) The authentication center sends a Challenge to the authentication module; the challenge is a random number or other specific information;

Step 15-3) The user enters the password Psw into the authentication module, and the authentication module assembles a complete authentication identifier Token; uses the authentication private key Token_Private_Key to sign the challenge Challenge using the IBC signature algorithm, and obtains the digital signature Challenge_Sign of Challenge Then send Token and Challenge_Sign to the authentication center;

After the signing party obtains the private key, they can digitally sign:

IBC_Signature = IBC_Sign (Message, Token_Private_Key, IBC_Common_Para);

Step 15-4) The authentication center uses the authentication token Token as the ID to verify the Challenge_Sign using the IBC signature verification algorithm; obtain the authentication result;

The signing party can directly use the signer's ID for signing:

Result = IBC_Verify (Message, IBC_Signature, ID, IBC_Common_Para);

One of the necessary conditions for authentication is to pass the verification check. Other optional requirements are: Dev_Info and Client_Tag (if there is Client_Tag) in the database and corresponding to Account, Dev_Info is not in the device lock list, Dev_Info and Client_Tag are not. In the client lock list, the current time is before Expire_Date (if there is Expire_Date) and so on.

Step 15-5) The authentication center sends the authentication result to the authentication module.

When another challenge verification method is adopted, the step 15) includes:

Step 15-1 ′) The user enters the password Psw into the authentication module, and the authentication module assembles a complete authentication token Token; the authentication module generates a challenge, and uses the authentication private key Token_Private_Key to sign the challenge Challenge using the IBC signature algorithm, Get the digital signature Challenge_Sign of Challenge, and then send the Token, challenge and digital signature Challenge_Sign to the authentication center;

After the signing party obtains the private key, they can digitally sign:

IBC_Signature = IBC_Sign (Message, Token_Private_Key, IBC_Common_Para);

Step 15-2 ′) The authentication center uses the authentication token Token as the ID to verify the Challenge_Sign using the IBC signing algorithm; obtain the authentication result;

The signing party can directly use the signer's ID for signing:

Result = IBC_Verify (Message, IBC_Signature, ID, IBC_Common_Para);

Step 15-3 ′) The authentication center sends the authentication result to the authentication module.

In addition, the authentication center can also set a security control policy to put certain Dev_Info into the device lock list under certain appropriate conditions (such as authentication failure several times).

When the user has the risk of leakage in Psw, the device bound to the authentication module is lost, or the Token_Private_Key has the risk of leakage, he should report the loss.

If Dev_Info information is stored in the database of the authentication center, the loss report method includes the following steps:

Step S1) The user uses the new device to use a second authentication method or other identity authentication means to authenticate the user's identity;

Step S2) The authentication center verifies the identity of the user. After the authentication is passed, the authentication center displays the Dev_Info list to the user;

Step S3) The user selects a device to be reported from the Dev_Info list, and informs the authentication center;

Step S4) The authentication center stores the corresponding Dev_Info in the device lock list, and the storage period is permanent (if there is no Expire_Date) or Expire_Date (if there is Expire_Date).

In addition, if the password is forgotten or the token expires, the device needs to go through the device binding process again.

When the time comes to Expire_Date (if there is Expire_Date), the device loss report will be lifted by itself. If the Client_Tag is also stored in the database of the authentication center, the loss reporting operation can be performed on the lost equipment before the loss reporting of the equipment is automatically resolved, including:

Step T4) The authentication center stores the corresponding Dev_Info and Client_Tag into the client lock list, the storage period is permanent (if there is no Expire_Date) or Expire_Date (if there is Expire_Date), and the corresponding Dev_Info is deleted from the device lock list;

Step T5) The device to be reported is completely deleted from the original Client_Tag, then a new Client_Tag is generated, and then the device binding process is performed again.

If Dev_Info information is stored in the database of the authentication center, another method of reporting loss includes the following steps:

Step S2 ′) The authentication center verifies the identity of the user. After the authentication is passed, the authentication center deletes all Dev_Info and Client_Tag (if there is Client_Tag) corresponding to the user account name Account in the database.

After the loss report is completed, re-bind all the bound devices of the Account. One Account can be bound to multiple devices. That is to say, if the loss is reported by this method, all existing device bindings of the Account will be invalidated, and all bindings need to be re-bind again.

The above method of loss reporting is applicable to application scenarios with higher security requirements.

Application example 2

The application scenario is a device-based application scenario, where "client" refers to the device to be authenticated, such as an Internet of Things device.

As shown in FIG. 3, an authentication method includes:

Step 21) The IoT platform establishes an algorithm PKG based on the selected IBC algorithm, and uses the PKG to generate a set of master keys and a set of public parameters; the IoT device loads the set of public parameters;

The IoT platform selects an IBC algorithm and establishes a PKG for the algorithm. Use PKG for initialization to generate a set of IBC_Master_Key and IBC_Common_Para. Make IBC_Common_Para public. The IBC_Master_Key should be stored on the high-security server and cannot be leaked. The PKG should also be run on the high-security server. Operations that do not involve IBC_Master_Key and PKG can be completed using a general server.

Step 22) The IoT device sends the device information and password to the IoT platform. The IoT platform generates an authentication ID, and generates an authentication private key based on the authentication ID. Specifically, it includes:

Step 22-1) The IoT device sends the hardware information Dev_Info and the password Psw to the IoT platform;

Step 22-2) The IoT platform generates a device authentication token Token for the IoT device;

The device authentication ID is composed of at least hardware information Dev_Info, and may also include information such as the expiration date Expire_Date and password Psw. See Table 2:

Table 2

among them:

Dev_Info is information that can uniquely identify the current device.

Psw: The password is randomly generated by the device. The IoT platform does not save Psw. Psw is stored in a secure area of the IoT device and cannot be leaked.

Expire_Date: Token expiration date, determined by the IoT platform.

Step 22-3) The IoT platform uses Token as the ID, and uses the PKG of step 21) to generate the authentication private key Token_Private_Key from the master key;

Step 23) The IoT platform sends the authentication ID and the authentication private key to the IoT device, and deletes the password in the authentication ID. After receiving, the IoT device saves the authentication ID and the authentication private key with the password deleted, and sends The password is stored in the device's secure storage area; it includes:

Step 23-1) The IoT platform sends the Token and Token_Private_Key to the IoT device, and then deletes the Token or saves only some information other than Psw in the Token to the database (be sure to completely delete the Psw information);

Step 23-2) After the IoT device receives the Token and Token_Private_Key, it saves all information in the Token except Psw; and stores the Token_Private_Key and Psw in the secure area of the device.

Step 24) The IoT device sends an authentication request to the IoT platform, and the IoT platform returns the authentication result to the IoT device after processing; specifically including:

Step 24-1) The IoT device sends an authentication request to the IoT platform;

Step 24-2) The IoT platform sends a challenge to the IoT device, and the challenge is a random number or other specific information;

Step 24-3) The IoT device reads Psw from the device's secure storage area to assemble a complete Token; then uses Token_Private_Key to sign the Challenge using the IBC signature algorithm to get the digital signature Challenge_Sign to the Challenge, and the IoT device sends the Token and Challenge_Sign Send to IoT platform;

Step 24-4) The IoT platform uses the Token as the ID to verify the Challenge_Sign using the IBC signing algorithm, and returns the authentication result;

The signing party can directly use the signer's ID for signing:

Result = IBC_Verify (Message, IBC_Signature, ID, IBC_Common_Para);

The IoT platform can also set security control policies to put certain Dev_Info in the device lock list under certain appropriate conditions (such as authentication failure several times).

When another challenge verification method is adopted, the step 24) includes:

Step 24-1 ′) The IoT device reads Psw from the device's secure storage area to assemble a complete Token; the authentication device generates a challenge, and uses the authentication private key Token_Private_Key to sign the challenge Challenge using the IBC signature algorithm to obtain the Challenge Digitally sign Challenge_Sign, then send the Token, challenge and digital signature Challenge_Sign to the IoT platform;

After the signing party obtains the private key, they can digitally sign:

IBC_Signature = IBC_Sign (Message, Token_Private_Key, IBC_Common_Para);

Step 24-2 ′) The IoT platform uses the authentication token Token as the ID to verify the Challenge_Sign using the IBC signature verification algorithm; obtains the authentication result;

The signing party can directly use the signer's ID for signing:

Result = IBC_Verify (Message, IBC_Signature, ID, IBC_Common_Para);

Step 24-3 ') The IoT platform sends the authentication result to the IoT device.

Application Example 3:

The application scenario is an application scenario based on user accounts, where the authentication unit refers to various hardware, software, or firmware that performs account authentication operations, such as certain online banking clients.

As shown in FIG. 4, an authentication system includes: an authentication module 300 and an authentication center 400; as shown in FIG. 5, the authentication module 300 includes: a first IBC loading unit 301, and account generation A unit 302, a device binding unit 303, a first storage unit 304, and a first authentication request unit 305;

A first IBC loading unit 301, configured to load public parameters disclosed by the authentication center 400;

The account generating unit 302 is configured to generate an account name of the authentication module, set a second authentication mode, and send the account name and the second authentication mode to the authentication center 400;

The device binding unit 303 is configured to initiate a device binding request and perform authentication using a second authentication method. After the request is passed, the device information, the password Psw, and the client tag Client_Tag are sent to the authentication center;

A first storage unit 304, configured to store the Psw-deleted authentication identifier Token and the authentication private key Token_Private_Key sent by the authentication center 400;

A first authentication requesting unit 305, configured to send an authentication request to the authentication center 400 by inputting a password Psw, and further configured to receive an authentication result sent by the authentication center 400;

The user inputs Psw to the first authentication request unit, and the first authentication request unit assembles a complete authentication identifier Token; uses the authentication private key Token_Private_Key to sign the Challenge using the IBC signature algorithm, and obtains the digital signature Challenge_Sign of the Challenge, and then Send Token and Challenge_Sign to the authentication center;

As shown in FIG. 6, the authentication center 400 includes a first IBC initialization unit 401, a first authentication identifier generation unit 402, a first authentication private key generation unit 403, a second storage unit 404, and a first authentication verification unit. 405;

The first IBC initialization unit 401 is used to select an IBC algorithm and establish a private key generator PKG of the algorithm, use the PKG to initialize, generate a set of master key IBC_Master_Key and public parameter IBC_Common_Para, and expose IBC_Common_Para;

The first authentication identifier generating unit 402 is configured to generate a device authentication identifier Token according to the account name, device information, and password sent by the authentication module 300; the form of the token is shown in Table 1;

The first authentication private key generation unit 403 is configured to generate an authentication private key Token_Private_Key by using the PKG and the master key generated by the IBC initialization unit 401 with the authentication identification Token as the ID; and then send the authentication identification and the authentication private key To the authentication module 300;

A second storage unit 404: used to store the master key generated by the IBC initialization unit 401, used to store the account name and the second authentication mode of the authentication module 300, and also used to store the authentication identifier with the password deleted;

The first authentication verification unit 405 is configured to receive an authentication request from the authentication module 300, and send a challenge to the authentication module 300; verify the Challenge_Sign using the IBC signature verification algorithm with the authentication identifier as the ID; and the authentication center 400 sends the authentication result to the authentication module 300.

One of the necessary conditions for authentication is to pass the verification check. Other optional requirements are: Dev_Info and Client_Tag (if there is Client_Tag) in the database and corresponding to Account, Dev_Info is not in the device lock list, Dev_Info and Client_Tag are not. Client lock list, the current time is before Expire_Date (if there is Expire_Date)

Application Example 4:

As shown in FIG. 7, an authentication system includes: an IoT device 500 and an IoT platform 600; as shown in FIG. 8, the IoT device 500 includes: a second IBC loading unit 501, information A sending unit 502, a third storage unit 503, a device secure storage area 504, and a second authentication request unit 505;

A second IBC loading unit 501 for loading public parameters disclosed by the Internet of Things platform 600;

An information sending unit 502, configured to send device information and a password Psw to the IoT platform 600;

A third storage unit 503, configured to store the authentication identifier Token with the deleted password Psw sent by the Internet of Things platform 600;

Device secure storage area 504, which is used to store the password Psw and the authentication private key Token_Private_Key;

A second authentication requesting unit 505, configured to send an authentication request to the Internet of Things platform 600, and receive an authentication result sent by the Internet of Things platform 600;

Read the Psw from the device's secure storage area to assemble a complete authentication identification; use Token_Private_Key to sign the Challenge using the IBC signature algorithm, get a digital signature on the Challenge (Challenge_Sign), and send the Token and Challenge_Sign to the IoT platform 400.

As shown in FIG. 9, the Internet of Things platform 600 includes: a second IBC initialization unit 601, a second authentication identifier generation unit 602, a second authentication private key generation unit 603, a fourth storage unit 604, and a second authentication verification unit 605;

The second IBC initialization unit 601 is used to select an IBC algorithm and establish a private key generator PKG for the algorithm, use the PKG to initialize, generate a set of master key IBC_Master_Key and public parameter IBC_Common_Para, and expose IBC_Common_Para;

The second authentication identifier generating unit 602 is configured to generate a device authentication identifier Token according to the device information and password sent by the IoT device 500; the form of the token is shown in Table 2;

The second authentication private key generation unit 603 is configured to generate an authentication private key Token_Private_Key with the Token as the ID and the PKG and the master key generated by the IBC initialization unit 601; and then send the authentication identifier and the authentication private key to the authenticator. Networked equipment 500;

A fourth storage unit 604: used to store the master key generated by the IBC initialization unit 401, and also used to store the authentication identifier with the password deleted;

The second authentication verification unit 605 is configured to receive an authentication request from the IoT device 500 and send a challenge Challenge to the IoT device 500; use the IBC signature verification algorithm to verify the Challenge_Sign with the authentication ID as the ID; the IoT platform 600 will authenticate The weight result is sent to the IoT device 500;

One of the necessary conditions for authentication is to pass the verification check. Other optional requirements are: Dev_Info and Client_Tag (if there is Client_Tag) in the database and corresponding to Account, Dev_Info is not in the device lock list, Dev_Info and Client_Tag are not. In the client lock list, the current time is before Expire_Date (if there is Expire_Date).

The security analysis of the authentication method of the present invention is as follows:

Attack scenario 1: The attacker steals data from the server database.

In the existing password method, the password is stored in the database in the form of a clear text or a password hash value. In this attack scenario, the attacker can directly obtain the password, or use a dictionary attack to obtain the password with a non-negligible success rate.

In the existing challenge response protocol, the authentication key is stored in a database. In this attack scenario, the attacker can directly obtain the authentication key.

In the method of the present invention, the server-side database does not store any information about the password, nor does it store the authentication private key. Even if the attacker obtains all information except the password for the Token, it cannot pass the authentication.

Attack scenario 2: Password leak.

In the existing password methods, password leakage will lead to the attacker being able to authenticate successfully.

In the method of the present invention, an attacker cannot obtain authentication simply by obtaining a password. Even if attack scenario 1 appears side by side, the attacker can only assemble tokens, but because he does not know the authentication private key, he still cannot authenticate successfully.

Attack scenario 3: Attacker gains client device.

According to the attacker's ability assumptions, in this attack scenario, the attacker can obtain any data stored in the device.

In the existing challenge response protocol, since the authentication key needs to be stored in the client device, an attacker can obtain the authentication key.

In the existing certificate-based digital signature method, since the authentication private key needs to be stored in the client device, an attacker can obtain the authentication private key.

In the method of the present invention, although the authentication private key is also stored in the client device, because the client device does not store the password, the attacker cannot form a complete token for authentication.

Usability, efficiency and cost analysis:

In the application scenario of Example 1, the method of the present invention uses the second authentication method when binding the device, and the password needs to be entered on the device during authentication, which is in contrast to the existing high security application scenarios (such as online banking clients) Do the same, without compromising ease of use.

Compared with the existing certificate-based digital signature methods, the method of the present invention no longer uses PKI and certificate chains. Only one verification is required during authentication, and the certificate-based digital signature method requires at least two verifications (verification of the certificate and verification of the authentication signature). And compared with CA, the construction cost of PKG is very low, and the maintenance workload and maintenance cost are also very low.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention and not limiting. Although the present invention has been described in detail with reference to the embodiments, those of ordinary skill in the art should understand that modifications or equivalent replacements of the technical solutions of the present invention shall not depart from the spirit and scope of the technical solutions of the present invention, which should be covered by the present invention Within the scope of the claims.

Claims

An authentication method is used to implement the authentication requested by an authentication center to an authentication module. The authentication module runs on a client and the authentication center runs on a server. The method is characterized in that the method includes:

The authentication center generates an authentication identifier based on one or more authentication factors, and the authentication factor is sent to the authentication center by the authentication module or is generated by the authentication center;

The authentication center generates an authentication private key based on the authentication identifier, and sends the authentication identifier and the authentication private key to the authentication module;

The authentication center and the authentication module perform all operations of storing, partially storing, or deleting the authentication identifier according to the content of the authentication identifier;

The authentication module sends an authentication request to the authentication center, and the authentication center verifies the authentication request.
The authentication method according to claim 1, further comprising: an initialization step of an authentication center and an authentication module: an IBC initialization unit of the authentication center establishes an IBC algorithm based on the selected IBC algorithm PKG, using the PKG to generate a set of master key and a set of public parameters, the second storage unit of the authentication center stores the master key generated by the IBC initialization unit; the IBC load unit of the authentication module loads This group of public parameters.
The authentication method according to claim 2, wherein the authentication factor is: client device hardware information, password, expiration time, account name, or client label.
The authentication method according to claim 3, wherein the method specifically comprises:

Step A1) The authentication module initiates a private key and authentication ID generation request to an authentication center, and sends client device hardware information to the authentication center; the authentication ID generation unit of the authentication center generates a client device Hardware information authentication identifier, and the authentication private key generation unit of the authentication center generates the authentication private key according to the authentication identifier;

Step A2) The authentication center sends an authentication identifier and an authentication private key to the authentication module, and the authentication center deletes the authentication identifier and the authentication private key. After the authentication module receives the authentication module, the authentication module deletes Client device hardware information in the authentication identifier, and the first storage unit of the authentication module stores the authentication identifier and the authentication private key;

Step A3) The authentication request unit of the authentication module sends an authentication request to the authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.
The authentication method according to claim 4, wherein the step A3) specifically comprises:

Step A3-1) The authentication request unit of the authentication module sends an authentication request to the authentication center;

Step A3-2) The authentication verification unit of the authentication center sends a challenge to the authentication module; the challenge is a random number or specific information;

Step A3-3) The authentication module obtains the hardware information of the device and assembles a complete authentication identification; the authentication private key is used to sign the challenge using the IBC signature algorithm to obtain the challenge digital signature, and then the authentication identification and digital signature are sent To the authentication center;

Step A3-4) The authentication verification unit of the authentication center uses the authentication identifier as the ID to verify the digital signature using the IBC signature verification algorithm; obtain the authentication result;

Step A3-5) The authentication verification unit of the authentication center sends the authentication result to the authentication module.
The authentication method according to claim 6, characterized in that when the authentication center sets a device lock list, the step A3-4) further comprises: determining whether the device hardware information in the authentication identifier is in the device lock list If the result of the judgment is affirmative, the signing inspection fails, otherwise, the signing inspection passes.
The authentication method according to claim 4, wherein the step A3) specifically comprises:

Step A3-1 ′) The authentication module obtains client device hardware information and assembles a complete authentication identifier; the authentication request unit of the authentication module generates a challenge, and the challenge is performed using the IBC signature algorithm using the authentication private key Sign, get a digital signature, and then send the authentication ID, challenge, and digital signature to the authentication center;

Step A3-2 ′) The authentication verification unit of the authentication center uses the authentication identifier as the ID to verify the digital signature using the IBC signature verification algorithm; obtains the authentication result;

Step A3-3 ′) The first authentication verification unit of the authentication center sends the authentication result to the authentication module.
The authentication method according to claim 3, wherein the method specifically comprises:

Step B1) The authentication module initiates a private key and authentication ID generation request to the authentication center, and the authentication module sends a password to the authentication center; the authentication ID generation unit of the authentication center generates a password including the password. An authentication identifier, and an authentication private key generating unit of an authentication center generates an authentication private key according to the authentication identifier;

Step B2) The authentication center sends the authentication identifier and the authentication private key to the authentication module, and the authentication center deletes the authentication identifier and the authentication private key. After receiving the authentication module, the authentication module deletes The password in the authentication ID, and the first storage unit of the authentication module stores the authentication ID and the authentication private key;

Step B3) The authentication request unit of the authentication module sends an authentication request to the authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.
The authentication method according to claim 3, wherein the method specifically comprises:

Step C1) The account generation unit of the authentication module generates an account name, the authentication module initiates a private key and authentication ID generation request to the authentication center, and sends the account name to the authentication center;

Step C2) The authentication identifier generation unit of the authentication center generates an authentication identifier including an account name, and the authentication private key generation unit of the authentication center generates an authentication private key according to the authentication identifier;

Step C3) The authentication center sends the authentication identifier and the authentication private key to the authentication module, and the authentication center deletes the authentication identifier and the authentication private key; after the authentication module receives the authentication module, The first storage unit stores an authentication identifier and an authentication private key;

Step C4) The authentication request unit of the authentication module sends an authentication request to the authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.
The authentication method according to claim 3, wherein the method specifically comprises:

Step D1) The authentication module initiates a request for generating a private key and an authentication identifier to the authentication center, and the authentication module sends a client tag to the authentication center; the generation of the authentication identifier generating unit of the authentication center includes An authentication identifier of a client label, and an authentication private key generating unit of the authentication center generates an authentication private key according to the authentication identifier;

Step D2) The authentication center sends the authentication identifier and the authentication private key to the authentication module, and the authentication center deletes the authentication identifier and the authentication private key. After the authentication module receives the authentication module, The first storage unit stores an authentication identifier and an authentication private key;

Step D3) The authentication request unit of the authentication module sends an authentication request to an authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.
The authentication method according to claim 10, wherein the step D3) specifically comprises:

Step D3-1) The authentication request unit of the authentication module sends an authentication request to the authentication center;

Step D3-2) The authentication verification unit of the authentication center sends a challenge to the authentication module; the challenge is a random number or specific information;

Step D3-3) The authentication module obtains the authentication ID from the first storage unit; uses the authentication private key to sign the challenge using the IBC signature algorithm to obtain the digital signature of the challenge, and then sends the authentication ID and digital signature to the authentication center;

Step D3-4) The authentication verification unit of the authentication center uses the authentication identifier as the ID to verify the digital signature using the IBC signature verification algorithm; obtains the authentication result;

Step D3-5) The authentication verification unit of the authentication center sends the authentication result to the authentication module.
The authentication method according to claim 11, wherein, when the authentication center sets a client lock list, the step D3-4) further comprises: determining whether the client tag in the authentication identifier is on the client lock list If the result of the judgment is affirmative, the signing inspection fails. Otherwise, the signing inspection passes.
The authentication method according to claim 3, wherein the method specifically comprises:

Step E1) The authentication identifier generation unit of the authentication center generates an authentication identifier including a time of expiration, and the authentication private key generation unit of the authentication center generates an authentication private key according to the authentication identifier;

Step E2) The authentication center sends an authentication identifier and an authentication private key to the authentication module, and the authentication center deletes the authentication identifier and the authentication private key. After the authentication module receives the authentication module, The first storage unit stores an authentication identifier and an authentication private key;

Step E3) The authentication request unit of the authentication module sends an authentication request to the authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.
The authentication method according to claim 13, wherein the step E3) specifically comprises:

Step E3-1) The authentication request unit of the authentication module sends an authentication request to the authentication center;

Step E3-2) The authentication verification unit of the authentication center sends a challenge to the authentication module; the challenge is a random number or specific information;

Step E3-3) The authentication module obtains the authentication ID from the first storage unit; uses the authentication private key to sign the challenge using the IBC signature algorithm, obtains the challenge digital signature, and then sends the authentication ID and digital signature to the authentication center;

Step E3-4) The authentication verification unit of the authentication center uses the authentication identifier as the ID to verify the digital signature using the IBC sign verification algorithm; obtain the authentication result;

Step E3-5) The authentication verification unit of the authentication center sends the authentication result to the authentication module.
The authentication method according to claim 14, wherein the step E3-4) further comprises: judging whether the current time is less than the expiration time in the authentication identifier, and if the judgment result is positive, the verification is passed, Otherwise, the verification fails.
The authentication method according to claim 3, wherein when the authentication factor includes client device hardware information and a password, the method specifically includes:

Step F1) The authentication module initiates a private key and authentication ID generation request to the authentication center, and sends the client device hardware information and password to the authentication center; the authentication ID generation unit of the authentication center includes the client End device hardware information and password authentication ID, and the authentication private key generation unit of the authentication center generates the authentication private key according to the authentication ID;

Step F2) The authentication center sends the authentication identifier and the authentication private key to the authentication module, and the authentication center deletes the authentication identifier; after the authentication module receives, the authentication module deletes the authentication identifier In the password, the first storage unit of the authentication module stores an authentication identifier and an authentication private key;

Step F3) The authentication request unit of the authentication module sends an authentication request to the authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.
The authentication method according to claim 3, wherein when the authentication factor includes client device hardware information, a password, and an account name, the method specifically includes:

Step G1) The account generating unit of the authentication module generates an account name, and sends the account name to the authentication center; and stores the account name in a storage unit of the authentication center;

Step G2) The authentication module initiates a private key and authentication ID generation request to the authentication center, and sends the client device hardware information and password to the authentication center; the generation of the authentication ID generation unit of the authentication center includes at least The authentication ID of the account name, client device hardware information, and password, and the authentication private key generation unit of the authentication center generates the authentication private key according to the authentication ID;

Step G3) The authentication center sends an authentication identifier and an authentication private key to the authentication module, and the authentication center deletes the authentication identifier; after the authentication module receives, the authentication module deletes the authentication identifier In the password, the first storage unit of the authentication module stores an authentication identifier and an authentication private key;

Step G4) The authentication request unit of the authentication module sends an authentication request to the authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.
The authentication method according to claim 17, wherein the step G2) specifically comprises:

Step G2-1) The authentication module initiates a private key and authentication identifier generation request to the authentication center, and the authentication module sends the client device hardware information and password to the authentication center;

Step G2-2) The authentication center generates an authentication identifier for the authentication module; the authentication identifier consists of at least an account name, client device hardware information, and a password;

Step G2-3) The authentication center uses the authentication ID as the ID, and uses the PKG generated in the initialization step to generate the authentication private key through the master key.
The authentication method according to claim 3, wherein when the authentication factor includes client device hardware information, password, client label, and expiration time, the method specifically includes:

Step H1) The authentication module initiates a private key and authentication ID generation request to the authentication center, and sends the client device hardware information, password, and client label to the authentication center; the authentication ID generation of the authentication center The unit generates an authentication identifier including account name, client device hardware information, password, client label, and expiration time, and the authentication private key generation unit of the authentication center generates an authentication private key according to the authentication identifier;

Step H2) The authentication center sends an authentication identifier and an authentication private key to the authentication module, and the authentication center deletes the authentication identifier; after receiving the authentication module, the authentication module deletes the authentication identifier The password and the client device hardware information, the first storage unit of the authentication module stores the authentication identifier and the authentication private key;

Step H3) The authentication request unit of the authentication module sends an authentication request to the authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.
The authentication method according to claim 3, wherein when the authentication factor includes client device hardware information, password, account name, client label, and expiration time, the method specifically includes:

Step R1) The account generating unit of the authentication module generates an account name, and sends the account name to the authentication center; and stores the account name in a storage unit of the authentication center;

Step R2) The authentication module initiates a private key and authentication ID generation request to the authentication center, and sends client device hardware information, password, and client label to the authentication center; the authentication ID generation of the authentication center The unit generates an authentication identifier including account name, client device hardware information, password, client label, and expiration time, and the authentication private key generation unit of the authentication center generates an authentication private key according to the authentication identifier;

Step R3) The authentication center sends the authentication identifier and the authentication private key to the authentication module, and the authentication center deletes the authentication identifier; after receiving the authentication module, the authentication module deletes the authentication identifier The password and the client device hardware information, the first storage unit of the authentication module stores the authentication identifier and the authentication private key;

Step R4) The authentication request unit of the authentication module sends an authentication request to the authentication center, and the authentication verification unit of the authentication center returns the authentication result to the authentication module after verification.
The authentication method according to claim 20, wherein when the authentication center saves the device information list, the method further comprises the step of reporting a loss:

Step S1) The user authenticates the user's identity through the new device using the second authentication mode or other identity authentication means;

Step S2) The authentication center verifies the identity of the user. After the authentication is passed, the authentication center displays the device information list to the user;

Step S3) The user selects a device to be reported from the device information list, and informs the authentication center;

Step S4) The authentication center stores the corresponding device hardware information in the device lock list, and the storage period is permanent or expiration date.
The authentication method according to claim 20, wherein when the authentication center saves device hardware information, the method further comprises the step of reporting a loss:

Step S1 ′) The user authenticates the user identity through the new device using the second authentication mode or other identity authentication means;

Step S2 ′) The authentication center verifies the identity of the user. After the authentication is passed, the authentication center deletes all the device hardware information and client tags corresponding to the user account in the database;

Step S3 ′) All device bindings of the account have been invalidated, and all devices perform the device binding process again.
The authentication method according to claim 21 or 22, wherein after performing the loss reporting step, when the time reaches the expiration time, the device loss reporting is automatically cancelled; when a client label list is set in the authentication center, the device is Before the report of loss is released, the method further includes the steps of canceling the report:

Step T1)) The user uses the new device to use the second authentication method or other identity authentication means to authenticate the user's identity;

Step T2) The authentication center verifies the identity of the user. After the authentication is passed, the authentication center displays the device lock list to the user;

Step T3) The user selects a device from the device lock list to report loss, and informs the authentication center;

Step T4) The authentication center puts the corresponding device hardware information and client label in the client lock list, the storage period is permanent or expiration date, and simultaneously deletes the corresponding device hardware information from the device lock list;

Step T5) The device to be reported is completely deleted from the original client label, then a new client label is generated, and then the device binding is performed again.
An authentication system includes: an authentication module and an authentication center; the authentication module runs on a client, and the authentication center runs on a server; and is characterized in that:

The authentication center is configured to generate an authentication identifier based on one or more authentication factors, and the authentication factor is sent to the authentication center by the authentication module or is generated by the authentication center; and is further used based on the authentication identifier. Generate an authentication private key, and send the authentication ID and the authentication private key to the authentication module; it is also used to perform all operations of storing, partially storing, or deleting the authentication ID based on the content of the authentication ID; Verifying the authentication request sent by the authentication module;

The authentication module is configured to perform all operations of storing, partially storing, or deleting the authentication identifier according to the content of the authentication identifier, and is further configured to send an authentication request to the authentication center.
The authentication system according to claim 24, wherein the authentication module comprises: an IBC load unit, an account generation unit, a private key request unit, a first storage unit, and an authentication request unit;

The IBC loading unit is used to load the public parameters disclosed by the authentication center;

The account generating unit is configured to generate an account name of an authentication module;

The first storage unit is configured to store an authentication identifier and / or an authentication private key;

The private key requesting unit is configured to send an authentication factor to an authentication center;

The authentication request unit is configured to send an authentication request to an authentication center, and is also used to receive an authentication result sent by the authentication center.
The authentication system according to claim 24 or 25, wherein the authentication center comprises: an IBC initialization unit, an authentication identifier generation unit, an authentication private key generation unit, a second storage unit and an authentication verification unit ;

The IBC initialization unit is used to select an IBC algorithm and establish a private key generator PKG for the algorithm, use the PKG for initialization, generate a set of master keys and public parameters, and publicize the public parameters;

The authentication identifier generating unit is configured to generate an authentication identifier according to an authentication factor sent by an authentication module;

The authentication private key generation unit is configured to generate an authentication private key by using the authentication identifier as an ID and the PKG and the master key generated by the IBC initialization unit; and then send the authentication identifier and the authentication private key to the authentication module. ;

The second storage unit is configured to store a master key generated by an IBC initialization unit;

The authentication verification unit is configured to receive an authentication request from an authentication module, use an authentication identifier as an ID to verify a digital signature using an IBC signature verification algorithm, and send an authentication result to the authentication module.