CN113922986A - Multi-terminal authority management method and equipment - Google Patents
Multi-terminal authority management method and equipment Download PDFInfo
- Publication number
- CN113922986A CN113922986A CN202111057388.5A CN202111057388A CN113922986A CN 113922986 A CN113922986 A CN 113922986A CN 202111057388 A CN202111057388 A CN 202111057388A CN 113922986 A CN113922986 A CN 113922986A
- Authority
- CN
- China
- Prior art keywords
- terminal
- login
- data
- page
- entering
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 15
- 238000000034 method Methods 0.000 claims abstract description 15
- 230000009191 jumping Effects 0.000 claims description 9
- 238000001914 filtration Methods 0.000 claims description 4
- 238000012216 screening Methods 0.000 claims description 3
- 230000004927 fusion Effects 0.000 abstract description 5
- 238000012795 verification Methods 0.000 description 5
- 238000013475 authorization Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000009877 rendering Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
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
-
- 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/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/105—Multiple levels of security
-
- 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)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a multi-terminal authority management method and equipment, wherein the method comprises the following steps: after entering a terminal page of the system, acquiring cached encrypted login data based on a token of a terminal entry address; entering a login page corresponding to the terminal based on the dynamic routing data in the encrypted login data and the routing data in the session storage; and storing the dynamic routing data into the session storage, and entering a terminal login success page, so that the problem of different standard specifications of menu components, menu items, authentication modes and authority control in a multi-terminal environment of the SaaS system is solved, the menu fusion efficiency is improved, and the cost is reduced.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a multi-terminal rights management method and device.
Background
The SaaS provider builds all network infrastructures, software and hardware operation platforms required by informatization for enterprises and is responsible for a series of services such as implementation in the early stage, maintenance in the later stage and the like, and the enterprises can use the information system through the Internet without purchasing software and hardware, building a machine room and recruiting IT personnel. The SaaS is a software layout model, and is designed for network delivery by application, and is convenient for users to host, deploy and access through the internet.
The SaaS system usually maintains the authority data of the whole system in a system-set login, menu, and authority management manner, so that different templates and different systems cannot share the same data, and a user needs to separately maintain a user entry when entering different systems, thereby resulting in low development efficiency and easily solving the same problem in multiple times.
Therefore, how to solve the technical problems that the authority data of the SaaS system is not uniform when multiple terminals exist and the operation cost is high is to be solved at present.
Disclosure of Invention
The invention provides a multi-terminal authority management method, which is applied to a SaaS software service system and is used for solving the technical problems of non-uniform authority data and high operation cost of the SaaS system in the prior art when multiple terminals exist.
The method comprises the following steps:
after entering a terminal page of the system, acquiring cached encrypted login data based on a token of a terminal entry address;
entering a login page corresponding to the terminal based on the dynamic routing data in the encrypted login data and the routing data in the session storage;
and storing the dynamic routing data into the session storage, and entering a terminal login success page.
In some embodiments of the present application, before obtaining the cached encrypted login data based on the token of the terminal entry address, the method further includes:
and configuring the incidence relation between the menu items and each terminal, the opening mode of the menu items and the positioning mode of the pages corresponding to the menu items.
In some embodiments of the present application, the obtaining of the cached encrypted login data by the token based on the terminal entry address specifically includes:
judging whether the token exists in the terminal entry address or not;
if so, verifying the token and acquiring the cached encrypted login data;
and if not, jumping to a preset unified login page from the terminal page for login.
In some embodiments of the present application, the verifying the token and obtaining the cached encrypted login data specifically include:
when the token is verified, obtaining the cached encrypted login data;
when the token is not checked, jumping to a preset unified login page from the terminal page
In some embodiments of the present application, entering a login page corresponding to the terminal based on the dynamic routing data in the encrypted login data and the routing data in the session storage specifically includes:
judging whether dynamic routing data in the encrypted login data exist or not;
if so, directly entering a terminal login success page through terminal page skipping;
and if not, entering a login page corresponding to the terminal based on the routing data in the session storage.
In some embodiments of the present application, entering a login page corresponding to the terminal based on the routing data in the session storage specifically includes:
if the routing data in the session storage exists, creating the dynamic routing data according to a diff algorithm, storing the dynamic routing data in the session storage, and entering a terminal login success page;
and if the routing data in the session storage does not exist, jumping to a preset uniform login page from the terminal page for login.
In some embodiments of the present application, the creating the dynamic routing data according to a diff algorithm specifically includes:
screening menu information which can be accessed by a current user from a local menu according to code encoding through a diff algorithm;
matching the authority data of the user through the accessible menu information;
and generating corresponding dynamic routing data for each authority data, so that the current user can only access the configured address data, and other addresses are uniformly redirected to the page 404.
In some embodiments of the present application, matching the authority data of the user through the accessible menu information specifically includes:
flattening the authority tree transmitted by the background;
putting each node in the background tree into a temp object;
and traversing the front-end routing tree through depth priority, and then filtering out the routing node corresponding to the authority data of the user by judging whether the current node exists in the temp object.
In some embodiments of the present application, the method further comprises:
and after entering the terminal login success page, acquiring the authority data of the current page through a preset instruction.
Correspondingly, the invention also provides a multi-terminal authority management device, which comprises:
the acquisition module is used for acquiring the cached encrypted login data based on the token of the terminal entry address after entering the terminal page of the system;
the first login module is used for entering a login page corresponding to the terminal based on dynamic routing data in the encrypted login data and routing data in session storage;
and the second login module is used for storing the dynamic routing data into the session storage and entering a terminal login success page.
By applying the technical scheme, after entering a terminal page of the system, the token based on the terminal entrance address obtains the cached encrypted login data; entering a login page corresponding to the terminal based on the dynamic routing data in the encrypted login data and the routing data in the session storage; and storing the dynamic routing data into the session storage, and entering a terminal login success page, so that the problem of different standard specifications of menu components, menu items, authentication modes and authority control in a multi-terminal environment of the SaaS system is solved, the menu fusion efficiency is improved, and the cost is reduced.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a flow chart schematically illustrating a multi-terminal rights management method according to an embodiment of the present invention;
fig. 2 shows a schematic structural diagram of a multi-terminal rights management device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The embodiment of the application provides a multi-terminal authority management method, which is applied to a SaaS software service system and comprises the following steps as shown in FIG. 1:
and S101, after entering a terminal page of the system, acquiring cached encrypted login data based on a token of a terminal entrance address.
In this embodiment, as described in the background art, the SaaS system usually maintains the authority data of the entire system in a system-set login, menu, and authority management manner, so that different templates and different systems cannot share the same data, and a user needs to separately maintain a user entry when entering different systems, thereby resulting in low development efficiency, and easily solving the same problem with a lot of time. Therefore, in the present scheme, a multi-terminal rights management method is provided to solve the above problems.
When entering a terminal page, the obtaining terminal obtains cached encrypted login data at an entrance address based on token, so that user information is prevented from being leaked, current user historical login information is prevented from being cracked, a uniform authentication mode and a corresponding entrance address of each terminal are configured and defined by a specially-assigned person in different terminals, wherein the authentication mode supports an authorization code mode, an authorization code simple mode, a password authorization mode and a client mode, and when entering the terminal page, the special encrypted login data of the terminal is obtained firstly.
In order to obtain the encrypted login data, in some embodiments of the present application, before obtaining the cached encrypted login data based on the token of the terminal entry address, the method further includes:
and configuring the incidence relation between the menu items and each terminal, the opening mode of the menu items and the positioning mode of the pages corresponding to the menu items.
Specifically, the developer maintains and configures the fusion menu and the menu items, including the association relationship between the menu items and each system, the opening mode (jump or new construction) of the menu items, and the positioning mode (route or relative address or absolute address) of the page corresponding to the menu items.
In order to obtain encrypted login data, in some embodiments of the present application, a token based on a terminal entry address obtains cached encrypted login data, specifically:
judging whether the token exists in the terminal entry address or not;
if so, verifying the token and acquiring the cached encrypted login data;
and if not, jumping to a preset unified login page from the terminal page for login.
When entering a terminal page, acquiring encrypted login data cached by a terminal at an entry address based on token, judging whether the entry address of the terminal exists because a token may not exist, if not, transferring the page to a unified login page, wherein the unified login page is equivalent to a visitor page or logs in after verification fails, and entering the login address uniformly and attaching a current jump link when the login address is not logged in or login information is invalid, generally, each terminal has one login address, and in case of a great number of terminals, a set of login authentication modes need to be developed for each terminal, and for the condition, a unified authentication mode is used, namely, each terminal does not need to develop authentication, and a user can enter different terminals by using the same login address through a unified configuration mode, and if the encrypted login data exists, the token is verified, and the cached encrypted login data is obtained.
In order to obtain encrypted login data, in some embodiments of the present application, the token is verified, and the cached encrypted login data is obtained, specifically:
when the token is verified, obtaining the cached encrypted login data;
and when the token is not checked, jumping to a preset unified login page by the terminal page.
Specifically, whether the token verification is successful or not needs to be checked, if the verification is failed, the page is transferred to the unified login page to log in, and if the verification is successful, encrypted login data of the user are obtained.
And step S102, entering a login page corresponding to the terminal based on the dynamic routing data in the encrypted login data and the routing data in the session storage.
In this embodiment, after the encrypted login data is obtained, the login page corresponding to the terminal is further entered according to the dynamic routing data in the encrypted login data and the routing data in the session storage, and the login flow and the login steps are different according to the difference between the dynamic routing data and the routing data in the session storage.
In order to enter the login page corresponding to the terminal, in some embodiments of the present application, the entry into the login page corresponding to the terminal is based on the dynamic routing data in the encrypted login data and the routing data in the session storage, which specifically includes:
judging whether dynamic routing data in the encrypted login data exist or not;
if so, directly entering a terminal login success page through terminal page skipping;
and if not, entering a login page corresponding to the terminal based on the routing data in the session storage.
In this embodiment, it is first determined whether dynamic routing data in the encrypted login data exists, if so, a terminal page jump is performed, the dynamic routing data is stored in the session storage, and a terminal login success page is entered, a corresponding right is displayed to a user, and if not, the user needs to enter a login page corresponding to the terminal based on the routing data in the session storage.
In order to access the login page corresponding to the terminal, in some embodiments of the present application, the accessing the login page corresponding to the terminal based on the routing data in the session storage specifically includes:
if the routing data in the session storage exists, creating the dynamic routing data according to a diff algorithm, storing the dynamic routing data in the session storage, and entering a terminal login success page;
and if the routing data in the session storage does not exist, jumping to a preset uniform login page from the terminal page for login.
Specifically, if the routing data in the session storage exists, the dynamic routing data is created according to a diff algorithm, and is stored in the session storage, and the dynamic routing data enters a terminal login success page.
The cost of rendering the real DOM is very large, and sometimes, if some data is modified, the direct rendering on the real DOM causes redrawing and rearrangement of the whole DOM tree. We want to update only the small block of dom we modify, instead of the entire dom, and the diff algorithm helps us achieve this. The essence of the diff algorithm is: the difference between the two objects is found out, and the purpose is to realize node multiplexing as much as possible. The object referred to here is actually a virtual dom (virtual dom tree) in vue, i.e., a js object is used to represent the dom structure in a page.
If the routing data in the session storage does not exist, the terminal page jumps to a preset unified login page for login, the unified login page is equivalent to a visitor page or logs in after verification fails, the unified login page enters a login address and is accompanied with a current jump link under the condition of no login or failure of login information, generally, each terminal has one login address, and under the condition of a large number of terminals, a set of login authentication mode needs to be developed for each terminal, and for the condition, the unified authentication mode is used, not only does not need to develop authentication for each terminal, but also enables users to use the same login address to enter different terminals through a uniform configuration mode, and if the encrypted login data exists, the token is verified, and the cached encrypted login data is obtained.
In order to create the dynamic routing data, in some embodiments of the present application, the dynamic routing data is created according to a diff algorithm, specifically:
screening menu information which can be accessed by a current user from a local menu according to code encoding through a diff algorithm;
matching the authority data of the user through the accessible menu information;
and generating corresponding dynamic routing data for each authority data, so that the current user can only access the configured address data, and other addresses are uniformly redirected to the page 404.
Specifically, menu information which can be accessed by a current user is screened out for a local menu according to code codes through a diff algorithm; matching the authority data of the user through the accessible menu information; and generating corresponding dynamic routing data for each authority data, so that the current user can only access the configured address data, other addresses are uniformly redirected to a 404 page, and after entering a login success page, an interface and an authority button corresponding to the authority data are displayed for the user.
In order to match the authority data of the user, in some embodiments of the present application, the authority data of the user is matched through the accessible menu information, specifically:
flattening the authority tree transmitted by the background;
putting each node in the background tree into a temp object;
and traversing the front-end routing tree through depth priority, and then filtering out the routing node corresponding to the authority data of the user by judging whether the current node exists in the temp object.
Specifically, flattening processing is carried out on the background incoming lady authority tree; putting each node in the background tree into a temp object; and traversing the front-end routing tree through depth priority, and then filtering out the routing node corresponding to the authority data of the user by judging whether the current node exists in the temp object.
Step S103, storing the dynamic routing data into the session storage, and entering a terminal login success page.
And skipping a terminal page, storing the dynamic routing data into the session storage, and entering a terminal login success page.
In some embodiments of the present application, the method further comprises:
and after entering the terminal login success page, acquiring the authority data of the current page through a preset instruction.
Specifically, after entering the terminal login success page, the permission data of the current page is acquired through a preset instruction, and an interface or permission button corresponding to the permission data is displayed to a user.
By applying the technical scheme, after entering a terminal page of the system, the token based on the terminal entrance address obtains the cached encrypted login data; entering a login page corresponding to the terminal based on the dynamic routing data in the encrypted login data and the routing data in the session storage; and storing the dynamic routing data into the session storage, and entering a terminal login success page, so that the problem of different standard specifications of menu components, menu items, authentication modes and authority control in a multi-terminal environment of the SaaS system is solved, the menu fusion efficiency is improved, and the cost is reduced.
In order to further illustrate the technical idea of the present invention, the technical solution of the present invention will now be described with reference to specific application scenarios.
The embodiment of the present application further provides a multi-terminal rights management device, as shown in fig. 2, the device includes:
an obtaining module 201, configured to obtain cached encrypted login data based on a token of a terminal entry address after entering a terminal page of the system;
a first login module 202, configured to enter a login page corresponding to the terminal based on the dynamic routing data in the encrypted login data and the routing data in the session storage;
and the second login module 203 is configured to store the dynamic routing data in the session storage, and enter a terminal login success page.
By applying the technical scheme, after entering a terminal page of the system, the token based on the terminal entrance address obtains the cached encrypted login data; entering a login page corresponding to the terminal based on the dynamic routing data in the encrypted login data and the routing data in the session storage; and storing the dynamic routing data into the session storage, and entering a terminal login success page, so that the problem of different standard specifications of menu components, menu items, authentication modes and authority control in a multi-terminal environment of the SaaS system is solved, the menu fusion efficiency is improved, and the cost is reduced.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some of the technical features may be equivalently replaced; such modifications and substitutions do not necessarily depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (10)
1. A multi-terminal authority management method is applied to a SaaS software service system, and comprises the following steps:
after entering a terminal page of the system, acquiring cached encrypted login data based on a token of a terminal entry address;
entering a login page corresponding to the terminal based on the dynamic routing data in the encrypted login data and the routing data in the session storage;
and storing the dynamic routing data into the session storage, and entering a terminal login success page.
2. The method of claim 1, wherein prior to obtaining the cached encrypted login data based on the token for the terminal entry address, further comprising:
and configuring the incidence relation between the menu items and each terminal, the opening mode of the menu items and the positioning mode of the pages corresponding to the menu items.
3. The method of claim 1, wherein the obtaining of the cached encrypted login data based on the token of the terminal entry address specifically comprises:
judging whether the token exists in the terminal entry address or not;
if so, verifying the token and acquiring the cached encrypted login data;
and if not, jumping to a preset unified login page from the terminal page for login.
4. The method according to claim 3, wherein verifying the token and obtaining the cached encrypted login data specifically comprises:
when the token is verified, obtaining the cached encrypted login data;
and when the token is not checked, jumping to a preset unified login page by the terminal page.
5. The method according to claim 1, wherein the entry into the login page corresponding to the terminal is based on the dynamic routing data in the encrypted login data and the routing data in the session storage, and specifically includes:
judging whether dynamic routing data in the encrypted login data exist or not;
if so, directly entering a terminal login success page through terminal page skipping;
and if not, entering a login page corresponding to the terminal based on the routing data in the session storage.
6. The method according to claim 5, wherein entering a login page corresponding to the terminal based on the routing data in the session storage specifically comprises:
if the routing data in the session storage exists, creating the dynamic routing data according to a diff algorithm, storing the dynamic routing data in the session storage, and entering a terminal login success page;
and if the routing data in the session storage does not exist, jumping to a preset unified login page by the terminal page for login.
7. The method according to claim 6, characterized in that the dynamic routing data is created according to a diff algorithm, in particular:
screening menu information which can be accessed by a current user from a local menu according to code encoding through a diff algorithm;
matching the authority data of the user through the accessible menu information;
and generating corresponding dynamic routing data for each authority data, so that the current user can only access the configured address data, and other addresses are uniformly redirected to a page 404.
8. The method according to claim 7, characterized in that the rights data of the user are matched by the accessible menu information, in particular:
flattening the authority tree transmitted by the background;
putting each node in the background tree into a temp object;
and traversing the front-end routing tree through depth priority, and then filtering out the routing node corresponding to the authority data of the user by judging whether the current node exists in the temp object.
9. The method of claim 1, wherein the method further comprises:
and after entering the terminal login success page, acquiring the authority data of the current page through a preset instruction.
10. A multi-terminal rights management device, the device comprising:
the acquisition module is used for acquiring the cached encrypted login data based on the token of the terminal entry address after entering the terminal page of the system;
the first login module is used for entering a login page corresponding to the terminal based on dynamic routing data in the encrypted login data and routing data in session storage;
and the second login module is used for storing the dynamic routing data into the session storage and entering a terminal login success page.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111057388.5A CN113922986B (en) | 2021-09-09 | 2021-09-09 | Multi-terminal authority management method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111057388.5A CN113922986B (en) | 2021-09-09 | 2021-09-09 | Multi-terminal authority management method and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113922986A true CN113922986A (en) | 2022-01-11 |
| CN113922986B CN113922986B (en) | 2024-02-09 |
Family
ID=79234303
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111057388.5A Active CN113922986B (en) | 2021-09-09 | 2021-09-09 | Multi-terminal authority management method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113922986B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103051631A (en) * | 2012-12-21 | 2013-04-17 | 国云科技股份有限公司 | Unified security authentication method for PaaS (Platform as a Service) platform and SaaS (Software as a Service) application system |
| CN105430102A (en) * | 2015-12-28 | 2016-03-23 | 东软集团股份有限公司 | Integration method and system of SaaS (Software as a Service) website and third-party system and device thereof |
| WO2021017128A1 (en) * | 2019-07-29 | 2021-02-04 | 深圳壹账通智能科技有限公司 | Login token generation method and apparatus, login token verification method and apparatus, and server |
| CN112507320A (en) * | 2020-12-10 | 2021-03-16 | 东莞市盟大塑化科技有限公司 | Access control method, device, system, electronic equipment and storage medium |
-
2021
- 2021-09-09 CN CN202111057388.5A patent/CN113922986B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103051631A (en) * | 2012-12-21 | 2013-04-17 | 国云科技股份有限公司 | Unified security authentication method for PaaS (Platform as a Service) platform and SaaS (Software as a Service) application system |
| CN105430102A (en) * | 2015-12-28 | 2016-03-23 | 东软集团股份有限公司 | Integration method and system of SaaS (Software as a Service) website and third-party system and device thereof |
| WO2021017128A1 (en) * | 2019-07-29 | 2021-02-04 | 深圳壹账通智能科技有限公司 | Login token generation method and apparatus, login token verification method and apparatus, and server |
| CN112507320A (en) * | 2020-12-10 | 2021-03-16 | 东莞市盟大塑化科技有限公司 | Access control method, device, system, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113922986B (en) | 2024-02-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20190207812A1 (en) | Hybrid cloud network configuration management | |
| CN110730153B (en) | Account configuration method, device and system of cloud equipment and data processing method | |
| US10216943B2 (en) | Dynamic security questions in electronic account management | |
| CN110049048B (en) | Data access method, equipment and readable medium for government affair public service | |
| CN111314340A (en) | Authentication method and authentication platform | |
| CN113542201B (en) | Access control method and equipment for Internet service | |
| CN109891415B (en) | Securing a Web server for an unauthorized client application | |
| CN112910904B (en) | Login method and device of multi-service system | |
| CN110493239B (en) | Authentication method and device | |
| CN106101054A (en) | The single-point logging method of a kind of multisystem and centralized management system | |
| CN112187491A (en) | Server management method, device and equipment | |
| CN109286620B (en) | User right management method, system, device and computer readable storage medium | |
| CN106254319A (en) | A kind of light application log-in control method and device | |
| CN105162774A (en) | Virtual machine login method and device used for terminal | |
| CN111191200A (en) | Page display method and device and electronic equipment | |
| CN112073366A (en) | Data processing method for railway financial system and data center | |
| CN110972093B (en) | Mobile office implementation method and system | |
| CN113922986A (en) | Multi-terminal authority management method and equipment | |
| CN112751800A (en) | Authentication method and device | |
| CN112287327B (en) | Method, device, medium and equipment for easily reconstructing single sign-on system | |
| CN115329297A (en) | Application mutual trust method, device, equipment and storage medium based on block chain | |
| CN115221447A (en) | Page menu authority control method, device, equipment and storage medium | |
| CN114726556A (en) | WAF management method, device, system, electronic equipment and readable medium | |
| CN114553608A (en) | Method and device for accessing cloud platform | |
| CN111835692B (en) | Information management and distribution 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 |