Multi-brand H5 page-oriented flexible access mechanism and dynamic identity authentication method

Abstract

The invention provides a multi-brand H5 page-oriented flexible access mechanism and a dynamic identity authentication method. A vehicle purchase page is established based on HTML5 to perform data display and a business process; a method for independently distributing a unique identity label for the brand and each series of vehicle types under the brand is designed based on a vehicle enterprise brand entering mode; a dynamic identity authentication method is designed for encrypting and verifying transmission data by using own private keys held by two parties and public keys held by the two parties during jumping among H5 pages of a multi-party platform; a dynamic token is generated through a secret key, so that identity authentication is carried out on requests of both parties, the security of data communication is guaranteed, multi-platform jump-based request identity authentication is realized, flexible access to a unified operation platform of a multi-brand three-party system can be supported, and a one-stop service mode of car selection, car purchase, insurance purchase and registration and number selection is further ensured.

Description

Technical Field

[0001] The present invention relates to the technical field of dynamic identity authentication, and in particular to a flexible access mechanism and a dynamic identity authentication method for multi-brand H5 pages. Background Art

[0002] As the country continues to introduce favorable policies such as "vehicle purchase tax exemption" and "vehicle trade-in", the demand for purchasing small passenger cars continues to expand. The existing car purchase process often involves viewing and comparing cars on online consulting platforms, and then making an appointment to test drive and place an order at offline car dealers (4S stores). Car dealers register orders on their own platforms, and the system pushes them to the car company's production system for production scheduling. After the vehicle is delivered to the dealer, the business personnel notify the buyer to pick up the car at the store, purchase insurance, and finally go to the vehicle management office to register and select a number. In the existing technology, there are also platforms that integrate multiple car companies, but under the current car purchase model, car buyers actually need to download applications and register personal information in multiple online and offline links such as consulting APPs, 4S stores, insurance APPs, and vehicle management offices, involving multiple docking parties such as car companies, dealers / delivery centers / experience centers, insurance, taxation, and traffic management resources. There is no platform that can connect all links, resulting in the entire car purchase process not only being cumbersome and opaque, but also having the risk of personal information being leaked and abused. Summary of the invention

[0003] In order to solve the problems in the prior art that the car purchasing process is complicated and the information is not transparent, and there is a risk of abuse of personal information, the present invention provides a flexible access mechanism and a dynamic identity authentication method for multi-brand H5 pages, which can ensure the transparency of the car purchasing process while ensuring the communication security of personal privacy data.

[0004] The technical solution of the present invention is as follows: a flexible access mechanism and dynamic identity authentication method for multi-brand H5 pages, characterized in that it includes the following steps: S1: Build a unified operation platform and dedicated APP; The unified operation platform includes: a car enterprise brand management module, a car purchase management module and a public service management module; The car enterprise brand management module manages all connected car enterprises and products; the car purchase management module manages the purchase process of the car; the public service management module manages all links other than the purchase process of the car purchase; The dedicated APP acts as a client to provide car buyers with an entrance to the unified operating platform; The brand service end of the automobile enterprise brand establishes data connection with the unified operation platform; The car purchase page of the unified operation platform and the car purchase page of the brand service end of the car enterprise brand itself are both built based on HTML5 technology; S2: Automobile enterprise brands apply to enter the unified operation platform and provide brand registration information; The brand registration information includes: brand information and brand public and private keys; The brand public and private keys are generated by the brand party, and a pair of public and private keys are generated through the SM2 algorithm: orgPubKey and orgPriKey. The orgPubKey is provided to the platform party, and the orgPriKey is held by the brand party; S3: The unified operation platform reviews the brand registration information; after the review is passed, the system automatically generates the unique authentication code orgCode and platform public key of the registered brand; The platform public key is generated by the platform, and a pair of public and private keys are generated through the SM2 algorithm: sitePubKey and sitePriKey. The sitePubKey is provided to the brand, and the sitePriKey is held by the platform. S4: Car companies register their brands for products; The unified operation platform assigns a unique model code orgProdCode to each brand product; S6: The car brand synchronizes the specific vehicle parameters of each model to the unified operation platform through the public interface opened by the platform in accordance with the interface access specification; each time data is written, authentication information is included; The authentication information includes: brand authentication code orgCode, vehicle model code orgProdCode, timestamp timestamp and signature sign JSON string, and the JSON string is encrypted and transmitted using sitePubKey; S7: After receiving the vehicle model parameters pushed by the car enterprise brand, the unified operation platform first decrypts the authentication information using sitePriKey and verifies the signature using orgPubKey. After the signature verification is passed, check whether siteCode and siteProdCode have been registered in the platform and whether the product is online normally. After all the verifications are passed, the vehicle model parameters are received; The unified operation platform confirms the received vehicle model parameters, and after confirmation, publishes them to the platform and synchronizes them to the relevant car purchase section of the dedicated APP; S8: The car purchasing user accesses the car purchasing section based on the dedicated APP, selects a car model and places an order, and then jumps to the car purchasing page on the brand service end; Before the jump, the unified operation platform generates the order number orderId, the identity authentication token authToken and the page token information jsApiToken, and caches them in Redis; The page token information jsApiToken is used for the page token authentication information carried when the car purchase page on the brand server jumps back to the unified operation platform H5 page; the authentication information is generated by the unified operation platform and passed when jumping to the car purchase page on the brand server; The identity authentication token authToken is used to carry the platform authentication information when the unified operation platform car purchase page jumps to the car purchase page on the brand service end; it is generated by the unified operation platform and passed when jumping to the car purchase page on the brand service end; After the brand server verifies the authToken, the user pays the deposit; S9: After the user pays the deposit, the brand server will send the generated car purchase order details back to the unified operation platform through the interface. After the unified operation platform returns a successful response, the brand server's order page will display a successful order. When the user clicks the back button, the brand server H5 page jumps back to the unified operation platform's order progress H5 page, carrying the page token information jsApiToken information; S10: After receiving the callback request, the unified operation platform verifies the legitimacy of jsApiToken. After all verifications are passed, the order information is written to complete the car purchase process. S11: The user completes other relevant processes of car purchase based on the public service management module.

[0005] It is further characterized by: The public service management module includes: access ports related to insurance, taxation and traffic management resources; wherein, the pages related to insurance purchase are constructed based on HTML5 technology; The page token information jsApiToken generation rule: the orgCode brand authentication code, orgProdCode vehicle model code, userId user account, and timestamp are included to generate a JSON string jsApiTokenBean, and the SM2 algorithm + sitePubKey is used to encrypt it to obtain the ciphertext jsApiToken; The authentication token authToken generation rule: generate a JSON string authTokenBean containing the orgCode brand authentication code, userId user account, orderId order number, orgProdCode vehicle model code, timestamp timestamp, jsApiToken page token, and signature summary, and encrypt it using the SM2 algorithm + orgPubKey to obtain the ciphertext authToken; The summary signature generation rule is: concatenate the strings in the following format to get signatureStr, and use sitePriKey to perform summary to get signature; orgCode=brand authentication code# userId=user account# timestamp=timestamp# jsApiToken=page token; In step S6, the signature generation rule is: concatenate siteCode, siteProdCode, and timestamp in the following format and use orgPriKey to perform a digest signature. The concatenation rule is as follows: orgCode=brand certification code#orgProdCode=model code#timestamp=timestamp; In step S8, the brand server verifies authToken by the following steps: a1: Use orgPriKey to decrypt authToken and obtain the plain text of orgCode, userId, timestamp, jsApiToken and signature. a2: After decryption is successful, first verify whether the signature exists in Redis; If it already exists, it is considered that the request has been received and the error prompt page is displayed; If the signature does not exist, go to step a3; a3: Obtain signatureStr according to the signature generation rule, and verify the signature through SM2+sitePubKey. After the signature verification is passed, verify whether the timestamp is within the preset time limit; if it is within the time limit, enter the car company's car purchase and order H5 page, and cache the signature to Redis; In step S10, the unified operation platform verifies the legitimacy of jsApiToken, which specifically includes the following steps: b1: Get the jsApiToken from the local cache and check whether it exists; If it exists, decrypt the jsApiToken information through sitePriKey to obtain userId (user account), orderId (order number), orgProdCode (car model code), and timestamp (timestamp); b2: Execute all the following confirmations: Check whether userId and orderId exist on this platform; Check whether the model is consistent with the order information; Check whether the timestamp is within the preset time limit.

