CN107147644A - It is a kind of to realize the method that mobile APP user logs in single equipment - Google Patents
It is a kind of to realize the method that mobile APP user logs in single equipment Download PDFInfo
- Publication number
- CN107147644A CN107147644A CN201710326598.7A CN201710326598A CN107147644A CN 107147644 A CN107147644 A CN 107147644A CN 201710326598 A CN201710326598 A CN 201710326598A CN 107147644 A CN107147644 A CN 107147644A
- Authority
- CN
- China
- Prior art keywords
- token
- user
- app
- stack
- legal
- 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.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0853—Network architectures or network communication protocols for network security for authentication of entities using an additional device, e.g. smartcard, SIM or a different communication terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/321—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority
- H04L9/3213—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority using tickets or tokens, e.g. Kerberos
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Telephonic Communication Services (AREA)
- Telephone Function (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The method that mobile APP user logs in single equipment is realized the invention discloses a kind of, one token stack is safeguarded to the user of each login, and arrange legal token and position of the illegal token in token stack, same account is logged on the mobile APP of distinct device, it will be updated by the token position pairing method token of agreement is corresponding with illegal token progress, and in the service request that APP ends are initiated, verification according to token stack to its entrained User Token, by the term of validity directly to token, legitimacy is judged, particularly limitation will be made in distinct device APP login to account, realize the uniqueness of service request after account is logged on single equipment, reduce the security risk of account, improve the reliability of APP systems.
Description
Technical field
It is more particularly to a kind of to realize that mobile APP user exists the present invention relates to computer technology and platform safety technical field
The method that single equipment is logged in.
Background technology
Under the overall situation that mobile Internet is rapidly popularized, Mobile solution is fast-developing, while being also faced with numerous choose
War and problem, one of FAQs is exactly the safety issue of user account, realizes that user is in the login of single equipment
The basic guarantee of user account safety.Consider from service layer, if the mechanism logged in without account in single equipment, then use
Family many equipment login after, at the same time requested service operate when, just occur business datum disorder with conflict, it is more serious very
It may extremely trigger whole system to collapse, cause unthinkable consequence；Consider from the aspect of user account safety and uniqueness, use
Family will not simultaneously be logged in and requested service in many equipment under normal circumstances, and the exactly system that user needs can exist to its account
The login of other equipment is limited, to ensure the security of its account information.The present invention will set for mobile APP user single
Standby secure log provides a set of efficient solution with business operation.
The content of the invention
The purpose of the present invention is to realize the method that mobile APP user logs in single equipment, by being safeguarded for each user
One token stack, legal token, illegal token, expired token to deposit user etc., according to user login operation behavior management
And the position of the various tokens of user is adjusted, the legitimacy of incoming token is verified, assists to realize that account is set single by MAC Address
The standby validity logged in.
In order to reach above-mentioned technique effect, the present invention takes following technical scheme：One kind realizes mobile APP user in list
The method that one equipment is logged in, comprises the following steps：
Step S1, user are logged in first, create and initialize token stack, and token is returned to APP ends；
According to user, successful log operates obtained data first, is that user creates the unique token stack in an address,
And the legal token PUSH of generation will be logged in first to this token stack, in this, as the initialization operation of User Token stack；Together
When for the storage user's particulars of token creation one in each token stack sub- token, and return and step on first to APP ends
The legal token of terrestrial production.
Step S2, user is non-logs in first, and the element of User Token stack is changed, and returns to token to APP ends, right
In same account, compared with last login, it is divided into same equipment and logs in and distinct device two kinds of situations of login, it is specific as follows：
B1. compared with the last Successful login, if account is logged in the equipment at same APP ends, service end incite somebody to action this
It is secondary to log in reported device mac address and memory database, the MAC Address in subscriber data corresponding to the legal token of user
Matched, after the match is successful, the element of legal token position in token stack is updated to the newest use that this login is produced
Family token, that is, the newest legal token of user, the corresponding sub- token of subscriber data of storage User Token after operating successfully, and
The newest User Token of this Successful login generation is returned to APP ends；
B2. compared with the last Successful login, if account is logged in the equipment at different APP ends, service end by this
Log in reported device mac address and memory database, the MAC Address in subscriber data corresponding to the legal token of user enters
Row matching, it is rear that it fails to match, and the element of legal token position in token stack is updated into the newest use that this login is produced
Family token, and the legal token of the user of last login is extruded into second position in token stack, the i.e. position of illegal token, and
The newest User Token of this Successful login generation is returned to APP ends.
Token when step S3, service end are to APP ends service request is verified, to judge that this login of user is reported
Token it is whether legal, specifically comprising following sub-step：
C1. service end intercepts the User Token that APP ends are reported, and inquires the legal of user in token stack according to user name
Token, and illegal token；
If the legal token c2. in c1 is not present with illegal token, then the token stack of user has been cleared, show to use
Family reports token to exceed the term of validity, and current token is expired, returns to the expired error message of token to APP ends, points out APP ends to use
Family is logged in again；
If legal token c3. in c1 is not sky, legal token is matched with reporting token, the match is successful then school
Test and pass through, be that the service request at APP ends is let pass, while the sub- token of the corresponding subscriber data of query token, is asked with auxiliary activities
Processing；
If c4. in c3 token matched fail, token will be reported to be matched with illegal token, it fails to match then show on
Report token to exceed the term of validity, return to the expired error message of token to APP ends, point out APP end subscribers to log in again；
If c5. the match is successful with illegal token in c4, show that current account is logged in other equipment, current token
For illegal token, the illegal error message of token is returned to APP ends, points out APP end subscribers account to be logged in other equipment, builds
View is logged in again, or account number safety is on the hazard, and points out it to give password or contact APP keepers for change.
Further technical scheme is：A kind of to realize the method that mobile APP user logs in single equipment, step S1 is specific
Realized by following sub-step：
A1.APP ends collect user input user name, password, and equipment MAC Address, to service end initiate log in
Request；
A2. service end intercepts the user name, password, device mac address that APP ends report, in user name, the conjunction of MAC Address
After method verification passes through, the correctness of password is judged；
If a3. code error, the prompt message of code error is returned to APP ends；If password is correct, inquiry user is detailed
Thin information, obtains generation token and data needed for sub- token；
A4. the necessary data in a3, generates User Token and the sub- token of subscriber data；
A5. using identification strings and login name string-concatenation with APP ends business correlation as KEY, with raw in a4
Into User Token initiate to create User Token stack to memory database as VALUE and initialize the request of token stack, and
After the completion of operation, using User Token as KEY, the sub- token generated using in a4 initiates the storage request of sub- token as VALUE；
A6. memory database creates User Token stack, and the legal token PUSH for logging in generation first is grasped to token stack
After making successfully, the corresponding sub- token of subscriber data is stored；
A7. the user profile needed for the legal token of the user generated in a4 and other business of APP ends is returned into APP
End.
Further technical scheme is：It is a kind of to realize in the method that mobile APP user logs in single equipment, token stack
The corresponding sub- token of User Token is one-to-one subordinate relation, and their term of validity is identical, and token expiration is according to industry
Business demand is set.
Further technical scheme is：It is a kind of to realize the method that mobile APP user logs in single equipment, token stack and son
Token is stored in internal memory, or in memory database such as Redis.
Further technical scheme is：A kind of realize is used in the method that mobile APP user logs in single equipment, token stack
The data that family token packet contains have Crypted password, token expiration etc., after being handled by AES, obtain a BASE64 character
String, i.e. User Token；Sub- token contains the particulars data of user, there is user name, user type, the MAC of beaching accommodation
Address and the related user profile of APP business, after being handled by AES, obtain a BASE64 character string, i.e. user
The corresponding sub- token stored data of token.
Further technical scheme is：The token of top in token stack is set as the legal token of user；Second token
For user's illegal token, i.e. account token when forcing down line is logged in by those in other equipment；The token of other positions is nothing
Imitate token.
The present invention compared with prior art, with following beneficial effect：It is disclosed by the invention to realize that mobile APP user exists
The method that single equipment is logged in, safeguards a token stack, and arrange legal token and illegal token to the user of each login
Position in token stack, same account is logged on the mobile APP of distinct device, by by the token position pairing decree of agreement
Board is corresponding with illegal token progress to be updated, and in the service request that APP ends are initiated, according to token stack to its entrained user
The verification of token, the term of validity directly to token, legitimacy are judged, particularly by account distinct device APP's
Limitation is made in login, realizes the uniqueness of service request after account is logged on single equipment, reduces the safety wind of account
Danger, improves the reliability of APP systems.
Brief description of the drawings
Fig. 1 is the flow chart of the inventive method；
Fig. 2 is the flowage structure schematic diagram of the inventive method.
Embodiment
With reference to embodiments of the invention, the invention will be further elaborated.
Embodiment：
It is a kind of to realize the method that mobile APP user logs in single equipment, as shown in Figure 1 and Figure 2, comprise the following steps：
Step S1, according to user, successful log operates obtained data first, and it is unique to be that user creates an address
Token stack 300, and the legal token 301PUSH of generation will be logged in first to this token stack, in this, as User Token stack
Initialization operation, legal token is 301 in Fig. 2, while detailed for one storage user of token creation in each token stack
The sub- token 3011 of thin data.The flow specifically included has：
A1, APP end 100 collect user input user name, password, and equipment MAC Address, sent out to service end 200
Play logging request；A2, service end 200 intercept user name, password, device mac address that APP ends 100 are reported etc., user name,
The legitimacy verifies of MAC Address judge the correctness of password by rear；If a3, code error, password is returned to APP ends wrong
Prompt message by mistake；If password is correct, User Detail is inquired about, generation token and data needed for sub- token are obtained；A4, root
According to the necessary data in a3, the sub- token 3011 of the generation legal token 301 of user and storage subscriber data；A5, APP ends will be carried
The related identification strings of business with login name string-concatenation as KEY, the User Token generated using in a4 as VALUE to
Memory database is initiated to create User Token stack and initializes the request of token stack, and after the completion of operation, is made with User Token
For KEY, the sub- token generated using in a4 initiates the storage request of sub- token as VALUE；A6, memory database create user's order
Board stack, and the legal token 301PUSH for logging in generation first after operating successfully, is stored into subscriber data correspondence to token stack 300
Sub- token 3011；A7, by the legal token 301 of the user generated in a4, and user profile needed for other business of APP ends is returned
Back to APP ends 100.
Accordingly, the data that User Token is included have Crypted password, token expiration etc., after being handled by AES,
Obtain a BASE64 character string, i.e. User Token；Sub- token contains the particulars data of user, there is user name, user
The related user profile of type, the MAC Address of beaching accommodation and APP business, after being handled by AES, obtains one
BASE64 character strings, that is, store the corresponding sub- token of User Token data.
Accordingly, the corresponding sub- token of User Token in token stack is one-to-one subordinate relation, and its term of validity
Identical, token expiration is set according to business demand.The token for arranging top in token stack is the legal token of user, second
Token is that user's illegal token, i.e. account log in token when forcing down line, the token of other positions by those in other equipment
For invalid token.As shown in Fig. 2 position 1 is legal token 301, corresponding sub- token is 3011；Position 2 is illegal token
302, corresponding sub- token is 3021；Position 1 is legal token 301, and corresponding sub- token is 3011；Follow-up other positions are it
His expired or illegal token 303,304, corresponding sub- token is 3031,3041 respectively, wherein 303,304 be only intended to represent should
Position is other expired or illegal tokens, is not used to specific restriction.
Accordingly, token stack is stored in internal memory with the suggestion of sub- token, or in memory database such as Redis.
S2, user is non-logs in first, and the element to User Token stack 300 is changed, for same account, and upper
Secondary login is compared, and is divided into same equipment and is logged in and distinct device two kinds of situations of login.
If compared with the last Successful login, account is logged in the equipment at same APP ends, and service end 200 will
This is logged in reported device mac address and memory database, in subscriber data corresponding to the legal token 301 of user
MAC Address is matched, after the match is successful, and the element of legal token position in token stack is updated into what this login was produced
Newest User Token, that is, the newest legal token 301 of user, the corresponding subscriber data of storage User Token after operating successfully
Sub- token, and return to the token that this Successful login is generated to APP ends.
If compared with the last Successful login, account is logged in the equipment at different APP ends, and service end 200 will be by
This is logged in reported device mac address and memory database, the MAC in subscriber data corresponding to the legal token of user
Location is matched, and it is rear that it fails to match, and the element of legal token position in token stack is updated into this login and produced most
New User Token, and the legal token 301 of the user of last login is extruded into second position in token stack, i.e. illegal token
302 position, the new legal token 301 of this Successful login generation is returned to APP ends 100；If continuously appearing in multiple set
Standby upper login, then the legal token 301 in token stack 300 and the token on the position of illegal token 302 will be pressed against 303 or 304
Position, new legal token is with illegal token by by PUSH to 301 and 302 position.
S3, service end 200 are verified to the service request token at APP ends 100, to judge that this login of user is reported
Token it is whether legal, comprising flow have：C1, service end 200 intercept the User Token that APP ends 100 are reported, and according to user
Name inquires the legal token 301 of user in token stack, and illegal token 302；If legal token 301 in c2, c1 with it is non-
Decree board 302 is not present, then the token stack of user has been cleared, and shows that reporting of user token exceeds the term of validity, currently
Token is expired, returns to the expired error message of token to APP ends 100, points out APP end subscribers to log in again；If the conjunction in c3, c1
Decree board 301 not for sky, then by legal token 301 with reporting token to be matched, the match is successful then verify pass through, be APP ends
Service request let pass, while the sub- token 3011 of the corresponding subscriber data of query token, the processing asked with auxiliary activities；c4、
If token matched fails in c3, token will be reported to be matched with illegal token 302, it fails to match then shows to report token to surpass
The term of validity is crossed, the expired error message of token is returned to APP ends 100, points out APP end subscribers to log in again；If in c5, c4 with it is non-
The match is successful for decree board 302, then show that current account is logged in other equipment, current token is illegal token, to APP ends
100 return to the illegal error message of token, point out APP end subscribers account to be logged in other equipment, it is proposed that to log in again, or account
Number safety is on the hazard, and points out it to give password or contact APP keepers etc. for change, so same account can only be in an equipment
APP on requested service.
It is understood that the principle that embodiment of above is intended to be merely illustrative of the present and the exemplary implementation that uses
Mode, but the invention is not limited in this.For those skilled in the art, the essence of the present invention is not being departed from
In the case of refreshing and essence, various changes and modifications can be made therein, and these variations and modifications are also considered as protection scope of the present invention.
Claims (7)
1. a kind of realize the method that mobile APP user logs in single equipment, it is characterised in that comprises the following steps：
Step S1, user are logged in first, create and initialize token stack, and token is returned to APP ends；
According to user, successful log operates obtained data first, is that user creates the unique token stack in an address, and will
The legal token PUSH of generation is logged in first to this token stack, in this, as the initialization operation of User Token stack；It is simultaneously
The sub- token of one storage user's particulars of token creation in each token stack, and life is logged in first to the return of APP ends
The legal token of production；
Step S2, user is non-logs in first, and the element of User Token stack is changed, and returns to token to APP ends,
For same account, compared with last login, it is divided into same equipment and logs in and distinct device two kinds of situations of login, specifically
It is as follows：
B1. compared with the last Successful login, if account is logged in the equipment at same APP ends, service end steps on this
In record reported device mac address and memory database, the MAC Address in subscriber data corresponding to the legal token of user is carried out
Matching, after the match is successful, the newest user order that this login is produced is updated to by the element of legal token position in token stack
Board, that is, the newest legal token of user, the corresponding sub- token of subscriber data of storage User Token after operating successfully, and to
APP ends return to the newest User Token of this Successful login generation；
B2. compared with the last Successful login, if account is logged in the equipment at different APP ends, service end logs in this
In the device mac address and memory database that are reported, the MAC Address progress in subscriber data corresponding to the legal token of user
Match somebody with somebody, it is rear that it fails to match, the element of legal token position in token stack is updated to the newest user order that this login is produced
Board, and the legal token of the user of last login is extruded into second position in token stack, the i.e. position of illegal token, and to
APP ends return to the newest User Token of this Successful login generation；
Token when step S3, service end are to APP ends service request is verified, and to judge user, this logs in reported order
Whether board is legal, specifically comprising following sub-step：
C1. service end intercepts the User Token that APP ends are reported, and inquires according to user name the legal order of user in token stack
Board, and illegal token；
If the legal token c2. in c1 is not present with illegal token, then the token stack of user has been cleared, and shows on user
Report token to exceed the term of validity, current token is expired, return to the expired error message of token to APP ends, point out APP end subscriber weights
New login；
If legal token c3. in c1 is not sky, legal token is matched with reporting token, the match is successful then verification lead to
Cross, be that the service request at APP ends is let pass, while the sub- token of the corresponding subscriber data of query token, the place asked with auxiliary activities
Reason；
If c4. token matched fails in c3, token will be reported to be matched with illegal token, it fails to match then shows to report order
Board exceedes the term of validity, returns to the expired error message of token to APP ends, points out APP end subscribers to log in again；
If c5. the match is successful with illegal token in c4, show that current account is logged in other equipment, current token is non-
Method token, the illegal error message of token is returned to APP ends, points out APP end subscribers account to be logged in other equipment, it is proposed that weight
New login, or account number safety are on the hazard, and point out it to give password or contact APP keepers for change.
2. a kind of the method that mobile APP user logs in single equipment is realized according to claim 1, it is characterised in that：
Step S1 is realized especially by following sub-step：
A1.APP ends collect user input user name, password, and equipment MAC Address, to service end initiate logging request；
A2. service end intercepts the user name, password, device mac address that APP ends report, in user name, the legitimacy of MAC Address
After verification passes through, the correctness of password is judged；
If a3. code error, the prompt message of code error is returned to APP ends；If password is correct, inquiry user believes in detail
Breath, obtains generation token and data needed for sub- token；
A4. the necessary data in a3, generates User Token and the sub- token of subscriber data；
A5. using identification strings and login name string-concatenation with APP ends business correlation as KEY, with what is generated in a4
User Token is initiated to create User Token stack and initializes the request of token stack as VALUE to memory database, and in operation
After the completion of, using User Token as KEY, the sub- token generated using in a4 initiates the storage request of sub- token as VALUE；
A6. memory database creates User Token stack, and the legal token PUSH for logging in generation first is operated into token stack
After work(, the corresponding sub- token of subscriber data is stored；
A7. the legal token of the user generated in a4 is returned into APP ends.
3. a kind of the method that mobile APP user logs in single equipment is realized according to claim 1, it is characterised in that：
The corresponding sub- token of User Token in token stack is one-to-one subordinate relation, and their term of validity is identical.
4. a kind of the method that mobile APP user logs in single equipment is realized according to claim 1, it is characterised in that：
Token stack is stored in internal memory with sub- token, or in memory database.
5. a kind of the method that mobile APP user logs in single equipment is realized according to claim 4, it is characterised in that：
Token stack is stored in database Redis with sub- token.
6. a kind of according to claim 1 or 3 realizes the method that movement APP user logs in single equipment, its feature exists
In：The data that User Token is included in token stack have Crypted password, token expiration；Sub- token contains the particulars of user
Data, there is the related user profile of user name, user type, the MAC Address of beaching accommodation and APP business.
7. a kind of the method that mobile APP user logs in single equipment is realized according to claim 1, it is characterised in that：
The token of top in token stack is set as the legal token of user；Second token is user's illegal token, i.e., account is by those
Token when forcing down line is logged in other equipment；The token of other positions is invalid token.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710326598.7A CN107147644B (en) | 2017-05-10 | 2017-05-10 | Method for realizing login of mobile APP user in single device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710326598.7A CN107147644B (en) | 2017-05-10 | 2017-05-10 | Method for realizing login of mobile APP user in single device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107147644A true CN107147644A (en) | 2017-09-08 |
| CN107147644B CN107147644B (en) | 2020-07-28 |
Family
ID=59777970
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710326598.7A Active CN107147644B (en) | 2017-05-10 | 2017-05-10 | Method for realizing login of mobile APP user in single device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107147644B (en) |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107481126A (en) * | 2017-09-27 | 2017-12-15 | 北京同城必应科技有限公司 | A kind of single method of anti-brush, server and client side |
| CN108023881A (en) * | 2017-12-04 | 2018-05-11 | 泰康保险集团股份有限公司 | Login method, device, medium and the electronic equipment of application program |
| CN108418821A (en) * | 2018-03-06 | 2018-08-17 | 北京焦点新干线信息技术有限公司 | Redis and Kafka-based high-concurrency scene processing method and device for online shopping system |
| CN108848113A (en) * | 2018-08-15 | 2018-11-20 | 广州视源电子科技股份有限公司 | Client device login control method and device, storage medium and server |
| CN109218326A (en) * | 2018-10-10 | 2019-01-15 | 广州虎牙信息科技有限公司 | Login validation method, device, storage medium and server |
| CN109587249A (en) * | 2018-12-07 | 2019-04-05 | 北京金山云网络技术有限公司 | Information sending, receiving method, device, server, client and storage medium |
| CN110032855A (en) * | 2019-02-28 | 2019-07-19 | 招银云创（深圳）信息技术有限公司 | Login method, device, computer equipment and the storage medium of application |
| CN112511563A (en) * | 2020-12-22 | 2021-03-16 | 四川长虹电器股份有限公司 | Method for logging in terminal equipment by cloud user |
| CN112910854A (en) * | 2021-01-18 | 2021-06-04 | 深圳万物安全科技有限公司 | Method and device for safe operation and maintenance of Internet of things, terminal equipment and storage medium |
| CN112948783A (en) * | 2021-02-26 | 2021-06-11 | 平安消费金融有限公司 | Client login management method, device, server and storage medium |
| CN113923010A (en) * | 2021-09-30 | 2022-01-11 | 上海影创信息科技有限公司 | Head display equipment single sign-on method and system based on virtual reality |
| CN114745133A (en) * | 2018-03-27 | 2022-07-12 | 杭州蚂蚁聚慧网络技术有限公司 | Method and device for identifying uniqueness of equipment |
| CN115344851A (en) * | 2022-10-13 | 2022-11-15 | 海看网络科技(山东)股份有限公司 | Method for realizing non-inductive refreshing of token based on dynamic proxy |
| CN117579254A (en) * | 2024-01-16 | 2024-02-20 | 金财数科(北京)信息技术有限公司 | Encryption method, system and device for data transmission |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101075864A (en) * | 2007-07-16 | 2007-11-21 | 腾讯科技（深圳）有限公司 | Method for synchronizing and processing data, customer terminal equipment and servo |
| CN104796408A (en) * | 2015-03-25 | 2015-07-22 | 广州视睿电子科技有限公司 | Single-point live login method and single-point live login device |
| CN104821937A (en) * | 2015-03-26 | 2015-08-05 | 腾讯科技（北京）有限公司 | Token acquisition method, device and system |
| US20150381618A1 (en) * | 2014-06-27 | 2015-12-31 | Gerard Lin | Method of mutual verification between a client and a server |
| CN105978682A (en) * | 2016-06-27 | 2016-09-28 | 武汉斗鱼网络科技有限公司 | Mobile terminal token generation system and method thereof for judging identity of login user |
| CN106104532A (en) * | 2014-01-23 | 2016-11-09 | 洛茨平有限公司 | For creating the computer system and method for multiple information token |
-
2017
- 2017-05-10 CN CN201710326598.7A patent/CN107147644B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101075864A (en) * | 2007-07-16 | 2007-11-21 | 腾讯科技（深圳）有限公司 | Method for synchronizing and processing data, customer terminal equipment and servo |
| CN106104532A (en) * | 2014-01-23 | 2016-11-09 | 洛茨平有限公司 | For creating the computer system and method for multiple information token |
| US20150381618A1 (en) * | 2014-06-27 | 2015-12-31 | Gerard Lin | Method of mutual verification between a client and a server |
| CN104796408A (en) * | 2015-03-25 | 2015-07-22 | 广州视睿电子科技有限公司 | Single-point live login method and single-point live login device |
| CN104821937A (en) * | 2015-03-26 | 2015-08-05 | 腾讯科技（北京）有限公司 | Token acquisition method, device and system |
| CN105978682A (en) * | 2016-06-27 | 2016-09-28 | 武汉斗鱼网络科技有限公司 | Mobile terminal token generation system and method thereof for judging identity of login user |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107481126A (en) * | 2017-09-27 | 2017-12-15 | 北京同城必应科技有限公司 | A kind of single method of anti-brush, server and client side |
| CN108023881A (en) * | 2017-12-04 | 2018-05-11 | 泰康保险集团股份有限公司 | Login method, device, medium and the electronic equipment of application program |
| CN108023881B (en) * | 2017-12-04 | 2020-12-15 | 泰康保险集团股份有限公司 | Application login method, device, medium and electronic equipment |
| CN108418821A (en) * | 2018-03-06 | 2018-08-17 | 北京焦点新干线信息技术有限公司 | Redis and Kafka-based high-concurrency scene processing method and device for online shopping system |
| CN108418821B (en) * | 2018-03-06 | 2021-06-18 | 北京焦点新干线信息技术有限公司 | Redis and Kafka-based high-concurrency scene processing method and device for online shopping system |
| CN114745133B (en) * | 2018-03-27 | 2024-09-17 | 杭州蚂蚁聚慧网络技术有限公司 | Method and device for identifying equipment uniqueness |
| CN114745133A (en) * | 2018-03-27 | 2022-07-12 | 杭州蚂蚁聚慧网络技术有限公司 | Method and device for identifying uniqueness of equipment |
| CN108848113B (en) * | 2018-08-15 | 2021-03-26 | 广州视源电子科技股份有限公司 | Client device login control method and device, storage medium and server |
| CN108848113A (en) * | 2018-08-15 | 2018-11-20 | 广州视源电子科技股份有限公司 | Client device login control method and device, storage medium and server |
| CN109218326A (en) * | 2018-10-10 | 2019-01-15 | 广州虎牙信息科技有限公司 | Login validation method, device, storage medium and server |
| CN109587249A (en) * | 2018-12-07 | 2019-04-05 | 北京金山云网络技术有限公司 | Information sending, receiving method, device, server, client and storage medium |
| CN110032855A (en) * | 2019-02-28 | 2019-07-19 | 招银云创（深圳）信息技术有限公司 | Login method, device, computer equipment and the storage medium of application |
| CN112511563A (en) * | 2020-12-22 | 2021-03-16 | 四川长虹电器股份有限公司 | Method for logging in terminal equipment by cloud user |
| CN112910854A (en) * | 2021-01-18 | 2021-06-04 | 深圳万物安全科技有限公司 | Method and device for safe operation and maintenance of Internet of things, terminal equipment and storage medium |
| CN112948783A (en) * | 2021-02-26 | 2021-06-11 | 平安消费金融有限公司 | Client login management method, device, server and storage medium |
| CN113923010A (en) * | 2021-09-30 | 2022-01-11 | 上海影创信息科技有限公司 | Head display equipment single sign-on method and system based on virtual reality |
| CN115344851A (en) * | 2022-10-13 | 2022-11-15 | 海看网络科技(山东)股份有限公司 | Method for realizing non-inductive refreshing of token based on dynamic proxy |
| CN117579254A (en) * | 2024-01-16 | 2024-02-20 | 金财数科(北京)信息技术有限公司 | Encryption method, system and device for data transmission |
| CN117579254B (en) * | 2024-01-16 | 2024-03-12 | 金财数科(北京)信息技术有限公司 | Encryption method, system and device for data transmission |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107147644B (en) | 2020-07-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107147644A (en) | It is a kind of to realize the method that mobile APP user logs in single equipment | |
| CN101316169B (en) | Network identity verification method based on internet third party biological characteristic validation | |
| CN102624705B (en) | A kind of intelligent image verification method and system | |
| US5841970A (en) | Authentication method for networks | |
| CN101047503B (en) | Method and system for fetching cipher | |
| KR20200105997A (en) | System and method for blockchain-based authentication | |
| CN103544074A (en) | Method and device for verifying service | |
| NZ550381A (en) | Authentication device and/or method | |
| WO2004049144A3 (en) | Generic security infrastructure for com based systems | |
| CN101316166A (en) | Dynamic password identity authentication method based on accidental character set | |
| CN103607416A (en) | Method and application system for authenticating identity of network terminal machine | |
| CN104899499A (en) | Internet image search based Web verification code generation method | |
| CN101689994A (en) | Multiple user authentications on a communications device | |
| CN108260015B (en) | Voting data processing method and device and electronic equipment | |
| CN106534119A (en) | Method and device for prompting client software login information | |
| CN106161348A (en) | A kind of method of single-sign-on, system and terminal | |
| CN105162604A (en) | Feature image identification based verification method and system, and verification server | |
| CN111934881B (en) | Data right determining method and device, storage medium and electronic device | |
| CN106656969A (en) | Payment state management method and system thereof, and network payment system | |
| CN106330448A (en) | User legality verification method and system, and devices | |
| EP3796613A1 (en) | Techniques for repeat authentication | |
| CN105225328A (en) | Based on mobile terminal electronic voting method and the system of face characteristic identification | |
| CN112199412A (en) | Payment bill processing method based on block chain and block chain bill processing system | |
| US7757080B1 (en) | User validation using cookies and isolated backup validation | |
| CN107580002B (en) | Double-factor authentication security manager login system and method |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |