CN113364798A - Redis-based user access frequency processing device - Google Patents
Redis-based user access frequency processing device Download PDFInfo
- Publication number
- CN113364798A CN113364798A CN202110683560.1A CN202110683560A CN113364798A CN 113364798 A CN113364798 A CN 113364798A CN 202110683560 A CN202110683560 A CN 202110683560A CN 113364798 A CN113364798 A CN 113364798A
- Authority
- CN
- China
- Prior art keywords
- user
- token
- redis
- access
- url
- 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
Images
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/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
-
- 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/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a Redis-based user access frequency processing device, which belongs to the technical field of communication and comprises four modules: the system comprises a configuration module, a user access frequency control module, a user authentication module and a user authentication module. The internet project authorization service is realized through the four modules. The invention has the advantages that: the access frequency of the user is controlled by adopting an ip address, the user is authenticated and authenticated by adopting a user token (token), and the token is stored by adopting Redis, so that the safety, the stability and the efficiency are obviously improved; the token is used as parameter transmission, and the compatibility problem of crossing clients and different languages is solved.
Description
Technical Field
The invention relates to the technical field of communication, in particular to a Redis-based user access frequency processing device.
Background
The HTTP/HTTPs protocol is a stateless protocol that does not record who the request message was sent. The user sends a request, and the server receives the request and returns data according to the request. HTTP protocol transport causes a problem: if a server does not have a user authentication and authorization mechanism, only the URL is needed, and any user can access the server application, which obviously does not meet the security requirement of the server. In order to ensure the security of the application of the server, most websites require the user to perform user name and password authentication before using the application, and after the authentication is passed, the user can request corresponding resources from the server. However, this also brings a problem that the user needs username and password authentication every time the user requests the resource, and this solution, while ensuring security, is extremely resource-consuming if the server needs to perform username and password authentication every time and is also extremely unfriendly for the user. In order to compromise efficiency and safety, the following solutions have emerged: after the user performs identity authentication through the user name and the password, the server generates a record, the record stores the unique identifier of the current user, the server returns the identifier to the user, the user carries the unique identifier when requesting again, the server verifies the identifier, the server returns resources after the verification is passed, and otherwise, the server does not return the resources.
Redis (remote Dictionary Server), a remote Dictionary service, is an open source log-type and Key-Value database written in ANSI C language, supporting network, based on memory and persistent, and provides API of multiple languages. Redis is a high-performance key-value database which can execute about 110000 write operations or 81000 read operations per second, and supports a master-slave mode, a cluster mode and the like, and is a mainstream NoSQL database in the Internet world today.
The traditional user authentication method is performed by a server (e.g., Tomcat), which takes Tomcat as an example, the Tomcat uses JESSIONID as a unique identifier of a client, and then stores the JESSIONID in a cookie, and the cookie is carried by the client and the server in subsequent communication, and the server also verifies the cookie. Although this method solves the problem that each request needs user name and password verification, with the development of the internet, more and more requests need to be processed by the server, and the above solution causes huge pressure on the server and cannot realize cross-server user authentication.
Disclosure of Invention
In order to solve the technical problems, the invention provides a device for controlling, authorizing and authenticating user access frequency based on Redis, which aims at solving the problems of how to apply the Redis to the control of the user access frequency, the user authentication and the user authentication so as to relieve the pressure of a server, realize cross-server authorization and protect back-end application.
The invention separates the user access frequency control, the user authentication and the user authorization from the back-end service through the access frequency limited by Redis, the token issued by the user and the user authentication, and the user access frequency control, the user authentication and the user authorization are firstly carried out when the user access request reaches the back-end service.
The technical scheme of the invention is as follows:
a user access frequency processing device based on Redis adopts token as a user mark, and realizes the storage and authentication of user identification (token) by Redis replacing a server, thereby greatly relieving the pressure of the server and solving the problem of cross-server user authentication; at the same time, Redis can authenticate and judge whether the user has the right to access a certain URL; and the Redis is utilized to control the user access frequency, so that the purpose of protecting the back-end application is achieved.
Comprises a configuration module, a user access frequency control module, a user authentication module and a user authentication module,
wherein the content of the first and second substances,
a configuration module: configuring parameters required by a user access frequency control module, a user authentication module and a user authentication module;
the user access frequency control module: querying whether the latest access times of the user exceed the limit by utilizing Redis;
a user authentication module: checking whether a user corresponding to the token exists or not, verifying whether the user who logs in for the first time is a legal user or not, and issuing the token for the legal user who logs in for the first time;
a user authentication module: and verifying whether the user has the right to access the requested URL by utilizing Redis.
Further, in the above-mentioned case,
the configuration module may configure a white list, a black list, an access frequency, a resource accessible by the user, and a token validity time of the user.
Further, in the above-mentioned case,
the user access control frequency module: detecting whether the recent access frequency of a user exceeds a limit or not so as to prevent the system from being attacked maliciously; acquiring an ip address of a user, inquiring whether the access frequency corresponding to the ip address exceeds the limit in Redis, if so, returning immediately without executing the next flow, otherwise, allowing the next flow to continue, and adding 1 to the access frequency of the user in Redis. In Redis, the user's access frequency is time-limited, and if this time limit is exceeded, Redis automatically deletes the record.
Further, in the above-mentioned case,
a user authentication module: if the user does not carry the token during the access or the token of the user stored in the Redis is expired, which indicates that the token is invalid due to the initial login of the user or the user does not request for too long, the user needs to enter an authentication module to perform authentication to generate the token for issuing.
The authentication process is as follows:
inquiring user information according to the token in Redis, if the token is inquired, resetting the expiration time corresponding to the token, if the token is not inquired, indicating that the user is redirected to a login page, setting a login interface in a white list, not inquiring the token in Redis, but verifying whether the user is a legal user according to a user name and a password in a Mysql database, if not, immediately terminating the process and returning error prompt information; if a legitimate user, a token is issued for the user, stored in Redis and an expiration time is set.
Further, in the above-mentioned case,
a user authentication module: in the user authentication module, if the user logs in for the first time and passes the verification, the user goes to the Mysql database to take out the URL which can be accessed by the user and stores the URL in Redis along with token; when the user authenticates the token to be legal through the user authentication module, the user authentication module is entered to judge whether the user can access the corresponding URL, if the user can access the URL, the user authentication module passes the request of the user, otherwise, the user request is terminated.
In a still further aspect of the present invention,
the initial login procedure is as follows:
the method comprises the following steps: a user logs in at a client and requests authorization;
step two: the user requests to reach the authentication service, an ip address of the user is obtained, the latest access times of the user are inquired in Redis according to the ip address, and if the access times exceed the access times limit, the process is terminated; otherwise, the Redis adds 1 to the user access times and continues the next steps;
step three: the user carries out authentication, as the user logs in for the first time and does not carry token parameters, the user name and the password are verified in the Mysql, and if the user name and the password pass the verification, the URL allowing the user to access is continuously taken out from the Mysql;
step four: generating a token, storing the token into the Redis, setting the storage period of the token, simultaneously storing the user information corresponding to the token and the URL allowed to be accessed by the user, returning to the token, and finishing the user login.
The flow is as follows when the user requests again:
the method comprises the following steps: the user accesses the client according to the URL;
step two: the user requests to reach the authentication service, an ip address of the user is obtained, the latest access times of the user are inquired in Redis according to the ip address, and if the access times exceed the access times limit, the process is terminated; otherwise, the Redis adds 1 to the user access times and continues the next steps;
step three: the user carries out authentication, because the user does not log in for the first time and carries token parameters, the user directly goes to Redis to search whether a token exists, if the token is not obtained, the token is indicated to be deleted after being expired or the request is illegal access which is not logged in by the user, and in this case, the user directly returns to redirect to a login interface; if the token is acquired, extracting URL information corresponding to the token from the Redis, wherein the URL information is a URL which is allowed to be accessed by a user holding the token;
step four: and comparing the URL requested by the user at this time with the URL allowed to be requested by the user, if the URL is matched with the URL, releasing the user, and finally reaching the back-end system, otherwise, terminating the user request and prompting that the user has no access right.
The invention has the advantages that
(1) The invention controls the access frequency of the user, can prevent the system from being maliciously attacked and protects the safety of the back-end service.
(2) The invention utilizes Redis storage token to greatly relieve the processing pressure and the storage pressure when the server stores the unique mark of the user, solves the authentication problem of the user accessing across servers, and improves the access processing capability of the system as a whole because Redis has excellent read-write performance.
(3) The invention limits the URL which can be accessed by the user, prevents the user from unauthorized access and improves the safety of the system.
Drawings
FIG. 1 is a schematic diagram of the operation of the module of the present invention
FIG. 2 is a schematic diagram of the overall architecture of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer and more complete, the technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention, and based on the embodiments of the present invention, all other embodiments obtained by a person of ordinary skill in the art without creative efforts belong to the scope of the present invention.
The invention comprises four modules: the system comprises a configuration module, a user access frequency control module, a user authentication module and a user authentication module, which are shown in the figure I. User authentication, user authentication and user access frequency control are realized through the four modules. The functions mainly responsible for each module are as follows:
a configuration module: and configuring parameters required by the user access frequency control module, the user authentication module and the user authentication module.
The user access frequency control module: and querying whether the latest access times of the user exceed the limit by utilizing Redis.
A user authentication module: checking whether a user corresponding to the token exists or not, verifying whether the user who logs in for the first time is a legal user or not, and issuing the token for the legal user who logs in for the first time
A user authentication module: and verifying whether the user has the right to access the requested URL by utilizing Redis.
These large modules are explained in detail below.
A configuration module: and configuring parameters required by the user access frequency control module, the user authentication module and the user authentication module. For example, a user's whitelist, blacklist, frequency of access, resources accessible to the user, token validity time, etc. may be configured.
The user access control frequency module: the module mainly detects whether the recent access frequency of a user exceeds a limit or not so as to prevent the system from being attacked maliciously. Acquiring an ip address of a user, inquiring whether the access frequency corresponding to the ip address exceeds the limit or not in Redis, if so, returning immediately without executing the next flow, otherwise, allowing the next flow to continue, and adding 1 to the access frequency of the user in Redis; in Redis, the user's access frequency is time-limited, and if this time limit is exceeded, Redis automatically deletes the record.
A user authentication module: if the user does not carry the token during the access or the token of the user stored in the Redis is expired, which indicates that the token is invalid due to the initial login of the user or the user does not request for too long, the user needs to enter an authentication module to perform authentication to generate the token for issuing. The authentication process is as follows: inquiring user information according to the token in Redis, if the token is inquired, resetting the expiration time corresponding to the token, if the token is not inquired, indicating that the user is redirected to a login page, setting a login interface in a white list, so that the token cannot be inquired in Redis, but the Mysql database is used for verifying whether the user is a legal user according to a user name and a password, if not, immediately terminating the process, and returning error prompt information; if a legitimate user, a token is issued for the user, stored in Redis and an expiration time is set.
A user authentication module: in the user authentication module, if the user logs in for the first time and passes the verification, the user goes to the Mysql database to take out the URL which can be accessed by the user and stores the URL in Redis along with token; when the user authenticates the token to be legal through the user authentication module, the user authentication module is entered to judge whether the user can access the corresponding URL, if the user can access the URL, the user authentication module passes the request of the user, otherwise, the user request is terminated.
The invention solves the problems of user access frequency control, user authentication and user authentication through the four modules, and refers to a second figure. The initial login procedure is as follows:
the method comprises the following steps: and the user logs in at the client to request authorization.
Step two: the user requests to reach the authentication service, an ip address of the user is obtained, the latest access times of the user are inquired in Redis according to the ip address, and if the access times exceed the access times limit, the process is terminated; otherwise, Redis increments the user access number by 1 and continues with the next step.
Step three: and (3) authenticating the user, and if the user logs in for the first time and does not carry the token parameter, verifying the user name and the password in the Mysql, and if the user passes the verification, continuously taking out the URL allowing the user to access from the Mysql.
Step four: generating a token, storing the token into the Redis, setting the storage period of the token, simultaneously storing the user information corresponding to the token and the URL allowed to be accessed by the user, returning to the token, and finishing the user login.
The flow is as follows when the user requests again:
the method comprises the following steps: the user accesses at the client according to the URL
Step two: the user requests to reach the authentication service, an ip address of the user is obtained, the latest access times of the user are inquired in Redis according to the ip address, and if the access times exceed the access times limit, the process is terminated; otherwise, Redis increments the user access number by 1 and continues with the next step.
Step three: the user carries out authentication, because the user does not log in for the first time and carries token parameters, the user directly goes to Redis to search whether a token exists, if the token is not obtained, the token is indicated to be deleted after being expired or the request is illegal access which is not logged in by the user, and in this case, the user directly returns to redirect to a login interface; if the token is acquired, the URL information corresponding to the token is taken out from the Redis, and the URL information is the URL which the user holding the token allows to access
Step four: and comparing the URL requested by the user at this time with the URL allowed to be requested by the user, if the URL is matched with the URL, releasing the user, and finally reaching the back-end system, otherwise, terminating the user request and prompting that the user has no access right.
The invention utilizes the characteristic that the block chain can not be tampered to store the data full-factor information, and carries out modeling analysis on the stored information according to the valuation model, thereby obtaining more accurate data valuation.
The data can be described in all directions, including but not limited to data examples, data feature information, data browsing information, data historical transaction information, and the like.
The block chain distributed storage and the characteristic of difficult tampering are utilized to store all data elements, so that the information is more reliable and accurate, and the evaluation value is more reliable.
And carrying out modeling analysis according to the data full-element information, the buyer data demand, the purchase record, the same-class data transaction condition in the platform, the seller data cost and the like to obtain a data approximate evaluation value.
The above description is only a preferred embodiment of the present invention, and is only used to illustrate the technical solutions of the present invention, and not to limit the protection scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (9)
1. A Redis-based user access frequency processing apparatus,
adopting token as user mark, using Redis to replace server to realize user mark storage and authentication; at the same time, Redis authenticates and judges whether the user has the authority to access the URL; and controlling the user access frequency by utilizing Redis to achieve the purpose of protecting the back-end application;
comprises a configuration module, a user access frequency control module, a user authentication module and a user authentication module,
wherein the content of the first and second substances,
a configuration module: configuring parameters required by a user access frequency control module, a user authentication module and a user authentication module;
the user access frequency control module: querying whether the latest access times of the user exceed the limit by utilizing Redis;
a user authentication module: checking whether a user corresponding to the token exists or not, verifying whether the user who logs in for the first time is a legal user or not, and issuing the token for the legal user who logs in for the first time;
a user authentication module: and verifying whether the user has the right to access the requested URL by utilizing Redis.
2. The apparatus of claim 1,
the configuration module may configure a white list, a black list, an access frequency, a resource accessible by the user, and a token validity time of the user.
3. The apparatus of claim 1,
the user access control frequency module: detecting whether the recent access frequency of a user exceeds a limit or not so as to prevent the system from being attacked maliciously; acquiring an ip address of a user, inquiring whether the access frequency corresponding to the ip address exceeds the limit in Redis, if so, returning immediately without executing the next flow, otherwise, allowing the next flow to continue, and adding 1 to the access frequency of the user in Redis.
4. The apparatus of claim 3,
in Redis, the user's access frequency is time-limited, and if this time limit is exceeded, Redis automatically deletes the record.
5. The apparatus of claim 1,
a user authentication module: if the user does not carry the token during the access or the token of the user stored in the Redis is expired, which indicates that the token is invalid due to the initial login of the user or the user does not request for too long, the user needs to enter an authentication module to perform authentication to generate the token for issuing.
6. The apparatus of claim 5,
the authentication process is as follows:
inquiring user information according to the token in Redis, if the token is inquired, resetting the expiration time corresponding to the token, if the token is not inquired, indicating that the user is redirected to a login page, setting a login interface in a white list, not inquiring the token in Redis, but verifying whether the user is a legal user according to a user name and a password in a Mysql database, if not, immediately terminating the process and returning error prompt information; if a legitimate user, a token is issued for the user, stored in Redis and an expiration time is set.
7. The apparatus of claim 1,
a user authentication module: in the user authentication module, if the user logs in for the first time and passes the verification, the user goes to the Mysql database to take out the URL which can be accessed by the user and stores the URL in Redis along with token; when the user authenticates the token to be legal through the user authentication module, the user authentication module is entered to judge whether the user can access the corresponding URL, if the user can access the URL, the user authentication module passes the request of the user, otherwise, the user request is terminated.
8. The apparatus of claim 1,
the initial login procedure is as follows:
the method comprises the following steps: a user logs in at a client and requests authorization;
step two: the user requests to reach the authentication service, an ip address of the user is obtained, the latest access times of the user are inquired in Redis according to the ip address, and if the access times exceed the access times limit, the process is terminated; otherwise, the Redis adds 1 to the user access times and continues the next steps;
step three: the user carries out authentication, as the user logs in for the first time and does not carry token parameters, the user name and the password are verified in the Mysql, and if the user name and the password pass the verification, the URL allowing the user to access is continuously taken out from the Mysql;
step four: generating a token, storing the token into the Redis, setting the storage period of the token, simultaneously storing the user information corresponding to the token and the URL allowed to be accessed by the user, returning to the token, and finishing the user login.
9. The apparatus of claim 8,
the flow is as follows when the user requests again:
the method comprises the following steps: the user accesses the client according to the URL;
step two: the user requests to reach the authentication service, an ip address of the user is obtained, the latest access times of the user are inquired in Redis according to the ip address, and if the access times exceed the access times limit, the process is terminated; otherwise, the Redis adds 1 to the user access times and continues the next steps;
step three: the user carries out authentication, because the user does not log in for the first time and carries token parameters, the user directly goes to Redis to search whether a token exists, if the token is not obtained, the token is indicated to be deleted after being expired or the request is illegal access which is not logged in by the user, and in this case, the user directly returns to redirect to a login interface; if the token is acquired, extracting URL information corresponding to the token from the Redis, wherein the URL information is a URL which is allowed to be accessed by a user holding the token;
step four: and comparing the URL requested by the user at this time with the URL allowed to be requested by the user, if the URL is matched with the URL, releasing the user, and finally reaching the back-end system, otherwise, terminating the user request and prompting that the user has no access right.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110683560.1A CN113364798A (en) | 2021-06-21 | 2021-06-21 | Redis-based user access frequency processing device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110683560.1A CN113364798A (en) | 2021-06-21 | 2021-06-21 | Redis-based user access frequency processing device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113364798A true CN113364798A (en) | 2021-09-07 |
Family
ID=77535312
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110683560.1A Pending CN113364798A (en) | 2021-06-21 | 2021-06-21 | Redis-based user access frequency processing device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113364798A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115549970A (en) * | 2022-08-29 | 2022-12-30 | 紫光云技术有限公司 | Method for authenticating lightweight failed JWT token by oauth2 |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017028804A1 (en) * | 2015-08-19 | 2017-02-23 | 中兴通讯股份有限公司 | Web real-time communication platform authentication and access method and device |
| CN110535851A (en) * | 2019-08-27 | 2019-12-03 | 浪潮云信息技术有限公司 | A kind of customer certification system based on oauth2 agreement |
| CN111031008A (en) * | 2019-11-25 | 2020-04-17 | 集奥聚合(北京)人工智能科技有限公司 | Method for gateway to uniformly intercept user request and judge whether to release |
| CN112104673A (en) * | 2020-11-12 | 2020-12-18 | 中博信息技术研究院有限公司 | Multimedia resource web access authority authentication method |
| CN112468409A (en) * | 2020-11-24 | 2021-03-09 | 平安消费金融有限公司 | Access control method, device, computer equipment and storage medium |
| CN112583600A (en) * | 2020-11-26 | 2021-03-30 | 平安普惠企业管理有限公司 | User authentication method, device, electronic equipment and medium |
| CN112597472A (en) * | 2021-03-03 | 2021-04-02 | 北京视界云天科技有限公司 | Single sign-on method, device and storage medium |
| CN112887284A (en) * | 2021-01-14 | 2021-06-01 | 北京电解智科技有限公司 | Access authentication method and device |
-
2021
- 2021-06-21 CN CN202110683560.1A patent/CN113364798A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017028804A1 (en) * | 2015-08-19 | 2017-02-23 | 中兴通讯股份有限公司 | Web real-time communication platform authentication and access method and device |
| CN110535851A (en) * | 2019-08-27 | 2019-12-03 | 浪潮云信息技术有限公司 | A kind of customer certification system based on oauth2 agreement |
| CN111031008A (en) * | 2019-11-25 | 2020-04-17 | 集奥聚合(北京)人工智能科技有限公司 | Method for gateway to uniformly intercept user request and judge whether to release |
| CN112104673A (en) * | 2020-11-12 | 2020-12-18 | 中博信息技术研究院有限公司 | Multimedia resource web access authority authentication method |
| CN112468409A (en) * | 2020-11-24 | 2021-03-09 | 平安消费金融有限公司 | Access control method, device, computer equipment and storage medium |
| CN112583600A (en) * | 2020-11-26 | 2021-03-30 | 平安普惠企业管理有限公司 | User authentication method, device, electronic equipment and medium |
| CN112887284A (en) * | 2021-01-14 | 2021-06-01 | 北京电解智科技有限公司 | Access authentication method and device |
| CN112597472A (en) * | 2021-03-03 | 2021-04-02 | 北京视界云天科技有限公司 | Single sign-on method, device and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115549970A (en) * | 2022-08-29 | 2022-12-30 | 紫光云技术有限公司 | Method for authenticating lightweight failed JWT token by oauth2 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8615794B1 (en) | Methods and apparatus for increased security in issuing tokens | |
| CN110381031B (en) | Single sign-on method, device, equipment and computer readable storage medium | |
| CN112597472B (en) | Single sign-on method, device and storage medium | |
| US9047458B2 (en) | Network access protection | |
| US20130047202A1 (en) | Apparatus and Method for Handling Transaction Tokens | |
| US20130160144A1 (en) | Entity verification via third-party | |
| US20130046696A1 (en) | Method and Apparatus for Object Transaction Session Validation | |
| US8806602B2 (en) | Apparatus and method for performing end-to-end encryption | |
| CN105577835B (en) | Cross-platform single sign-on system based on cloud computing | |
| CN110535884B (en) | Method, device and storage medium for cross-enterprise inter-system access control | |
| US8752157B2 (en) | Method and apparatus for third party session validation | |
| CN108632241B (en) | Unified login method and device for multiple application systems | |
| US8572690B2 (en) | Apparatus and method for performing session validation to access confidential resources | |
| KR20130103537A (en) | User account recovery | |
| US11444936B2 (en) | Managing security credentials | |
| CN112492028A (en) | Cloud desktop login method and device, electronic equipment and storage medium | |
| CN111291353B (en) | Account number association method and device and computer storage medium | |
| US8572724B2 (en) | Method and apparatus for network session validation | |
| CN110944021A (en) | Method and system for campus unified authentication and single sign-on | |
| US20150066766A1 (en) | Secure Generation of a User Account in a Service Server | |
| CN113364798A (en) | Redis-based user access frequency processing device | |
| CN106529216B (en) | Software authorization system and software authorization method based on public storage platform | |
| CN116668190A (en) | Cross-domain single sign-on method and system based on browser fingerprint | |
| US8572688B2 (en) | Method and apparatus for session validation to access third party resources | |
| US8584201B2 (en) | Method and apparatus for session validation to access from uncontrolled devices |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210907 |