[0006] The present invention provides a flexible access mechanism and dynamic identity authentication method for multi-brand H5 pages, which builds a vehicle purchase page based on HTML5 to display data and business processes; designs a method based on the car company brand entry mode to independently assign a unique identity identifier to the brand and its various series of models; designs a method for dynamic identity authentication based on the identity identifiers of each party when jumping between H5 pages of multiple platforms, and uses the private keys and public keys of both parties to encrypt and verify the transmission data; generates a dynamic token through a key to authenticate the requests of both parties, ensure the security of data communication, and realize request identity authentication based on multi-platform jumps, ensuring that the flexible access to a unified operation platform for multi-brand three-party systems can be supported, thereby ensuring the realization of a one-stop service model for car selection, car purchase, insurance purchase, and registration and number selection. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 This is a structural diagram of the unified operation platform; Figure 2 For business process diagram; Figure 3 This is the authToken token authentication flow chart. DETAILED DESCRIPTION

[0008] like Figure 1~Figure 3 As shown, the flexible access mechanism and dynamic identity authentication method for multi-brand H5 pages in this application are characterized by supporting flexible access to multi-brand third-party systems, dynamically allocating identity identifiers based on each brand series product, and used in subsequent page interaction processes to verify the identity information of both parties and ensure data interaction security. Specifically, this application includes a flexible access mechanism and dynamic identity authentication method for multi-brand H5 pages, which includes the following steps.

[0009] S1: Build a unified operation platform and dedicated APP; The unified operation platform includes: car enterprise brand management module, car purchase management module and public service management module; The car company brand management module manages all connected car companies and products; the car purchase management module manages the purchase process; the public service management module manages all aspects of the car purchase process other than purchase; The dedicated APP serves as a client, providing car buyers with access to a unified operating platform; The brand service end of the car company itself establishes data connection with the unified operation platform; The car purchase page of the unified operation platform and the car purchase page of the brand service end of the car company itself are built based on HTML5 technology. The public service management module includes: access ports related to insurance, taxation and traffic management resources; among them, the pages related to insurance selection are built based on HTML5 (hereinafter referred to as H5) technology. Through the platform settlement method, a flexible access method for the platform H5 page integrating multiple brands is realized.

[0010] This application is approved by Figure 1 The unified operating platform shown in the figure connects the dedicated traffic management APP, automobile manufacturers, and insurance platforms. It uses the dedicated traffic management APP as a container and integrates the H5 pages of automobile manufacturers and insurance brands to achieve a one-stop service model for car selection, car purchase, insurance purchase, registration and number selection.

[0011] S2: Auto brands apply to join the unified operation platform and provide brand registration information; Brand registration information includes: brand information and brand public and private keys; The brand public and private keys are generated by the brand. A pair of public and private keys are generated through the SM2 algorithm: orgPubKey and orgPriKey. The orgPubKey is provided to the platform, and the orgPriKey is held by the brand.

[0012] In specific implementation, the car brand completes the platform account registration through the mobile phone number and verification code. Then, provide the brand registration information as required.

[0013] The brand information includes: brand name, brand icon, brand introduction, brand service description, brand domain name, contact person, contact number, contact email, and city. After the brand information is complete, submit it to the backend for review.

[0014] S3: The unified operation platform reviews the brand registration information; after the review is passed, the system automatically generates the unique authentication code orgCode and platform public key of the registered brand; The platform public key is generated by the platform, and a pair of public and private keys are generated through the SM2 algorithm: sitePubKey and sitePriKey. The sitePubKey is provided to the brand, and the sitePriKey is held by the platform.

[0015] S4: Car companies register their brands for products; The unified operation platform assigns a unique model code orgProdCode to each brand product.

[0016] This application uses an identity allocation mechanism to designate a method based on the car company brand entry model to independently allocate a unique identity to the brand and its various series of models.

[0017] Brand staff use their mobile phone number and verification code to log in to the operation platform, enter the car company brand product registration page, and enter the model parameters launched on the platform. The operation platform automatically assigns the brand product unique model code orgProdCode based on each model parameter. See Table 1 for details.

[0018] Table 1: Example of vehicle model registration form S6: Car brands synchronize the specific vehicle parameters of each model to the unified operation platform through the public interface opened by the platform in accordance with the interface access specifications; each time data is written, authentication information is included; The authentication information includes: brand authentication code orgCode, vehicle model code orgProdCode, timestamp timestamp and signature sign JSON string, and the JSON string is encrypted and transmitted using sitePubKey.

[0019] Vehicle parameters include: length, width, height, curb weight, acceleration from 0 to 100 km / h, etc.

[0020] Among them, the signature generation rule is: concatenate siteCode, siteProdCode, and timestamp in the following format and use orgPriKey to sign the summary. The concatenation rules are as follows: orgCode=Brand certification code#orgProdCode=Model code#timestamp=Timestamp.

[0021] S7: After receiving the vehicle parameters pushed by the car brand, the unified operation platform first decrypts the authentication information using sitePriKey and verifies the signature using orgPubKey. After the signature verification is passed, check whether siteCode and siteProdCode have been registered on the platform and whether the product is online normally. After all the verifications are passed, the vehicle parameters are received; The unified operation platform confirms the received vehicle model parameters. Once confirmed to be correct, it is publicly released to the platform and synchronized to the relevant car purchase section of the dedicated APP.

[0022] Among them, the unified operation platform confirms the received vehicle model parameters, including: the operation platform staff checks whether the model parameters pushed by the car company are consistent with the car announcement parameters, and releases the model if confirmed to be correct.

[0023] S8: Car buyers access the car purchase section based on a dedicated APP. After selecting a car model and placing an order, they are redirected to the car purchase page on the brand service end.

[0024] In specific implementation, after the user logs in to the APP and enters the car life section, he can select the vehicle brand and view the relevant vehicle parameters of all the models released under the brand, and can select 1-3 models for parameter comparison. After the user selects the model, he will jump to the car company's car purchase H5 page.

[0025] Before the jump, the unified operation platform generates the order number orderId, the identity authentication token authToken and the page token information jsApiToken, and caches them in Redis. In this embodiment, the expiration time is set to 5 minutes and 15 minutes for the two tokens respectively.

[0026] In this application, an identity authentication token authToken is dynamically generated, combined with a unique identity identifier assigned to the brand and model, to form a dynamic identity identifier. Together with the public keys held by both parties, a dynamic identity authentication method is constructed to authenticate the H5 page data jumped by both parties, effectively improving the security of data transmission.

[0027] Among them, the page token information jsApiToken is used for the page token authentication information when the car purchase page on the subsequent brand server jumps back to the unified operation platform H5 page; the authentication information is generated by the unified operation platform and passed when jumping to the car purchase page on the brand server. The page token information jsApiToken generation rules: include the orgCode brand authentication code, orgProdCode vehicle model code, userId user account, timestamp (timestamp), generate a JSON string jsApiTokenBean, and use the SM2 algorithm + sitePubKey to encrypt it to obtain the ciphertext jsApiToken.

[0028] jsApiTokenBean: { "orgCode": "001", "orgProdCode": "CAA0701", "userId": "xxxx", "timestamp": 122999999 }.

[0029] The identity authentication token authToken is used to carry the platform authentication information when the car purchase page of the unified operation platform jumps to the car purchase page of the brand server. It is generated by the unified operation platform and passed when jumping to the car purchase page on the brand server. Identity authentication token authToken generation rules: It will contain orgCode brand authentication code, userId user account, orderId order number, orgProdCode vehicle model code, timestamp timestamp, jsApiToken page token, signature summary, generate JSON string authTokenBean, and use SM2 algorithm + orgPubKey to encrypt it to get the ciphertext authToken.

[0030] Summary signature generation rules: concatenate the strings in the following format to get signatureStr, and use sitePriKey to perform summary to get signature; orgCode=Brand authentication code# userId=User account# timestamp=Timestamp# jsApiToken=Page token.

[0031] authTokenBean:{ "orgCode": "001", "userId": "xxxx", "orderId": "xxxx", "orgProdCode": "CAA0701", "timestamp": 122999999, "jsApiToken": "ababcbcdbbaebacaa", "signature": "aabbabdaaba123424" }.

[0032] After the user selects the model, he / she will be redirected to the car purchase H5 page of the car company's brand service end. On the car purchase page of the brand service end, the user can select the specific model and optional products. The car purchase page will simultaneously display the relevant discounts and value-added services provided by the model. After the user selects the model, he / she will click to place an order and pay the deposit. The user can pay the deposit only after the brand service end verifies the authToken.

[0033] The brand server verifies the authToken by following these steps: a1: Use orgPriKey to decrypt authToken and obtain the plain text of orgCode, userId, timestamp, jsApiToken and signature. a2: After decryption is successful, first verify whether the signature exists in Redis; If it already exists, it is considered that the request has been received and the error prompt page is displayed; If the signature does not exist, go to step a3; a3: Get signatureStr according to the signature generation rule, and verify the signature through SM2+sitePubKey. After the signature verification is passed, verify whether the timestamp is within the preset 5-minute validity period; if it is within the time limit, enter the car company's car purchase and order H5 page, and cache the signature to Redis to prevent multiple calls or disguised calls to the page.

[0034] S9: After the user pays the deposit, the brand service end will send the generated car purchase order details back to the unified operation platform through the interface. After the unified operation platform returns a successful response, the car company's brand service end order page will display a successful order and display a return button; When the user clicks the back button, the brand server H5 page jumps back to the order progress H5 page of the unified operation platform and carries the page token information jsApiToken information.

[0035] S10: After receiving the callback request, the unified operation platform verifies the legitimacy of jsApiToken. After all verifications are passed, the order information is written to complete the car purchase process. The unified operation platform verifies the legitimacy of jsApiToken, which specifically includes the following steps: b1: Get the jsApiToken from the local cache and check whether it exists; If it exists, decrypt the jsApiToken information through sitePriKey to obtain userId (user account), orderId (order number), orgProdCode (car model code), and timestamp (timestamp); b2: Execute all the following confirmations: Check whether userId and orderId exist on this platform; Check whether the model is consistent with the order information; Check whether the timestamp is within the preset 15-minute validity period; After all verifications are passed, the order information is written, otherwise the error page is entered.

[0036] S11: The user completes other related processes of car purchase based on the public service management module.

[0037] This application designs a dynamic identity authentication method. When jumping between H5 pages of multiple platforms, it is based on the identity identification of each party, and uses the private key held by each party and the public key of the other party to encrypt and verify the transmitted data, thus realizing a dynamic identity authentication method. Identity authentication process In order to ensure the data interaction security during the three-party brand integration process, when the platform interacts with the three parties, it generates a dynamic token (identity authentication token authToken and page token information jsApiToken) through a key, thereby authenticating the requests of both parties and ensuring the security of data communication After using the technical solution of the present invention, it can effectively solve the current problem. The method mainly explains how to access multiple platforms from the aspects of third-party brand platform entry, product data synchronization, car viewing, and order placement, as well as how to perform identity authentication after the H5 pages jump to each other. It is suitable for the dedicated traffic management APP released by the traffic management department to integrate the third-party platform to realize business processing.

Claims

1. A flexible access mechanism and dynamic identity authentication method for multi-brand H5 pages, characterized in that: It includes the following steps: S1: Build a unified operation platform and dedicated APP; The unified operation platform includes: a car enterprise brand management module, a car purchase management module and a public service management module; The car enterprise brand management module manages all connected car enterprises and products; the car purchase management module manages the purchase process of the car; the public service management module manages all links other than the purchase process of the car purchase; The dedicated APP acts as a client to provide car buyers with an entrance to the unified operating platform; The brand service end of the automobile enterprise brand establishes data connection with the unified operation platform; The car purchase page of the unified operation platform and the car purchase page of the brand service end of the car enterprise brand itself are both built based on HTML5 technology; S2: Automobile enterprise brands apply to enter the unified operation platform and provide brand registration information; The brand registration information includes: brand information and brand public and private keys; The brand public and private keys are generated by the brand party, and a pair of public and private keys are generated through the SM2 algorithm: orgPubKey and orgPriKey. The orgPubKey is provided to the platform party, and the orgPriKey is held by the brand party; S3: The unified operation platform reviews the brand registration information; after the review is passed, the system automatically generates the unique authentication code orgCode and platform public key of the registered brand; The platform public key is generated by the platform, and a pair of public and private keys are generated through the SM2 algorithm: sitePubKey and sitePriKey. The sitePubKey is provided to the brand, and the sitePriKey is held by the platform. S4: Car companies register their brands for products; The unified operation platform assigns a unique model code orgProdCode to each brand product; S6: The car brand synchronizes the specific vehicle parameters of each model to the unified operation platform through the public interface opened by the platform in accordance with the interface access specification; each time data is written, authentication information is included; The authentication information includes: brand authentication code orgCode, vehicle model code orgProdCode, timestamp timestamp and signature sign JSON string, and the JSON string is encrypted and transmitted using sitePubKey; S7: After receiving the vehicle model parameters pushed by the car enterprise brand, the unified operation platform first decrypts the authentication information using sitePriKey and verifies the signature using orgPubKey. After the signature verification is passed, check whether siteCode and siteProdCode have been registered in the platform and whether the product is online normally. After all the verifications are passed, the vehicle model parameters are received; The unified operation platform confirms the received vehicle model parameters, and after confirmation, publishes them to the platform and synchronizes them to the relevant car purchase section of the dedicated APP; S8: The car purchasing user accesses the car purchasing section based on the dedicated APP, selects a car model and places an order, and then jumps to the car purchasing page on the brand service end; Before the jump, the unified operation platform generates the order number orderId, the identity authentication token authToken and the page token information jsApiToken, and caches them in Redis; The page token information jsApiToken is used for the page token authentication information carried when the car purchase page on the brand server jumps back to the unified operation platform H5 page; the authentication information is generated by the unified operation platform and passed when jumping to the car purchase page on the brand server; The identity authentication token authToken is used to carry the platform authentication information when the unified operation platform car purchase page jumps to the car purchase page on the brand service end; it is generated by the unified operation platform and passed when jumping to the car purchase page on the brand service end; After the brand server verifies the authToken, the user pays the deposit; S9: After the user pays the deposit, the brand server will send the generated car purchase order details back to the unified operation platform through the interface. After the unified operation platform returns a successful response, the brand server's order page will display a successful order. When the user clicks the back button, the brand server H5 page jumps back to the unified operation platform's order progress H5 page, carrying the page token information jsApiToken information; S10: After receiving the callback request, the unified operation platform verifies the legitimacy of jsApiToken. After all verifications are passed, the order information is written to complete the car purchase process. S11: The user completes other relevant processes of car purchase based on the public service management module.

