Verification seal taking method, system and equipment and medium
By employing a multi-factor verification method for seal retrieval, the risk of unauthorized access caused by single-factor verification in existing technologies is resolved. This achieves security and differentiated authorization for electronic seals, meeting the dynamic verification needs of multiple business scenarios.
Patent Information
- Application Number
- CN202511245901.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-09-02
- Publication Date
- 2025-11-21
AI Technical Summary
The current electronic seal retrieval process only verifies a single factor such as user identity or application permissions, which poses a risk of unauthorized access and fails to meet the dynamic verification needs of multiple business scenarios.
The system obtains the application identifier, user identifier, public key certificate, and current timestamp through the user terminal, concatenates them into the original signature text, performs digital signing using the signing private key, and sends the signature value to the seal management module. The seal management module parses the public key certificate and verifies the signature value using the signing public key, determines whether the timestamp range, certificate serial number, application identifier, and user identifier meet the preset conditions, and returns the target seal after multiple verifications.
It implements multiple security verifications, improves the security of stamp retrieval, and supports differentiated authorization for different business systems by different users, meeting the growing application needs.
Smart Images
Figure CN120995510A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of electronic seal security, in particular to a verification method, system, device and medium. BACKGROUND
[0002] The existing electronic seal taking process only verifies single factors such as user identity or application permission, and the risk of illegal calling is high. Moreover, the current technology does not consider the dynamic verification demand of multi-business scenarios, and does not support combined verification according to different user and different business system scenarios. SUMMARY
[0003] Therefore, the present application aims to overcome the deficiencies in the prior art and provide a verification method, system, device and medium. The present application provides the following technical solutions: In a first aspect, the present application provides a verification method for a verification seal system, wherein the verification seal system comprises a user terminal and a seal management module. The method comprises the following steps: The user terminal acquires an application identifier, a user identifier, a public key certificate and a current timestamp, concatenates the application identifier, the user identifier, the public key certificate and the current timestamp to obtain a signature original text; The signature original text is digitally signed using a signature private key to obtain a signature value; The application identifier, the user identifier, the public key certificate, the current timestamp and the signature value are sent to the seal management module; The public key certificate is parsed by the seal management module to obtain a signature public key and a certificate serial number; The signature value is verified using the signature public key. If the verification is passed, it is determined whether the current timestamp belongs to a preset service time range. If it belongs, the target seal is acquired according to the certificate serial number; It is sequentially determined whether the certificate serial number meets a first preset condition, whether the application identifier meets a second preset condition, and whether the user identifier meets a third preset condition. If all the conditions are met, the target seal is returned to the user terminal.
[0004] In an optional embodiment, the determination of whether the certificate serial number meets the first preset condition comprises: The preset sequence list is traversed to determine whether the certificate serial number belongs to the preset sequence list. If it belongs, it is determined that the certificate serial number meets the first preset condition. The preset sequence list stores a plurality of authorized certificate serial numbers; If it does not belong, an error information is returned to the user terminal.
[0005] In an optional implementation, the determining whether the application identifier meets the second preset condition comprises: traversing an application authorization relationship table to determine whether the application identifier belongs to the application authorization relationship table, and if yes, determining that the application identifier meets the second preset condition, wherein the application authorization relationship table comprises a plurality of authorized application identifiers; if not, returning the error information to the user terminal.
[0006] In an optional implementation, the determining whether the user identifier meets the third preset condition comprises: traversing a user authorization relationship table to determine whether the user identifier belongs to the user authorization relationship table, and if yes, determining that the user identifier meets the third preset condition, wherein the user authorization relationship table comprises a plurality of authorized user identifiers; if not, returning the error information to the user terminal.
[0007] In an optional implementation, the verifying the signature value using the signature public key comprises: decrypting the signature value using the signature public key to obtain a hash value of the signature plaintext; re-splicing the application identifier, the user identifier, the public key certificate, and the current timestamp to obtain a plaintext to be verified; obtaining a hash value to be verified of the plaintext to be verified, and determining whether the hash value to be verified is consistent with the hash value, and if yes, determining that the verification is passed.
[0008] In an optional implementation, after the obtaining the target seal according to the certificate serial number, the method further comprises: obtaining a current state of the target seal, and determining whether the current state is an available state, and if not, returning error information to the user terminal.
[0009] In an optional implementation, the method further comprises: if the current timestamp does not belong to the preset service time range, returning the error information to the user terminal.
[0010] In a second aspect, the application provides a seal checking system, which comprises: a user terminal configured to obtain an application identifier, a user identifier, a public key certificate, and a current timestamp, and splice the application identifier, the user identifier, the public key certificate, and the current timestamp to obtain a signature plaintext; performing digital signature on the signature plaintext using a signature private key to obtain a signature value; sending the application identifier, the user identifier, the public key certificate and the signature value to a seal management module; The seal management module is configured to parse the public key certificate to obtain a signature public key and a certificate serial number. The signature value is verified using the signature public key, and if the verification is passed, it is determined whether the current timestamp belongs to a preset service time range, and if it belongs, a target seal is obtained according to the certificate serial number. It is sequentially determined whether the certificate serial number satisfies a first preset condition, whether the application identifier satisfies a second preset condition, and whether the user identifier satisfies a third preset condition, and if all the conditions are satisfied, the target seal is returned to the user terminal.
[0011] In a third aspect, the present application provides an electronic device including a memory and a processor, the memory storing a computer program, the computer program being executed on the processor to implement the verification and seal obtaining method of any one of the preceding embodiments. In a fourth aspect, the present application provides a computer readable storage medium storing a computer program, the computer program being executed on a processor to implement the verification and seal obtaining method of any one of the preceding embodiments.
[0012] The verification and seal obtaining method, system, device and medium provided by the embodiments of the present application obtain an application identifier, a user identifier, a public key certificate and a current timestamp through the user terminal, splice the application identifier, the user identifier, the public key certificate and the current timestamp to obtain a signature original text, use a signature private key to digitally sign the signature original text to obtain a signature value, send the application identifier, the user identifier, the public key certificate, the current timestamp and the signature value to the seal management module, the seal management module parses the public key certificate to obtain a signature public key and a certificate serial number, the signature value is verified using the signature public key, if the verification is passed, it is determined whether the current timestamp belongs to a preset service time range, if it belongs, a target seal is obtained according to the certificate serial number, it is sequentially determined whether the certificate serial number satisfies a first preset condition, whether the application identifier satisfies a second preset condition, and whether the user identifier satisfies a third preset condition, and if all the conditions are satisfied, the target seal is returned to the user terminal, realizing multiple security verification, improving the seal security, realizing the differentiated authorization of different users to different business systems, and meeting the current growing application demand.
[0013] In order to make the above objectives, features and advantages of the present application more apparent and easy to understand, the following preferred embodiments are described in detail below, and the accompanying drawings are described as follows. BRIEF DESCRIPTION OF DRAWINGS
[0014] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments. It should be understood that the following drawings only show some of the embodiments of the present application, and therefore should not be considered as limiting the scope. For those skilled in the art, other related drawings can also be obtained without creative labor.
[0015] Figure 1 A flowchart of a seal checking and stamping method provided by an embodiment of the present application is shown; Figure 2 A structural diagram of a seal checking and stamping system provided by an embodiment of the present application is shown; Figure 3 Another flowchart of a seal checking and stamping method provided by an embodiment of the present application is shown; Figure 4 A structural diagram of an electronic device provided by an embodiment of the present application is shown.
[0016] Main element symbol explanation: 200 - seal checking and stamping system; 210 - user terminal; 220 - seal management module; 400 - electronic device; 401 - transceiver; 402 - processor; 403 - memory. DETAILED DESCRIPTION
[0017] The embodiments of the present application will be described in detail below, examples of which are shown in the drawings, wherein the same or similar notations represent the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the drawings are exemplary and are only used to explain the present application, and cannot be understood as limiting the present application.
[0018] In addition, the terms "first", "second" are only for the purpose of description, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined with "first", "second" can explicitly or implicitly include one or more of the features. In the description of the present application, the meaning of "a plurality of" is two or more, unless otherwise specifically limited.
[0019] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present application belongs. The terms used in the specification of the template herein are only for the purpose of describing specific embodiments and are not intended to limit the present application. The term "and / or" used herein includes any and all combinations of one or more of the related listed items.
[0020] Embodiment 1 In the prior art, only a single factor such as user identity or application permission needs to be verified in the electronic seal taking process, and there is a risk of illegal calling. For this, please refer to Figure 1 Embodiments of the present application provide a verification method for taking a seal, which is applied to a verification seal taking system 200 as shown in Figure 2 The verification seal taking system 200 includes a user terminal 210 and a seal management module 220, and the method includes steps S110-S160.
[0021] In step S110, the user terminal 210 acquires an application identifier, a user identifier, a public key certificate, and a current timestamp, concatenates the application identifier, the user identifier, the public key certificate, and the current timestamp to obtain a signature original text.
[0022] In this embodiment, the application identifier refers to the interfacing application identifier that needs to call the electronic seal; the user identifier refers to the unique identifier of the seal person, which is used to accurately locate the specific user who initiates the seal taking operation; the public key certificate needs to be read from the UKEY hardware device after the seal person inserts the universal key (UKEY) into the user terminal 210 and inputs the correct UKEY password, and the public key certificate includes the signature public key paired with the UKEY private key and the unique certificate serial number. The application identifier, the user identifier, the public key certificate, and the current timestamp are concatenated into a continuous string, which is the signature original text.
[0023] In step S120, the signature original text is digitally signed using a signature private key to obtain a signature value.
[0024] In this embodiment, the seal person needs to insert the UKEY certificate and input the correct UKEY password first to unlock the signature private key stored in the UKEY, and the signature private key and the signature public key in the public key certificate used for subsequent verification are in a paired relationship, and then the signature private key is used to encrypt the signature original text to obtain the signature value.
[0025] In step S130, the application identifier, the user identifier, the public key certificate, the current timestamp, and the signature value are sent to the seal management module 220.
[0026] Specifically, the application identifier, the user identifier, the public key certificate, the current timestamp, and the signature value are used as input parameters to call the seal taking interface and transmitted to the seal management module 220.
[0027] In step S140, the seal management module 220 parses the public key certificate to obtain the signature public key and the certificate serial number.
[0028] In the embodiment, the seal management module 220 extracts information from the public key certificate according to the electronic certificate parsing specification, parses the signature public key paired with the signature private key, and the certificate number corresponding to the public key certificate, i.e., the unique identifier of the certificate.
[0029] In step S150, the signature value is verified using the signature public key. If the verification is passed, it is determined whether the current timestamp belongs to the preset service time range. If it belongs, the target seal is obtained according to the certificate serial number.
[0030] In the embodiment, the signature value is first verified by the signature public key. After the verification is passed, the current timestamp is also checked to determine whether the current timestamp is within the preset service time range, so as to prevent repeated requests.
[0031] In an embodiment, referring to Figure 3 , the signature value is verified using the signature public key, including steps S151-S153.
[0032] In step S151, the signature value is decrypted using the signature public key to obtain the hash value of the signature original text.
[0033] In the embodiment, signing the signature original text using the signature private key means that the hash value of the signature original text is first calculated, and then the hash value is encrypted using the signature private key to obtain the signature value. Therefore, after the signature value is decrypted using the signature public key paired with the signature private key, the hash value of the signature original text is obtained.
[0034] In step S152, the application identifier, the user identifier, the public key certificate, and the current timestamp are re-spliced to obtain the to-be-verified original text.
[0035] It can be understood that, in order to verify whether data is lost or changed during transmission, the obtained application identifier, user identifier, public key certificate, and current timestamp need to be re-spliced into the to-be-verified original text. The hash value of the to-be-verified original text is compared with the hash value of the signature original text to determine whether the obtained data is reliable.
[0036] In step S153, the to-be-verified hash value of the to-be-verified original text is obtained, and it is determined whether the to-be-verified hash value is consistent with the hash value. If they are consistent, it is determined that the verification is passed.
[0037] It can be understood that if they are completely consistent, it indicates that the application identifier, user identifier, public key certificate and current timestamp obtained by the seal management module 220 are not tampered with in the transmission process, and the signature value is generated by the signature private key paired with the current signature public key. Since only the signature value encrypted by the legal private key can be decrypted by the corresponding signature public key to obtain the original hash value consistent with the hash value to be verified, it is determined that the signature value verification is passed. If they are not consistent, it indicates that the request is tampered with or illegally generated, the signature verification fails, and the seal taking process is terminated.
[0038] In step S160, it is judged in sequence whether the certificate serial number meets the first preset condition, whether the application identifier meets the second preset condition, and whether the user identifier meets the third preset condition. If all of them meet, the target seal is returned to the user terminal 210.
[0039] In the embodiment, after determining the target seal according to the certificate serial number, the certificate serial number, the application identifier and the user identifier need to be checked in sequence, and the return operation of the target seal is triggered when the multiple checks are passed. It can be understood that through the multiple security verifications, the security of seal taking is improved, and at the same time, the differentiated authorization of different users to different business systems is realized, which meets the increasing application requirements.
[0040] In an embodiment, the judgment of whether the certificate serial number meets the first preset condition comprises: traversing a preset sequence list to judge whether the certificate serial number belongs to the preset sequence list. If it belongs, it is determined that the certificate serial number meets the first preset condition. The preset sequence list stores a plurality of authorized certificate serial numbers. If it does not belong, an error information is returned to the user terminal 210.
[0041] In the embodiment, the preset sequence list is generated or updated when the user applies for a UKEY and handles the UKEY seal binding. A plurality of authorized certificate serial numbers are pre-stored in the preset sequence list. By traversing all the certificate serial numbers in the preset sequence list, the parsed certificate serial number is compared with the authorized serial numbers stored in the preset sequence list one by one. If there is a complete matching record, it is determined that the certificate serial number meets the first preset condition. If there is no matching item after the traversal ends, an error information is generated and fed back to the user terminal 210, and the subsequent seal taking process is terminated.
[0042] It can be understood that the preset sequence list only includes authorized serial numbers, which can quickly exclude seal taking requests corresponding to UKEYs that are not registered in the seal management platform, have been invalidated, such as revoked or expired UKEYs, and make up for the vulnerability of the prior art single-factor verification that cannot identify illegal UKEYs.
[0043] In an embodiment, the determining whether the application identifier satisfies the second preset condition comprises: traversing an application authorization relationship table to determine whether the application identifier belongs to the application authorization relationship table, if yes, determining that the application identifier satisfies the second preset condition, the application authorization relationship table comprising a plurality of authorized application identifiers; and if no, returning the error information to the user terminal 210.
[0044] In the embodiment, the application authorization relationship table stores a plurality of authorized application identifiers, and all authorized application identifiers bound to the target seal in the application authorization relationship table are traversed to compare the obtained application identifier with the record in the application authorization relationship table one by one to determine whether they are consistent; if there is a mapping relationship between the target seal and the current application identifier, it is determined that the application identifier satisfies the second preset condition; if there is no corresponding matching item after the traversal ends, it indicates that the current docking application does not obtain the use authorization of the target seal, and then an error information is generated and fed back to the user terminal 210, and the subsequent seal taking process is terminated. In an embodiment, the determining whether the user identifier satisfies the third preset condition comprises: traversing the user authorization relationship table to determine whether the user identifier belongs to the user authorization relationship table, if yes, determining that the user identifier satisfies the third preset condition, the user authorization relationship table comprising a plurality of authorized user identifiers; and if no, returning the error information to the user terminal 210.
[0045] In the embodiment, the user authorization relationship table stores a plurality of authorized user identifiers, and all authorized user identifiers bound to the target seal in the user authorization relationship table are traversed to compare the user identifier with the record in the user authorization relationship table one by one to determine whether they are consistent; if there is a mapping relationship between the target seal and the current user identifier, it is determined that the user identifier satisfies the third preset condition; if there is no corresponding matching item after the traversal ends, it indicates that the current seal person does not obtain the use authorization of the target seal, and then an error information is generated and fed back to the user terminal 210, and the subsequent seal taking process is terminated.
[0046] In an embodiment, after the target seal is obtained according to the certificate serial number, the method further comprises: obtaining a current state of the target seal, and determining whether the current state is an available state, if no, returning an error information to the user terminal 210.
[0047] In the embodiment, after locating the target seal through the certificate serial number, the seal management module 220 calls the latest state data of the target seal, and judges whether the current state of the target seal is an available state. Only when the state of the target seal is marked as available (i.e. not disabled, not expired, and not handled for cancellation), the subsequent authorization verification link is entered; if the state is a non-available state such as disabled, expired, or cancelled, an error message is returned to the user terminal 210, and the subsequent seal taking process is terminated to avoid the continuation of invalid verification.
[0048] In an embodiment, the method further comprises: if the current timestamp does not belong to the preset service time range, returning the error message to the user terminal 210.
[0049] In the embodiment, the preset service time range is a time interval that is pre-configured and allows the seal taking request to take effect, and is used to define the effective duration of the request. If the current timestamp exceeds the preset service range, the current timestamp is determined to be invalid, and an error message is returned to the user terminal 210, thereby avoiding the reuse of expired requests.
[0050] The verification seal taking method provided in the embodiments of the application comprises the following steps: the user terminal 210 acquires an application identifier, a user identifier, a public key certificate, and a current timestamp, splices the application identifier, the user identifier, the public key certificate, and the current timestamp to obtain a signature original text; a signature private key is used to digitally sign the signature original text to obtain a signature value; the application identifier, the user identifier, the public key certificate, the current timestamp, and the signature value are sent to the seal management module 220; the seal management module 220 parses the public key certificate to obtain a signature public key and a certificate serial number; the signature public key is used to verify the signature value. If the verification is passed, it is judged whether the current timestamp belongs to a preset service time range. If it belongs, a target seal is acquired according to the certificate serial number; it is sequentially judged whether the certificate serial number satisfies a first preset condition, whether the application identifier satisfies a second preset condition, and whether the user identifier satisfies a third preset condition. If all of them are satisfied, the target seal is returned to the user terminal 210, multiple security verifications are realized, the seal taking security is improved, and the differentiated authorization of different users to different business systems is realized, which meets the current growing application requirements.
[0051] Embodiment 2 In addition, please refer again to Figure 2 The verification seal taking system 200 provided in the embodiments of the application comprises: The user terminal 210 is configured to acquire an application identifier, a user identifier, a public key certificate, and a current timestamp, splice the application identifier, the user identifier, the public key certificate, and the current timestamp to obtain a signature original text, use a signature private key to digitally sign the signature original text to obtain a signature value, and send the application identifier, the user identifier, the public key certificate, and the signature value to the seal management module 220. The seal management module 220 is configured to parse the public key certificate to obtain a signature public key and a certificate serial number, use the signature public key to verify the signature value, if the verification is passed, determine whether the current timestamp belongs to a preset service time range, if yes, acquire a target seal according to the certificate serial number, and in sequence, determine whether the certificate serial number satisfies a first preset condition, whether the application identifier satisfies a second preset condition, and whether the user identifier satisfies a third preset condition, and if all the conditions are satisfied, return the target seal to the user terminal 210.
[0052] In an embodiment, the determination of whether the certificate serial number satisfies the first preset condition comprises: traversing a preset serial list to determine whether the certificate serial number belongs to the preset serial list, if yes, it is determined that the certificate serial number satisfies the first preset condition, and the preset serial list stores a plurality of authorized certificate serial numbers; and if not, an error information is returned to the user terminal 210.
[0053] In an embodiment, the determination of whether the application identifier satisfies the second preset condition comprises: traversing an application authorization relationship table to determine whether the application identifier belongs to the application authorization relationship table, if yes, it is determined that the application identifier satisfies the second preset condition, and the application authorization relationship table includes a plurality of authorized application identifiers; and if not, the error information is returned to the user terminal 210.
[0054] In an embodiment, the determination of whether the user identifier satisfies the third preset condition comprises: traversing the user authorization relationship table to determine whether the user identifier belongs to the user authorization relationship table, if yes, it is determined that the user identifier satisfies the third preset condition, and the user authorization relationship table includes a plurality of authorized user identifiers; and if not, the error information is returned to the user terminal 210.
[0055] In an embodiment, the verification of the signature value using the signature public key comprises: using the signature public key to decrypt the signature value to obtain a hash value of the signature original text, re-splicing the application identifier, the user identifier, the public key certificate, and the current timestamp to obtain a to-be-verified original text, acquiring a to-be-verified hash value of the to-be-verified original text, determining whether the to-be-verified hash value is consistent with the hash value, and if yes, determining that the verification is passed.
[0056] In an embodiment, after obtaining the target seal according to the certificate serial number, the method further comprises: obtaining a current state of the target seal, determining whether the current state is an available state, and if not, returning error information to the user terminal 210.
[0057] In an embodiment, the method further comprises: if the current timestamp does not belong to the preset service time range, returning the error information to the user terminal 210.
[0058] The verification and seal obtaining system 200 provided by the embodiments of the present application can execute the verification and seal obtaining method provided by the method embodiment 1, and thus will not be described here again to avoid repetition.
[0059] The verification and seal obtaining system 200 provided by the embodiments of the present application realizes multiple security verifications, improves the seal security, realizes the differentiated authorization of different users to different business systems, and meets the growing application requirements.
[0060] Embodiment 3 In addition, the embodiments of the present application provide an electronic device 400 comprising a memory 403 and a processor 402, wherein the memory 403 stores a computer program, and the computer program executes the verification and seal obtaining method provided by the embodiment 1 when running on the processor 402.
[0061] Specifically, referring to Figure 4 , the electronic device 400 comprises a transceiver 401, a bus interface, and a processor 402, wherein the processor 402 is configured to: obtain, by the user terminal 210, an application identifier, a user identifier, a public key certificate, and a current timestamp, splice the application identifier, the user identifier, the public key certificate, and the current timestamp to obtain a signature original text, perform digital signature on the signature original text using a signature private key to obtain a signature value, and send the application identifier, the user identifier, the public key certificate, the current timestamp, and the signature value to the seal management module 220; the seal management module 220 analyzes the public key certificate to obtain a signature public key and a certificate serial number, verifies the signature value using the signature public key, and if the verification is passed, determines whether the current timestamp belongs to a preset service time range, and if yes, obtains a target seal according to the certificate serial number; and sequentially determines whether the certificate serial number satisfies a first preset condition, whether the application identifier satisfies a second preset condition, and whether the user identifier satisfies a third preset condition, and if all of them are satisfied, returns the target seal to the user terminal 210.
[0062] In the embodiments of the present application, the electronic device 400 further comprises a memory 403. In Figure 4In particular embodiments, the bus architecture can include any number of interconnecting buses and bridges, and the various circuitry representative of the processor 402 and the memory 403, for example, can be linked through a bus architecture by any number of buses and bridges, for example. The bus architecture can also include a memory-mapped I / O bus for linking various circuitry representative of peripheral devices, voltage regulators, and power management circuitry, among other circuitry, as is well-known in the art. The bus interface provides an interface to the transceiver 401. The transceiver 401 can be a plurality of elements including a transmitter and a receiver for communicating with various other apparatus over a transmission medium. The processor 402 is responsible for managing the bus architecture and general processing, and the memory 403 can store data for use by the processor 402 in executing operations.
[0063] The electronic device 400 provided by the embodiments of the present application can execute the verification and stamping method provided by the method embodiment 1, and thus, details are not described herein again.
[0064] Embodiment 4 In addition, the embodiments of the present application provide a computer readable storage medium, and the computer readable storage medium stores a computer program, and the computer program is executed by a processor to implement the verification and stamping method provided by the embodiment 1.
[0065] In the embodiment, the computer readable storage medium can be a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like.
[0066] The computer readable storage medium provided by the embodiment can implement the verification and stamping method provided by the embodiment 1, and thus, details are not described herein again.
[0067] In all the examples shown and described herein, any specific values should be interpreted as merely exemplary and not as a limitation, and thus, other examples of the example embodiments can have different values.
[0068] It should be noted that like numerals and letters refer to like items throughout the drawings, and thus, once an item is defined in one drawing, it need not be further defined and explained in subsequent drawings.
[0069] The above-described embodiments are merely representative of several embodiments of the present application, and the description is relatively specific and detailed, but should not be understood as limiting the scope of the present application. It should be noted that, for those skilled in the art, several modifications and improvements can be made without departing from the concept of the present application, and these are within the scope of protection of the present application.
Claims
1. A method for verifying a notary method, characterized in that, The application is applied to a check and seal taking system, and the check and seal taking system comprises a user terminal and a seal management module. The user terminal acquires an application identifier, a user identifier, a public key certificate and a current timestamp, splices the application identifier, the user identifier, the public key certificate and the current timestamp to obtain a signature original text; The signature original text is digitally signed by using a signature private key to obtain a signature value; The application identifier, the user identifier, the public key certificate, the current timestamp and the signature value are sent to the seal management module; The public key certificate is parsed by the seal management module to obtain a signature public key and a certificate serial number; The signature value is verified by using the signature public key, and if the verification is passed, it is judged whether the current timestamp belongs to a preset service time range, and if yes, a target seal is acquired according to the certificate serial number; It is judged in sequence whether the certificate serial number satisfies a first preset condition, whether the application identifier satisfies a second preset condition and whether the user identifier satisfies a third preset condition, and if all the conditions are satisfied, the target seal is returned to the user terminal.
2. The method for verifying a seal according to claim 1, wherein, The judgment of whether the certificate serial number satisfies the first preset condition comprises: A preset sequence list is traversed to judge whether the certificate serial number belongs to the preset sequence list, and if yes, it is determined that the certificate serial number satisfies the first preset condition, and the preset sequence list stores a plurality of authorized certificate serial numbers; If not, an error information is returned to the user terminal.
3. The method for verifying a seal according to claim 2, wherein, The judgment of whether the application identifier satisfies the second preset condition comprises: An application authorization relationship table is traversed to judge whether the application identifier belongs to the application authorization relationship table, and if yes, it is determined that the application identifier satisfies the second preset condition, and the application authorization relationship table comprises a plurality of authorized application identifiers; If not, the error information is returned to the user terminal.
4. The method for verifying a chapter stamping according to claim 3, wherein, The judgment of whether the user identifier satisfies the third preset condition comprises: The user authorization relationship table is traversed to judge whether the user identifier belongs to the user authorization relationship table, and if yes, it is determined that the user identifier satisfies the third preset condition, and the user authorization relationship table comprises a plurality of authorized user identifiers; If not, the error information is returned to the user terminal.
5. The method for verifying a chapter stamping according to claim 1, wherein, The verification of the signature value by using the signature public key comprises: The signature value is decrypted by using the signature public key to obtain a hash value of the signature original text; The application identifier, the user identifier, the public key certificate and the current timestamp are spliced to obtain a to-be-verified original text; A to-be-verified hash value of the to-be-verified original text is acquired, and it is judged whether the to-be-verified hash value is consistent with the hash value, and if yes, it is determined that the verification is passed.
6. The method of claim 1-5, wherein, After the target seal is acquired according to the certificate serial number, the current state of the target seal is acquired, and it is judged whether the current state is an available state, and if not, an error information is returned to the user terminal. If the current timestamp does not belong to the preset service time range, the error information is returned to the user terminal.
7. The method of claim 6, wherein, The system comprises: 8. A verification stamp taking system characterized by comprising: A user terminal is configured to acquire an application identifier, a user identifier, a public key certificate and a current timestamp, splice the application identifier, the user identifier, the public key certificate and the current timestamp to obtain a signature original text; perform digital signature on the signature original text using a signature private key to obtain a signature value; send the application identifier, the user identifier, the public key certificate and the signature value to a seal management module; the seal management module is configured to parse the public key certificate to obtain a signature public key and a certificate serial number; verify the signature value using the signature public key, and if the verification is passed, determine whether the current timestamp belongs to a preset service time range, and if yes, acquire a target seal according to the certificate serial number; sequentially determine whether the certificate serial number satisfies a first preset condition, whether the application identifier satisfies a second preset condition, and whether the user identifier satisfies a third preset condition, and if all the conditions are satisfied, return the target seal to the user terminal.
9. An electronic device, comprising: A computer readable storage medium stores a computer program, and the computer program is executed by a processor to implement the verification and seal obtaining method in any one of claims 1-7.
10. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, and the computer program is executed by a processor to implement the verification and seal obtaining method in any one of claims 1-7.