CN112231674A - Skip verification method and system for URL (Uniform resource locator) address and electronic equipment - Google Patents
Skip verification method and system for URL (Uniform resource locator) address and electronic equipment Download PDFInfo
- Publication number
- CN112231674A CN112231674A CN202011125461.3A CN202011125461A CN112231674A CN 112231674 A CN112231674 A CN 112231674A CN 202011125461 A CN202011125461 A CN 202011125461A CN 112231674 A CN112231674 A CN 112231674A
- Authority
- CN
- China
- Prior art keywords
- token
- url address
- encryption
- encrypted
- encrypted token
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012795 verification Methods 0.000 title claims abstract description 59
- 238000000034 method Methods 0.000 title claims abstract description 31
- 230000000977 initiatory effect Effects 0.000 claims description 5
- 238000010200 validation analysis Methods 0.000 claims 1
- 230000009286 beneficial effect Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/33—User authentication using certificates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2137—Time limited access, e.g. to a computer or data
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention relates to a jump verification method, a system and an electronic device of a URL address, which acquire the URL address to be jumped according to login information, when the URL address to be jumped belongs to any subsystem, the token receiving service system initiates an HTTP request to the URL address to be jumped based on the second encrypted token ID according to the token ID generated by the login information, verifying the second encrypted token ID according to the first encrypted token ID, if the second encrypted token ID passes the first encrypted token ID, responding the HTTP request to jump to the URL address to be jumped, and increasing validity verification under the condition of not modifying the main system, the method verifies the access legitimacy of any subsystem through the token ID of the token service system, improves the safety of the subsystem, avoids the problems of system data information leakage and illegal service handling caused by illegal access outside the subsystem, can be transplanted to any WEB engineering for use, and has strong applicability.
Description
Technical Field
The invention relates to the technical field of telecommunication industry, in particular to a method, a system and electronic equipment for skipping verification of a Uniform Resource Locator (URL) address.
Background
At present, a telecom CRM service handling system is decoupled from an original service integration system into a distributed system in the current internet mode, the telecom CRM service handling system, namely all subsystems of a main system, have the capability of providing independent service handling, only after login verification is carried out on a unified interface, and after an operation code is input, the front end of the telecom CRM service handling system, namely the main system, accesses all subsystems such as a score system, a report system and the like according to a Uniform Resource Locator (URL) address configured by the operation code.
Disclosure of Invention
The invention provides a method, a system and electronic equipment for skipping verification of a URL address, aiming at the defects of the prior art.
The technical scheme of the jump verification method of the URL address comprises the following steps:
acquiring a URL address to be jumped according to login information, and receiving a token ID generated by a token service system according to the login information when the URL address to be jumped belongs to any subsystem;
encrypting the token ID according to a first encryption algorithm to generate a first encrypted token ID, and encrypting the token ID according to a second encryption algorithm to generate a second encrypted token ID;
and initiating an HTTP request to the URL address to be jumped based on the second encrypted token ID, verifying the second encrypted token ID according to the first encrypted token ID, and responding to the HTTP request to jump to the URL address to be jumped if the second encrypted token ID passes the first encrypted token ID.
The jump verification method of the URL address has the following beneficial effects:
under the condition that a main system is not modified, the validity check can be added by the URL address jump verification method, and specifically: the validity of access to any subsystem is verified through the token ID of the token service system, the safety of the subsystem is improved, the problems of system data information leakage and illegal service handling caused by illegal access outside the subsystem are solved, and the system can be transplanted to any WEB engineering for use, so that the applicability is high and the expandability is high.
On the basis of the above scheme, the jump verification method for the URL address of the present invention may be further improved as follows.
Further, said verifying said second encrypted token ID from said first encrypted token ID comprises:
decrypting the second encrypted token ID by using a second decryption algorithm corresponding to the second encryption algorithm to obtain a second decrypted token ID;
encrypting the second decryption token ID by using the first encryption algorithm to obtain a third encryption token ID;
and judging whether the first encryption token ID is the same as the third encryption token ID or not so as to determine whether the second encryption token ID passes the verification.
Further, still include: setting a validity period of the first encrypted token ID when the first encrypted token ID is generated;
then, when determining whether the first encrypted token ID is the same as the third encrypted token, the method further includes: verifying whether the current point in time is within a validity period of the first cryptographic token ID.
The beneficial effect of adopting the further scheme is that: through double verification, namely judging whether the first encryption token ID is the same as the third encryption token ID or not and verifying whether the current time point is in the valid period of the first encryption token ID or not, the access legitimacy of any subsystem is further improved and the safety of the subsystem is further improved.
Further, the login information comprises a job number, an operation code, operation time and at least one random code.
The technical scheme of the jump verification system of the URL address comprises the following steps:
the method comprises the steps of obtaining a receiving module, an encryption module and a verification module;
the acquisition receiving module is used for acquiring a URL address to be jumped according to login information, and when the URL address to be jumped belongs to any subsystem, receiving a token ID generated by the token service system according to the login information;
the encryption module is used for encrypting the token ID according to a first encryption algorithm to generate a first encrypted token ID, and encrypting the token ID according to a second encryption algorithm to generate a second encrypted token ID;
the verification module is used for initiating an HTTP request to the URL address to be jumped based on the second encrypted token ID, verifying the second encrypted token ID according to the first encrypted token ID, and responding the HTTP request to jump to the URL address to be jumped if the second encrypted token ID passes the first encrypted token ID.
The jump verification system of the URL address has the following beneficial effects:
under the condition that a main system is not modified, the URL address jump verification system can increase validity verification, and specifically comprises the following steps: the validity of access to any subsystem is verified through the token ID of the token service system, the safety of the subsystem is improved, the problems of system data information leakage and illegal service handling caused by illegal access outside the subsystem are solved, and the system can be transplanted to any WEB engineering for use, so that the applicability is high and the expandability is high.
On the basis of the above scheme, the jump verification system for the URL address of the present invention may be further improved as follows.
Further, the verification module is specifically configured to:
decrypting the second encrypted token ID by using a second decryption algorithm corresponding to the second encryption algorithm to obtain a second decrypted token ID;
encrypting the second decryption token ID by using the first encryption algorithm to obtain a third encryption token ID;
and judging whether the first encryption token ID is the same as the third encryption token ID or not so as to determine whether the second encryption token ID passes the verification.
Further, the encryption module is further configured to: setting a validity period of the first encrypted token ID when the first encrypted token ID is generated;
the checking module is further configured to, when determining whether the first encrypted token ID is the same as the third encrypted token, further include: verifying whether the current point in time is within a validity period of the first cryptographic token ID.
The beneficial effect of adopting the further scheme is that: through double verification, namely judging whether the first encryption token ID is the same as the third encryption token ID or not and verifying whether the current time point is in the valid period of the first encryption token ID or not, the access legitimacy of any subsystem is further improved and the safety of the subsystem is further improved.
Further, the login information comprises a job number, an operation code, operation time and at least one random code.
The technical scheme of the electronic equipment is as follows:
the jump verification method for the URL address comprises a memory, a processor and a program stored in the memory and running on the processor, and is characterized in that the processor executes the program to realize the steps of the jump verification method for the URL address.
The electronic equipment has the following beneficial effects:
validity checks can be added without modifications to the host system, specifically: the validity of access to any subsystem is verified through the token ID of the token service system, the safety of the subsystem is improved, the problems of system data information leakage and illegal service handling caused by illegal access outside the subsystem are solved, and the system can be transplanted to any WEB engineering for use, so that the applicability is high and the expandability is high.
Drawings
Fig. 1 is a schematic flowchart of a jump verification method for URL addresses according to an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a jump verification system for URL addresses according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present invention;
Detailed Description
As shown in fig. 1, a method for verifying a jump of a URL address according to an embodiment of the present invention includes the following steps:
s1, acquiring a URL address to be jumped according to login information, and receiving a token ID generated by the token service system according to the login information when the URL address to be jumped belongs to any subsystem;
s2, encrypting the token ID according to a first encryption algorithm to generate a first encrypted token ID, and encrypting the token ID according to a second encryption algorithm to generate a second encrypted token ID;
s3, initiating an HTTP request to the URL address to be jumped based on the second encryption token ID, checking the second encryption token ID according to the first encryption token ID, and responding the HTTP request to jump to the URL address to be jumped if the second encryption token ID passes the first encryption token ID.
Under the condition that a main system is not modified, the validity check can be added by the URL address jump verification method, and specifically: the validity of access to any subsystem is verified through the token ID of the token service system, the safety of the subsystem is improved, the problems of system data information leakage and illegal service handling caused by illegal access outside the subsystem are solved, and the system can be transplanted to any WEB engineering for use, so that the applicability is high and the expandability is high.
The login information comprises a job number, an operation code, operation time and at least one random code, wherein the random codes such as 1 bit, 3 bits and 6 bits can be generated specifically, the number of the random codes can be set according to actual conditions, and the random codes can be generated by the skip verification method of the URL address or the token service system;
the token service system generates a token ID (token _ ID) according to the job number, the operation code, the operation time and at least one random code, wherein the job number is the job number of a service operator, and the operation time refers to a time point for inputting login information to acquire a URL (uniform resource locator) address to be jumped; the token service system specifically refers to a token-based authentication system;
it can be understood that the subsystems are relative concepts, for example, when the main system is a service handling system of china mobile, the subsystems are a payment system, a telephone fee inquiry system, etc., for example, when the main system is a service handling system of china telecommunication, the subsystems are a payment system, a telephone fee inquiry system, etc., for example, the main system is a service handling system of telecommunication CRM, and the subsystems are a credit system, a report system, etc.;
the first encryption algorithm is an MD5 encryption algorithm, an MD3 encryption algorithm, a 3DES encryption algorithm, or the like, the second encryption algorithm is an MD5 encryption algorithm, an MD3 encryption algorithm, a 3DES encryption algorithm, or the like, and the description is given by taking the example that the first encryption algorithm is an MD5 encryption algorithm and the second encryption algorithm is a 3DES encryption algorithm, specifically:
encrypting the token ID according to the MD5 encryption algorithm to generate a first encrypted token ID and encrypting the token ID according to the 3DES encryption algorithm to generate a second encrypted token ID, then verifying the second encrypted token ID according to the first encrypted token ID, comprising:
s30, decrypting the second encrypted token ID by using a second decryption algorithm corresponding to the second encryption algorithm, namely the 3DES encryption algorithm, to obtain a second decrypted token ID;
s31, encrypting the second decryption token ID by using the first encryption algorithm, namely the MD5 encryption algorithm, so as to obtain a third encryption token ID;
s32, judging whether the first encryption token ID is the same as the third encryption token ID or not, and determining whether the second encryption token ID passes the verification.
The first encrypted token ID can also be stored in a verification information table, whether each encrypted token ID in the verification information table is the same as the third encrypted token or not is judged in a traversing manner, if yes, the second encrypted token ID is verified to be passed, at the moment, an HTTP request is responded to jump to the URL address to be jumped, so that the business process processing is continued, or a page corresponding to the URL address to be jumped is displayed, or the business data processing is continued; if the description content fails, the corresponding description content is returned in the form of a popup frame and the like, the description content includes time, reasons and the like which fail to pass the verification, and the specific description content can be set according to the actual situation, which is not described herein again.
The process of verifying the second encrypted token ID according to the first encrypted token ID may also be in the form of:
s300, decrypting the first encrypted token ID by using a first decryption algorithm corresponding to the first encryption algorithm, namely the MD5 encryption algorithm, so as to obtain a first decrypted token ID;
s310, encrypting the first decryption token ID by using the second encryption algorithm, namely the 3DES encryption algorithm, to obtain a fourth encryption token ID;
s320, determining whether the second encrypted token ID is the same as the fourth encrypted token ID, to determine whether the second encrypted token ID passes verification, specifically:
if the two types of description contents are the same, the verification is passed, at this time, the HTTP request is responded to jump to the URL address to be jumped, if the URL address to be jumped does not pass, the corresponding description contents are returned in the form of a popup box and the like, the description contents comprise time, reasons and the like which do not pass the verification, the specific description contents can be set according to the actual situation, and the detailed description is omitted here.
Preferably, in the above technical solution, the method further comprises: setting a validity period of the first encrypted token ID when the first encrypted token ID is generated;
then, when determining whether the first encrypted token ID is the same as the third encrypted token, the method further includes: verifying whether a current time point is within a validity period of the first cryptographic token ID; then:
s32 specifically includes:
judging whether the first encryption token ID is the same as the third encryption token ID or not, and judging whether the current verification time point is within the validity period of the first encryption token ID or not so as to determine whether the second encryption token ID passes the verification.
The validity period may be a specific time point, for example, the validity period is set to be valid before 12 months and 31 days in 2020, and the validity period may also refer to a time period: if the time is valid within 5 minutes and within 10 minutes, the starting time point can be set as the time for generating the first encryption token ID, for example, the time for generating the first encryption token ID is 12:00, the validity period is 10 minutes, then 12:10 is invalid, the current time point can be understood as the current time point for verifying the validity period, if the current time point is 12:05, the current time point is determined to be within the validity period of the first encryption token ID, and if the current time point is 12:15, the current time point is determined not to be within the validity period of the first encryption token ID; specifically, a countdown may be set to verify whether the current time point is within the validity period of the first encryption token ID;
it can be understood that, when the first encrypted token ID is the same as the third encrypted token ID and whether the current time point is within the validity period of the first encrypted token ID, the verification is considered to be passed, and if any one of the first encrypted token ID and the third encrypted token ID is not passed, the verification is determined to be not passed;
in this embodiment, through double verification, that is, whether the first encrypted token ID is the same as the third encrypted token ID is determined, and whether the current time point is within the validity period of the first encrypted token ID is verified, the validity of access to any subsystem is further improved, and the security of the subsystem is further improved.
In the foregoing embodiments, although the steps are numbered as S1, S2, etc., but only the specific embodiments are given in this application, and those skilled in the art may adjust the execution order of S1, S2, etc. according to the actual situation, which is also within the protection scope of the present invention, and it is understood that some embodiments may include some or all of the above embodiments.
As shown in fig. 2, a system 200 for skipping verification of a URL address according to an embodiment of the present invention includes an obtaining receiving module 210, an encrypting module 220, and a verifying module 230;
the obtaining and receiving module 210 is configured to obtain a URL address to be skipped according to login information, and when the URL address to be skipped belongs to any subsystem, receive a token ID generated by the token service system according to the login information;
the encryption module 220 is configured to encrypt the token ID according to a first encryption algorithm to generate a first encrypted token ID, and encrypt the token ID according to a second encryption algorithm to generate a second encrypted token ID;
the verification module 230 is configured to initiate an HTTP request to the URL address to be jumped based on the second encrypted token ID, verify the second encrypted token ID according to the first encrypted token ID, and respond to the HTTP request to jump to the URL address to be jumped if the second encrypted token ID passes the first encrypted token ID.
Under the condition of not modifying a main system, the jump verification system 200 for the URL address can add validity check, specifically: the validity of access to any subsystem is verified through the token ID of the token service system, the safety of the subsystem is improved, the problems of system data information leakage and illegal service handling caused by illegal access outside the subsystem are solved, and the system can be transplanted to any WEB engineering for use, so that the applicability is high and the expandability is high.
Preferably, in the above technical solution, the verification module 230 is specifically configured to:
decrypting the second encrypted token ID by using a second decryption algorithm corresponding to the second encryption algorithm to obtain a second decrypted token ID;
encrypting the second decryption token ID by using the first encryption algorithm to obtain a third encryption token ID;
and judging whether the first encryption token ID is the same as the third encryption token ID or not so as to determine whether the second encryption token ID passes the verification.
Preferably, in the above technical solution, the encryption module 220 is further configured to: setting a validity period of the first encrypted token ID when the first encrypted token ID is generated;
the checking module 230 is further configured to, when determining whether the first encrypted token ID is the same as the third encrypted token, further include: verifying whether the current point in time is within a validity period of the first cryptographic token ID.
Through double verification, namely judging whether the first encryption token ID is the same as the third encryption token ID or not and verifying whether the current time point is in the valid period of the first encryption token ID or not, the access legitimacy of any subsystem is further improved and the safety of the subsystem is further improved.
Preferably, in the above technical solution, the login information includes a job number, an operation code, an operation time, and at least one random code.
The above-mentioned steps for realizing the corresponding functions of each parameter and each unit module in the jump verification system 200 for a URL address of the present invention refer to each parameter and step in the above-mentioned embodiment of the jump method for a URL address, which are not described herein again.
As shown in fig. 3, an electronic device 300 according to an embodiment of the present invention includes a memory 310, a processor 320, and a program 330 stored in the memory 310 and running on the processor 320, wherein the processor 320 executes the program 330 to implement any of the steps of the URL address jump method implemented in the foregoing embodiments.
Validity checks can be added without modifications to the host system, specifically: the validity of access to any subsystem is verified through the token ID of the token service system, the safety of the subsystem is improved, the problems of system data information leakage and illegal service handling caused by illegal access outside the subsystem are solved, and the system can be transplanted to any WEB engineering for use, so that the applicability is high and the expandability is high.
The electronic device 300 may be a computer, a mobile phone, or the like, and correspondingly, the program 330 is computer software or a mobile phone APP, and the above parameters and steps in the electronic device 300 of the present invention may refer to the parameters and steps in the above embodiment of the URL address jump method, which is not described herein again.
In the present invention, the terms "first", "second" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present invention, "a plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.
Claims (9)
1. A jump verification method of a URL address is characterized by comprising the following steps:
acquiring a URL address to be jumped according to login information, and receiving a token ID generated by a token service system according to the login information when the URL address to be jumped belongs to any subsystem;
encrypting the token ID according to a first encryption algorithm to generate a first encrypted token ID, and encrypting the token ID according to a second encryption algorithm to generate a second encrypted token ID;
and initiating an HTTP request to the URL address to be jumped based on the second encrypted token ID, verifying the second encrypted token ID according to the first encrypted token ID, and responding to the HTTP request to jump to the URL address to be jumped if the second encrypted token ID passes the first encrypted token ID.
2. The method of claim 1, wherein the verifying the second encrypted token ID based on the first encrypted token ID comprises:
decrypting the second encrypted token ID by using a second decryption algorithm corresponding to the second encryption algorithm to obtain a second decrypted token ID;
encrypting the second decryption token ID by using the first encryption algorithm to obtain a third encryption token ID;
and judging whether the first encryption token ID is the same as the third encryption token ID or not so as to determine whether the second encryption token ID passes the verification.
3. The jump verification method of URL address as claimed in claim 2, further comprising: setting a validity period of the first encrypted token ID when the first encrypted token ID is generated;
then, when determining whether the first encrypted token ID is the same as the third encrypted token, the method further includes: verifying whether the current point in time is within a validity period of the first cryptographic token ID.
4. The jump verification method for URL address as claimed in any one of claims 1 to 3, wherein the login information comprises job number, operation code, operation time and at least one random code.
5. A jump verification system of a URL address is characterized by comprising an acquisition receiving module, an encryption module and a verification module;
the acquisition receiving module is used for acquiring a URL address to be jumped according to login information, and when the URL address to be jumped belongs to any subsystem, receiving a token ID generated by the token service system according to the login information;
the encryption module is used for encrypting the token ID according to a first encryption algorithm to generate a first encrypted token ID, and encrypting the token ID according to a second encryption algorithm to generate a second encrypted token ID;
the verification module is used for initiating an HTTP request to the URL address to be jumped based on the second encrypted token ID, verifying the second encrypted token ID according to the first encrypted token ID, and responding the HTTP request to jump to the URL address to be jumped if the second encrypted token ID passes the first encrypted token ID.
6. The system for skip validation of URL address as claimed in claim 5, wherein said check module is specifically configured to:
decrypting the second encrypted token ID by using a second decryption algorithm corresponding to the second encryption algorithm to obtain a second decrypted token ID;
encrypting the second decryption token ID by using the first encryption algorithm to obtain a third encryption token ID;
and judging whether the first encryption token ID is the same as the third encryption token ID or not so as to determine whether the second encryption token ID passes the verification.
7. The jump verification system of a URL address as claimed in claim 6,
the encryption module is further configured to: setting a validity period of the first encrypted token ID when the first encrypted token ID is generated;
the checking module is further configured to, when determining whether the first encrypted token ID is the same as the third encrypted token, further include: verifying whether the current point in time is within a validity period of the first cryptographic token ID.
8. The jump verification system for URL address as claimed in any one of claims 5 to 7, wherein the login information comprises job number, operation code, operation time and at least one random code.
9. An electronic device comprising a memory, a processor and a program stored in said memory and running on said processor, wherein said processor implements the steps of a jump verification method for URL addresses as claimed in any one of claims 1 to 4 when executing said program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011125461.3A CN112231674A (en) | 2020-10-20 | 2020-10-20 | Skip verification method and system for URL (Uniform resource locator) address and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011125461.3A CN112231674A (en) | 2020-10-20 | 2020-10-20 | Skip verification method and system for URL (Uniform resource locator) address and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112231674A true CN112231674A (en) | 2021-01-15 |
Family
ID=74118580
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011125461.3A Pending CN112231674A (en) | 2020-10-20 | 2020-10-20 | Skip verification method and system for URL (Uniform resource locator) address and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112231674A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113065160A (en) * | 2021-04-12 | 2021-07-02 | 浙江环玛信息科技有限公司 | Intelligent court data transmission method and system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107483437A (en) * | 2017-08-14 | 2017-12-15 | 深圳市华傲数据技术有限公司 | A kind of user's unified login management method and device |
| CN109150800A (en) * | 2017-06-16 | 2019-01-04 | 中兴通讯股份有限公司 | Login access method, system and storage medium |
| CN109150910A (en) * | 2018-10-11 | 2019-01-04 | 平安科技（深圳）有限公司 | Log in token generation and verification method, device and storage medium |
| CN109309683A (en) * | 2018-10-30 | 2019-02-05 | 泰华智慧产业集团股份有限公司 | The method and system of client identity verifying based on token |
| CN111783067A (en) * | 2016-05-09 | 2020-10-16 | 阿里巴巴集团控股有限公司 | Automatic login method and device among multiple network stations |
-
2020
- 2020-10-20 CN CN202011125461.3A patent/CN112231674A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111783067A (en) * | 2016-05-09 | 2020-10-16 | 阿里巴巴集团控股有限公司 | Automatic login method and device among multiple network stations |
| CN109150800A (en) * | 2017-06-16 | 2019-01-04 | 中兴通讯股份有限公司 | Login access method, system and storage medium |
| CN107483437A (en) * | 2017-08-14 | 2017-12-15 | 深圳市华傲数据技术有限公司 | A kind of user's unified login management method and device |
| CN109150910A (en) * | 2018-10-11 | 2019-01-04 | 平安科技（深圳）有限公司 | Log in token generation and verification method, device and storage medium |
| CN109309683A (en) * | 2018-10-30 | 2019-02-05 | 泰华智慧产业集团股份有限公司 | The method and system of client identity verifying based on token |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113065160A (en) * | 2021-04-12 | 2021-07-02 | 浙江环玛信息科技有限公司 | Intelligent court data transmission method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110036613B (en) | System and method for providing identity authentication for decentralized applications | |
| US10284376B2 (en) | Code signing system with machine to machine interaction | |
| CN108023874B (en) | Single sign-on verification device and method and computer readable storage medium | |
| US11258792B2 (en) | Method, device, system for authenticating an accessing terminal by server, server and computer readable storage medium | |
| CN108322461B (en) | Method, system, device, equipment and medium for automatically logging in application program | |
| CN104954330B (en) | A kind of methods, devices and systems to be conducted interviews to data resource | |
| CN103577206A (en) | Method and device for installing application software | |
| CN111030812A (en) | Token verification method, device, storage medium and server | |
| US10284374B2 (en) | Code signing system with machine to machine interaction | |
| CN112261012A (en) | Browser, server and webpage access method | |
| CN111917773A (en) | Service data processing method and device and server | |
| CN103561040A (en) | File downloading method and system | |
| CN109474600B (en) | Account binding method, system, device and equipment | |
| JP2011151785A (en) | Relay processing apparatus, relay processing method and program | |
| CN111431920A (en) | Security control method and system based on dynamic token | |
| CN108235067B (en) | Authentication method and device for video stream address | |
| CN112231674A (en) | Skip verification method and system for URL (Uniform resource locator) address and electronic equipment | |
| CN110855656B (en) | Plug-in flow proxy method, device and system capable of realizing application server protection | |
| CN111182010B (en) | Local service providing method and device | |
| CN116821918A (en) | Online upgrading method, chip device, computer terminal and storage medium | |
| CN108429621B (en) | Identity verification method and device | |
| CN107241341B (en) | Access control method and device | |
| Wichmann et al. | Web cryptography API: Prevalence and possible developer mistakes | |
| CN112732676B (en) | Block chain-based data migration method, device, equipment and storage medium | |
| CN103179088A (en) | Protection method and protection system of common gateway interface business |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |