CN102480474A - Method, device and enterprise system for verifying user login state - Google Patents
Method, device and enterprise system for verifying user login state Download PDFInfo
- Publication number
- CN102480474A CN102480474A CN2010105657990A CN201010565799A CN102480474A CN 102480474 A CN102480474 A CN 102480474A CN 2010105657990 A CN2010105657990 A CN 2010105657990A CN 201010565799 A CN201010565799 A CN 201010565799A CN 102480474 A CN102480474 A CN 102480474A
- Authority
- CN
- China
- Prior art keywords
- user
- server
- close string
- close
- string
- 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
- 238000000034 method Methods 0.000 title claims abstract description 40
- 238000012545 processing Methods 0.000 claims description 7
- 230000008676 import Effects 0.000 claims description 5
- 230000002441 reversible effect Effects 0.000 claims 2
- 235000014510 cooky Nutrition 0.000 description 4
- 238000012795 verification Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012797 qualification Methods 0.000 description 1
- 230000002787 reinforcement Effects 0.000 description 1
- 239000000725 suspension Substances 0.000 description 1
Images
Landscapes
- Computer And Data Communications (AREA)
Abstract
The invention is suitable for the field of computer software, and provides a method, a device and an enterprise system for verifying a user login state, wherein the method comprises the following steps: the method comprises the steps that a server receives user information transmitted by a client and stores a first secret string in the client, wherein the first secret string comprises the user information encrypted by the server; when logging in again, the client sends the user information and the first secret string to the server, and the server encrypts the user information to generate a second secret string; and verifying the login state of the user corresponding to the user information by comparing the second secret string with the first secret string. According to the method and the device, the login state of the user corresponding to the user information is verified by comparing the second secret string generated after the user information is encrypted with the first secret string stored in the client in advance. The server resources are not occupied, and the burden of the server is greatly reduced. Performance can be guaranteed even when the access amount is large.
Description
Technical field
The invention belongs to computer software fields, relate in particular to a kind of method, device and business system of the user's of checking logging status.
Background technology
Now, mainly be the problem that all need repeat to import username and password when logging status solves the same system of each login through preserving.Can solve the problem that repeats to import username and password when logining same system through the method for preserving user's logging status.Its concrete method mainly contains following two kinds:
1, preserves logging status through Session.Promptly after user's login, current log-on message is put among the Session, when the logon rights checking is carried out in login next time, come judges whether to login according to the value among the Session.But this method need be in all state of user of server end buffer memory, and when visit capacity was bigger, Session can take more server resource, and was not easy to expand performance.And in the time of server failing, all users can be compelled to roll off the production line.
2, preserve logging status through Cookie and database.Promptly after user login, at login string of client records (like member Id etc.), preserve active user's information and login string simultaneously at database through cookie.When carrying out the logon rights checking, remove to search in the database corresponding record according to the login string.But when visit capacity is bigger, cause the linking number superelevation of database easily, increase database pressure.
Summary of the invention
The purpose of the embodiment of the invention is to provide a kind of method, device and business system of the user's of checking logging status, is intended to solve existing method of preserving logging status and takies the many and database problem of big pressure of server resource.
The embodiment of the invention is achieved in that a kind of method of the user's of checking logging status, and said method comprises the steps:
Server receives the user profile that client is imported into, and the first close string is stored in client, and the said first close string comprises by the user profile after the server for encrypting processing;
When landing once more, client is sent said user profile and the said first close string to said server, and said server carries out encryption to said user profile and generates the second close string;
Verify the logging status of said user profile respective user through comparing the said second close string and the said first close string.
Another purpose of the embodiment of the invention is to provide a kind of device of the user's of checking logging status, and said device comprises:
The first close module of concatenating into receives the user profile that client is imported into, and the first close string is stored in client, and the said first close string comprises by the user profile after the server for encrypting processing;
The second close module of concatenating into when landing once more, receives the said user profile and the said first close string that client is sent, said user profile is carried out encryption generate the second close string;
Logging status is preserved module, verifies the logging status of said user profile respective user through comparing the said second close string and the said first close string.
Another purpose of the embodiment of the invention is to provide a kind of business system that comprises the device of said checking user logging status.
In embodiments of the present invention, when the user's login system first time or website, adopt preset algorithm that user profile is encrypted, generate the first close string.When the user logins identical system or website once more, after the preset algorithm of employing generates the second close string according to user profile, verify the logging status of said user profile respective user through comparing the said second close string and the said first close string.The user profile of said method is kept at client, does not take server resource, has greatly reduced load of server.Even when visit capacity is big, also can guaranteed performance, well promoted user experience.
Description of drawings
Fig. 1 is the flow chart of the method for the checking user logging status that provides of first embodiment of the invention;
Fig. 2 is the flow chart of the method for the checking user logging status that provides of second embodiment of the invention;
Fig. 3 is the device sketch map of the checking user logging status that provides of the embodiment of the invention.
Embodiment
In order to make the object of the invention, technical scheme and advantage clearer,, the present invention is further elaborated below in conjunction with accompanying drawing and embodiment.Should be appreciated that specific embodiment described herein only in order to explanation the present invention, and be not used in qualification the present invention.
The embodiment of the invention after the user login successfully for the first time, the more newly-generated second close string of employing and be stored in the first close string of client in advance whether equal method is verified user's logging status when next time logining identical system or website again.
The invention provides a kind of method, device and business system of the user's of checking logging status:
Said method comprises:
Server receives the user profile that client is imported into, and the first close string is stored in client, and the said first close string comprises by the user profile after the server for encrypting processing;
When landing once more, client is sent said user profile and the said first close string to said server, and said server carries out encryption to said user profile and generates the second close string;
Verify the logging status of said user profile respective user through comparing the said second close string and the said first close string.
Said device comprises:
The first close module of concatenating into receives the user profile that client is imported into, and the first close string is stored in client, and the said first close string comprises by the user profile after the server for encrypting processing;
The second close module of concatenating into when landing once more, receives the said user profile and the said first close string that client is sent, said user profile is carried out encryption generate the second close string;
Logging status is preserved module, verifies the logging status of said user profile respective user through comparing the said second close string and the said first close string.
Said business system comprises the device of said checking user logging status.
For technical scheme of the present invention is described, describe through specific embodiment below.
Embodiment one:
Fig. 1 shows the flow process of the method for a kind of user's of checking logging status that first embodiment of the invention provides, and details are as follows:
In step S101, the user authentication information of user's input that server authentication receives.
In embodiments of the present invention, when the user landed for the first time, server received the user authentication information and the checking of input, and said user authentication information includes but not limited to user name, password etc.
In step S102, after user authentication information was verified successfully, server adopted preset algorithm that user profile is carried out encryption, generates the first close string, and the user profile and the first close string are stored in the client.
In embodiments of the present invention, after user authentication information was verified successfully, with the mode of Cookie, server adopted preset algorithm that user profile is carried out encryption, generates the first close string.Said user profile is one or more combinations in user's unique identification, the IP address, sends user profile when the user sends user authentication information in the lump to server.Therefore, the first close string can be that user's unique identification is carried out generating after the encryption, IP address is carried out generating after the encryption or user's unique identification and IP address being carried out generating after the encryption jointly.
Below specify as example to use hash algorithm to generate the first close string, but be not limited to this algorithm, also can be other arbitrary algorithms.
For example:
ClientSig=(User).hashCode();
Wherein, ClientSig is close string; User is a user profile; Hash algorithm is used in hashCode () expression.
Specifically can be following three kinds;
1, adopt preset algorithm that user's unique identification is carried out generating the first close string after the encryption.
Algorithm is following:
ClientSig=(UserId).hashCode();
Wherein, ClientSig is close string; Userid is user's unique identification (this sentences ID as user's unique identification); Hash algorithm is used in hashCode () expression.
2, adopt preset algorithm that IP address is carried out generating the first close string after the encryption.
Algorithm is following:
ClientSig=(Ip).hashCode();
Wherein, ClientSig is close string; Ip is an IP address; Hash algorithm is used in hashCode () expression.
3, adopt preset algorithm that user's unique identification and IP address are carried out generating the first close string after the encryption jointly.
Algorithm is following:
ClientSig=(UserId+Ip).hashCode();
Wherein, ClientSig is close string; Userid is user's unique identification (this sentences ID as user's unique identification); Ip is an IP address; Hash algorithm is used in hashCode () expression.
In embodiments of the present invention, generate the first close string after, the user profile and the first close string are stored in the client.
In step S103, when the user landed once more, client was sent the said user profile and said first close the string to server.
In embodiments of the present invention, when the user landed identical system or website once more, server at first received the user profile and the first close string that imports into from client.
In step S104, server adopts preset algorithm that user profile is carried out encryption, generates the second close string.
In embodiments of the present invention, the generation method of the second close string is identical with the method for the generation first close string among the step S102, has just repeated no more at this.
In step S105, whether the server relatively second close string equate with the first close string, if execution in step S106 then, otherwise execution in step S107.
In embodiments of the present invention; Whether server equates to verify that through the relatively second close string and the first close string whether the user is the user who imports correct username and password when landing the last time; Come the judges logging status whether to verify success with this, promptly verify the logging status of user profile respective user through the comparison second close string and the first close string.
In step S106, keep the user to land state.
In embodiments of the present invention, when the second close string equated with the first close string, then the user had logon rights, kept user's logging status.
In step S107, the user lands the state verification failure.
In embodiments of the present invention, when the second close string and the first close string were unequal, then the user did not have logon rights, and the user lands the state verification failure, asked the user to re-enter the authorization information login.
In embodiments of the present invention, when the user's login system first time or website, adopt preset algorithm that user profile is encrypted, generate the first close string.When the user logins identical system or website once more; Server adopts preset algorithm that user profile is carried out encryption; After generating the second close string, verify the logging status of said user profile respective user through comparing the said second close string and the said first close string.Because user profile is kept at client, does not take server resource, has greatly reduced load of server.Even when visit capacity is big, also can guaranteed performance, well promoted user experience.
Embodiment two:
Fig. 2 shows the flow process of the method for a kind of user's of checking logging status that second embodiment of the invention provides, and details are as follows:
In step S201, the user authentication information of user's input that server authentication receives.
In step S202, after user authentication information was verified successfully, server adopted preset algorithm that user profile and the close string of server are carried out encryption, generates the first close string, and the user profile and the first close string are stored in the client.
In embodiments of the present invention, after user authentication information was verified successfully, with the mode of Cookie and encryption, server adopted preset algorithm that user profile and the close string of server are carried out encryption, generates the first close string.The close string of server comprises the close string that server generates at random or is stored in the close string of server in advance, the common close string of same server that uses of all users.Because said user profile is one or more combinations in user's unique identification, the IP address.Therefore, cipher mode has 3 kinds.To specify below.
Below using hash algorithm to specify as example, but be not limited to this algorithm, also can be other arbitrary algorithms.
For example:
ClientSig=(User+ServierSig).hashCode();
Wherein, ClientSig is close string; User is a user profile; ServierSig is the close string of server; Hash algorithm is used in hashCode () expression.
Be specially following three kinds:
1, adopts preset algorithm that user's unique identification and the close string of server are carried out encryption, generate the first close string.
Algorithm is following:
ClientSig=(UserId+ServierSig).hashCode();
Wherein, ClientSig is close string; Userid is user's unique identification (this sentences ID as user's unique identification); ServierSig is the close string of server; Hash algorithm is used in hashCode () expression.
2, adopt preset algorithm that IP address and the close string of server are carried out encryption and generate the first close string.
Algorithm is following:
ClientSig=(Ip+ServierSig).hashCode();
Wherein, ClientSig is close string; Ip is an IP address; ServierSig is the close string of server; Hash algorithm is used in hashCode () expression.
3, adopt preset algorithm that the close string of user's unique identification, IP address and server is carried out encryption and generate the first close string.
Algorithm is following:
ClientSig=(UserId+Ip+ServierSig).hashCode();
Wherein, ClientSig is close string; Userid is user's unique identification (this sentences ID as user's unique identification); Ip is an IP address; ServierSig is the close string of server; Hash algorithm is used in hashCode () expression.
In embodiments of the present invention, generate the first close string after, the user profile and the first close string are stored in the client.
In step S203, when the user landed once more, client was sent the said user profile and said first close the string to server;
In step S204, server adopts preset algorithm that user profile and the close string of server are carried out encryption, generates the second close string;
In step S205, whether the server relatively second close string equate with the first close string, if execution in step S206 then, otherwise execution in step S207;
In step S206, keep the user to land state;
In step S207, the user lands the state verification failure.
In embodiments of the present invention, obtained reinforcement, can prevent to be cracked according to user profile and the close complexity of concatenating into the method for the first close string and the second close string of server.And server has only been stored a close string of server, can not take server resource.
Embodiment three:
Fig. 3 shows the structure of the device of the checking user logging status that the embodiment of the invention provides, and this device is built in server, for the ease of explanation, only shows the part relevant with the embodiment of the invention.This device can be to be built in the unit that software unit, hardware cell or software and hardware in the business system combine, and perhaps is integrated in the application system of business system or business system as suspension member independently.Wherein:
User name password authentication module 31 is used to verify the user authentication information of the user input that receives.
The first close module 32 of concatenating into after user authentication information is verified successfully, adopts preset algorithm that user profile is carried out encryption and generates the first close string, and the user profile and the first close string are stored in the client.This module also comprises a junior unit:
The first close unit 321 of concatenating into after username and password is verified successfully, adopts preset algorithm that user profile and the close string of server are carried out encryption, and the user profile and the first close string is stored in the client.
In embodiments of the present invention, said user profile is one or more combinations in user's unique identification, the IP address.
The second close module 33 of concatenating into when the user lands once more, receives the said user profile and the said first close string that client is sent, said user profile is carried out encryption generate the second close string, and the second close string is identical with the generation method of the first close string.This module also comprises a junior unit:
The second close unit 331 of concatenating into when the user lands once more, receives the said user profile and the said first close string that client is sent, said user profile is carried out encryption generate the second close string, and the second close string is identical with the generation method of the first close string.
Logging status determination module 34 when the second close string equates with the first close string, keeps user's logging status; When the second close string and the first close string are unequal, user's logging status authentication failed.
In embodiments of the present invention, whether server equates to verify with the first close string that is stored in client in advance whether user's logging status can good authentication through comparing the second close string.
In embodiments of the present invention, when the user's login system first time or website, adopt preset algorithm that user profile is encrypted, generate the first close string.When the user logins identical system or website once more; Server adopts preset algorithm that user profile and the close string of server are carried out encryption; After generating the second close string, verify the logging status of said user profile respective user through comparing the said second close string and the said first close string.Because user profile is kept at client, server is only preserved a close string of server, does not take server resource, has greatly reduced load of server.Even when visit capacity is big, also can guaranteed performance, well promoted user experience.And the stronger complexity that has according to the close method of concatenating into close string of user profile and server can prevent to be cracked.
One of ordinary skill in the art will appreciate that; Realize that all or part of step in the foregoing description method is to instruct relevant hardware to accomplish through program; Described program can be in being stored in a computer read/write memory medium; Described storage medium is like ROM/RAM, disk, CD etc.
The above is merely preferred embodiment of the present invention, not in order to restriction the present invention, all any modifications of within spirit of the present invention and principle, being done, is equal to and replaces and improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. a method of verifying user's logging status is characterized in that, said method comprises the steps:
Server receives the user profile that client is sent, and the first close string is stored in client, and the said first close string comprises by the user profile after the said server for encrypting processing;
When landing once more, client is sent said user profile and the said first close string to said server, and said server carries out encryption to said user profile and generates the second close string;
Verify the logging status of said user profile respective user through comparing the said second close string and the said first close string.
2. the method for claim 1 is characterized in that, said user profile is one or more combinations in user's unique identification, the IP address.
3. the method for claim 1 is characterized in that, receives at said server before the step of the user profile that client imports into and the first close string, and said method also comprises:
The user profile that the said client of server authentication is imported into.
4. the method for claim 1 is characterized in that, the said first close string and the second close string also comprise by the close string of server after the said server for encrypting processing.
5. method as claimed in claim 4 is characterized in that, the close string of said server is generated or be stored in advance server at random by server.
6. the method for claim 1 is characterized in that, said server adopts non-reversible algorithm to carry out encryption.
7. method as claimed in claim 6 is characterized in that, said non-reversible algorithm is a hash algorithm.
8. the device in checking user logging status is characterized in that said device is built in server, and said device comprises:
The first close module of concatenating into receives the user profile that client is imported into, and the first close string is stored in client, and the said first close string comprises by the user profile after the server for encrypting processing;
The second close module of concatenating into when landing once more, receives the said user profile and the said first close string that client is sent, said user profile is carried out encryption generate the second close string;
Logging status is preserved module, verifies the logging status of said user profile respective user through comparing the said second close string and the said first close string.
9. device as claimed in claim 8 is characterized in that, said device also comprises:
Subscriber authentication module is used to verify the user authentication information of the user input that receives.
10. a business system is characterized in that, said system comprises the device of claim 8 or 9 described checking user logging status.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2010105657990A CN102480474A (en) | 2010-11-30 | 2010-11-30 | Method, device and enterprise system for verifying user login state |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2010105657990A CN102480474A (en) | 2010-11-30 | 2010-11-30 | Method, device and enterprise system for verifying user login state |
Publications (1)
Publication Number | Publication Date |
---|---|
CN102480474A true CN102480474A (en) | 2012-05-30 |
Family
ID=46092956
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN2010105657990A Pending CN102480474A (en) | 2010-11-30 | 2010-11-30 | Method, device and enterprise system for verifying user login state |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN102480474A (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102946384A (en) * | 2012-10-24 | 2013-02-27 | 北京奇虎科技有限公司 | User authentication method and device |
CN103001770A (en) * | 2012-10-24 | 2013-03-27 | 北京奇虎科技有限公司 | User verification method, user verification server and user verification system |
CN105933302A (en) * | 2016-04-14 | 2016-09-07 | 北京思特奇信息技术股份有限公司 | Repeated job number login method and system |
CN108092937A (en) * | 2016-11-23 | 2018-05-29 | 厦门雅迅网络股份有限公司 | Prevent the method and system of Web system unauthorized access |
CN108667604A (en) * | 2018-04-24 | 2018-10-16 | 湖南东方华龙信息科技有限公司 | Sharable network identity generation method |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1937498A (en) * | 2006-10-09 | 2007-03-28 | 网之易信息技术(北京)有限公司 | Dynamic cipher authentication method, system and device |
CN101075875A (en) * | 2007-06-14 | 2007-11-21 | 中国电信股份有限公司 | Method and system for realizing monopoint login between gate and system |
CN101421970A (en) * | 2004-01-12 | 2009-04-29 | 思科技术公司 | Avoiding server storage of client state |
-
2010
- 2010-11-30 CN CN2010105657990A patent/CN102480474A/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101421970A (en) * | 2004-01-12 | 2009-04-29 | 思科技术公司 | Avoiding server storage of client state |
CN1937498A (en) * | 2006-10-09 | 2007-03-28 | 网之易信息技术(北京)有限公司 | Dynamic cipher authentication method, system and device |
CN101075875A (en) * | 2007-06-14 | 2007-11-21 | 中国电信股份有限公司 | Method and system for realizing monopoint login between gate and system |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102946384A (en) * | 2012-10-24 | 2013-02-27 | 北京奇虎科技有限公司 | User authentication method and device |
CN103001770A (en) * | 2012-10-24 | 2013-03-27 | 北京奇虎科技有限公司 | User verification method, user verification server and user verification system |
CN103001770B (en) * | 2012-10-24 | 2016-06-01 | 北京奇虎科技有限公司 | A kind of user rs authentication method, server and system |
CN102946384B (en) * | 2012-10-24 | 2016-10-05 | 北京奇虎科技有限公司 | User authentication method and equipment |
CN105933302A (en) * | 2016-04-14 | 2016-09-07 | 北京思特奇信息技术股份有限公司 | Repeated job number login method and system |
CN108092937A (en) * | 2016-11-23 | 2018-05-29 | 厦门雅迅网络股份有限公司 | Prevent the method and system of Web system unauthorized access |
CN108092937B (en) * | 2016-11-23 | 2021-04-20 | 厦门雅迅网络股份有限公司 | Method and system for preventing unauthorized access of Web system |
CN108667604A (en) * | 2018-04-24 | 2018-10-16 | 湖南东方华龙信息科技有限公司 | Sharable network identity generation method |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN109716375B (en) | Block chain account processing method, device and storage medium | |
CN101425897B (en) | Customer authentication method, system, server and customer node | |
KR101082917B1 (en) | Method for verifying the integrity of a user's data in remote computing and System thereof | |
CN103731475B (en) | A kind of data protection system | |
CN102420836A (en) | Sign-on method and sign-on management system for service information system | |
US9313185B1 (en) | Systems and methods for authenticating devices | |
CN102480474A (en) | Method, device and enterprise system for verifying user login state | |
US20080155669A1 (en) | Multiple account authentication | |
CN108965275B (en) | Method and system for experiencing game | |
CN103763326A (en) | Website one-stop log-in method and system based on Memcache and Cookie | |
CN110620669A (en) | Data security method and system based on quantum random number | |
CN110336807A (en) | A kind of identity identifying method based on Web service, equipment and storage medium | |
CN102143131A (en) | User logout method and authentication server | |
CN107862198A (en) | One kind accesses verification method, system and client | |
CN102769629B (en) | Client-side password storage method and service system | |
CN106127081B (en) | The open data fault-tolerant method for secure storing that can verify that | |
CN101325483A (en) | Method and apparatus for updating symmetrical cryptographic key, symmetrical ciphering method and symmetrical deciphering method | |
CN106919348A (en) | Distributed memory system and storage method that anti-violence is cracked | |
Agarkhed et al. | An efficient auditing scheme for data storage security in cloud | |
US20160350518A1 (en) | Method for verifying web system license based on multi-way tree search | |
CN107248997A (en) | Authentication method based on smart card under environment of multi-server | |
CN112291218B (en) | Equipment identity authentication method based on two-dimensional code double fusion encryption algorithm | |
CN103051614A (en) | Secure access and data transmission method for cloud platform | |
CN102195983B (en) | network terminal encryption authentication method and server | |
US11902428B2 (en) | Key exchange system, communication apparatus, key exchange method and program |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C12 | Rejection of a patent application after its publication | ||
RJ01 | Rejection of invention patent application after publication |
Application publication date: 20120530 |