2. According to claim 1, a flexible access mechanism and dynamic identity authentication method for multi-brand H5 pages, characterized in that: The public service management module includes: access ports related to insurance, taxation and traffic management resources; wherein, pages related to insurance purchase are constructed based on HTML5 technology.

3. According to claim 1, a flexible access mechanism and dynamic identity authentication method for multiple brand H5 pages, characterized in that: The page token information jsApiToken generation rules: include the orgCode brand authentication code, orgProdCode vehicle model code, userId user account, and timestamp to generate a JSON string jsApiTokenBean, and use the SM2 algorithm + sitePubKey to encrypt it to obtain the ciphertext jsApiToken.

4. According to claim 1, a flexible access mechanism and dynamic identity authentication method for multiple brand H5 pages, characterized in that: The identity authentication token authToken generation rule is as follows: the orgCode brand authentication code, userId user account, orderId order number, orgProdCode vehicle model code, timestamp timestamp, jsApiToken page token, and signature summary are included to generate a JSON string authTokenBean, and it is encrypted using the SM2 algorithm + orgPubKey to obtain the ciphertext authToken.

5. According to claim 4, a flexible access mechanism and dynamic identity authentication method for multiple brand H5 pages, characterized in that: The summary signature generation rule is: concatenate the strings in the following format to get signatureStr, and use sitePriKey to perform summary to get signature; orgCode=brand authentication code# userId=user account# timestamp=timestamp# jsApiToken=page token; In step S6, the signature generation rule is: concatenate siteCode, siteProdCode, and timestamp in the following format and use orgPriKey to perform a digest signature. The concatenation rule is as follows: orgCode=Brand certification code#orgProdCode=Model code#timestamp=Timestamp.

6. According to claim 1, a flexible access mechanism and dynamic identity authentication method for multiple brand H5 pages, characterized in that: In step S8, the brand server verifies authToken by the following steps: a1: Use orgPriKey to decrypt authToken and obtain the plain text of orgCode, userId, timestamp, jsApiToken and signature. a2: After decryption is successful, first verify whether the signature exists in Redis; If it already exists, it is considered that the request has been received and the error prompt page is displayed; If the signature does not exist, go to step a3; a3: Get signatureStr according to the signature generation rule, and verify the signature through SM2+sitePubKey. After the signature verification is passed, verify whether the timestamp is within the preset time limit; if it is within the time limit, enter the car company's car purchase and order H5 page, and cache the signature to Redis.

7. According to claim 1, a flexible access mechanism and dynamic identity authentication method for multiple brand H5 pages, characterized in that: In step S10, the unified operation platform verifies the legitimacy of jsApiToken, which specifically includes the following steps: b1: Get the jsApiToken from the local cache and check whether it exists; If it exists, decrypt the jsApiToken information through sitePriKey to obtain userId (user account), orderId (order number), orgProdCode (car model code), and timestamp (timestamp); b2: Execute all the following confirmations: Check whether userId and orderId exist on this platform; Check whether the model is consistent with the order information; Check whether the timestamp is within the preset time limit.

Images