CN113922986B - Multi-terminal authority management method and equipment - Google Patents
Multi-terminal authority management method and equipment Download PDFInfo
- Publication number
- CN113922986B CN113922986B CN202111057388.5A CN202111057388A CN113922986B CN 113922986 B CN113922986 B CN 113922986B CN 202111057388 A CN202111057388 A CN 202111057388A CN 113922986 B CN113922986 B CN 113922986B
- Authority
- CN
- China
- Prior art keywords
- data
- terminal
- login
- 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.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 14
- 238000000034 method Methods 0.000 claims abstract description 18
- 238000001914 filtration Methods 0.000 claims description 4
- 238000012216 screening Methods 0.000 claims description 4
- 230000004927 fusion Effects 0.000 abstract description 5
- 238000013475 authorization Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000009877 rendering Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 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
- 230000008707 rearrangement Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
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 successful login page of the terminal, thereby solving the problem of different standard specifications of menu components, menu items, authentication modes and authority control under the multi-terminal environment of the SaaS system, improving the menu fusion efficiency and reducing the cost.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method and apparatus for managing rights of multiple terminals.
Background
The SaaS provider builds all network infrastructure, 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. SaaS is a software layout model, and the application of the software layout model is specially designed for network delivery, so that users can conveniently host, deploy and access through the Internet.
The SaaS system generally uses a system to maintain authority data of the whole system in a set of login, menu and authority management modes, so that different templates and different systems cannot share the same data, and a user needs to independently maintain a user entrance when entering different systems, so that development efficiency is low, and the same problem is easy to take multiple times to solve.
Therefore, how to solve the technical problems that the permission data of the SaaS system are not uniform and the running cost is high in a multi-terminal process is a technical problem to be solved at present.
Disclosure of Invention
The invention provides a multi-terminal authority management method which is applied to a SaaS software server system and is used for solving the technical problems of non-uniform permission 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 successful login page of the terminal.
In some embodiments of the present application, before the token based on the terminal entry address obtains the cached encrypted login data, the method further includes:
and configuring the association relation between the menu items and the terminals, the opening mode of the menu items and the positioning mode of pages corresponding to the menu items.
In some embodiments of the present application, the token based on the terminal entry address obtains cached encrypted login data, specifically:
judging whether the token exists at the terminal entry address or not;
if yes, checking the token and acquiring the cached encrypted login data;
if not, the terminal page jumps to a preset unified login page to log in.
In some embodiments of the present application, the token is checked, and the cached encrypted login data is obtained, which specifically includes:
when the token is checked to pass, obtaining the cached encrypted login data;
when the token check fails, the terminal page jumps to a preset unified login page
In some embodiments of the present application, the entry page corresponding to the terminal is entered based on the dynamic routing data in the encrypted login data and the routing data in the session storage, specifically:
judging whether dynamic routing data in the encrypted login data exists or not;
if yes, the user directly jumps to enter a successful login page of the terminal through the page of the terminal;
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 is specifically:
if the route data in the session storage exists, creating the dynamic route data according to diff algorithm, storing the dynamic route data in the session storage, and entering a successful page of terminal login;
and if the routing data in the session storage does not exist, the terminal page jumps to a preset unified login page to log in.
In some embodiments of the present application, the dynamic routing data is created according to diff algorithm, specifically:
screening menu information which can be accessed by a current user from a local menu according to code codes through diff algorithm;
matching authority data of the user through the accessible menu information;
each authority data is generated into corresponding dynamic routing data, so that the current user can only access the configured address data, and the other addresses are uniformly redirected to 404 pages.
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;
placing each node in the background tree into a temp object;
traversing the front-end routing tree by 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 successful login page of the terminal, acquiring the authority data of the current page through a preset instruction.
Correspondingly, the invention also provides multi-terminal authority management equipment, which comprises:
the acquisition module is used for acquiring cached encrypted login data based on a token of a terminal entry address after entering a terminal page of the system;
the first login module is used for 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 the second login module is used for storing the dynamic routing data into the session storage and entering a successful login page of the terminal.
By applying the technical scheme, after entering a terminal page of the system, the encrypted login data of the cache is obtained 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 successful login page of the terminal, thereby solving the problem of different standard specifications of menu components, menu items, authentication modes and authority control under the multi-terminal environment of the SaaS system, improving the menu fusion efficiency and reducing the cost.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 shows a flow diagram of a multi-terminal rights management method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a multi-terminal rights management device according to an embodiment of the present invention;
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The embodiment of the application provides a multi-terminal authority management method, which is applied to a SaaS software serviceization system, as shown in fig. 1, and comprises the following steps:
step S101, after entering a terminal page of the system, obtaining cached encrypted login data based on a token of a terminal entry address.
In this embodiment, as described in the background art, the SaaS system generally uses a system to log in, menu, and authority management to maintain authority data of the whole system, 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, which results in low development efficiency and easy and similar problems to take multiple times to solve. Therefore, in the present solution, a multi-terminal rights management method is provided to solve the above-mentioned problems.
When entering a terminal page, the obtaining terminal obtains cached encrypted login data based on token at an entry address, so that user information leakage is prevented, current user history login information can be prevented from being broken, a unified authentication mode of each terminal and a corresponding entry address are defined by special personnel configuration 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 firstly obtained.
In order to obtain encrypted login data, in some embodiments of the present application, before obtaining cached encrypted login data based on a token of a terminal entry address, the method further includes:
and configuring the association relation between the menu items and the terminals, the opening mode of the menu items and the positioning mode of pages corresponding to the menu items.
Specifically, the developer maintains and configures the fusion menu and menu items, including the association relation between the menu items and each system, the opening mode (jump or new creation) of the menu items, and the positioning mode (route or relative address or absolute address) of the pages corresponding to the menu items, where the specific configuration mode is not limited, and the corresponding relation is preset, so that the subsequent authentication and the determination of the authority data of the user are facilitated.
In order to obtain encrypted login data, in some embodiments of the present application, the token based on the terminal entry address obtains cached encrypted login data, which specifically includes:
judging whether the token exists at the terminal entry address or not;
if yes, checking the token and acquiring the cached encrypted login data;
if not, the terminal page jumps to a preset unified login page to log in.
When entering a terminal page, acquiring the cached encrypted login data of the terminal at an entry address based on token, judging whether the token exists at the entry address of the terminal or not because the token does not exist possibly, if the token does not exist, turning the page to a unified login page, logging in the unified login page after the failure of the verification, uniformly entering the login address and attaching a current jump link to the condition that the login address is not logged in or the login information is invalid, generally, developing a set of login authentication mode for each terminal, and if the terminals are very many, adopting a unified authentication mode, namely not needing to develop authentication for each terminal, enabling a user to enter different terminals by using the same login address in a uniformly configured mode, checking the token, and acquiring the cached encrypted login data.
In order to obtain encrypted login data, in some embodiments of the present application, the token is checked, and the cached encrypted login data is obtained, which specifically includes:
when the token is checked to pass, obtaining the cached encrypted login data;
and when the token check fails, the terminal page jumps to a preset unified login page.
Specifically, whether the token is successfully checked is also required to be checked, if the check fails, the page is transferred to a unified login page to log in, and if the check succeeds, encrypted login data of the user is obtained.
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 process 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 a login page corresponding to the terminal, in some embodiments of the present application, the entry page corresponding to the terminal is entered based on the dynamic routing data in the encrypted login data and the routing data in the session storage, specifically:
judging whether dynamic routing data in the encrypted login data exists or not;
if yes, the user directly jumps to enter a successful login page of the terminal through the page of the terminal;
if not, entering a login page corresponding to the terminal based on the routing data in the session storage. In this embodiment, first, whether dynamic routing data in the encrypted login data exists is determined, if yes, terminal page skip is performed, the dynamic routing data is stored in the session storage, a successful login page of the terminal is entered, corresponding permission is displayed to a user, and if not, the user needs to enter a login page corresponding to the terminal further based on the routing data in the session storage.
In order to enter a login page corresponding to the terminal, in some embodiments of the present application, the entering the login page corresponding to the terminal based on the routing data in the session storage is specifically:
if the route data in the session storage exists, creating the dynamic route data according to diff algorithm, storing the dynamic route data in the session storage, and entering a successful page of terminal login;
and if the routing data in the session storage does not exist, the terminal page jumps to a preset unified login page to log in.
Specifically, if the routing data in the session storage exists, the dynamic routing data is created according to diff algorithm, and the dynamic routing data is stored in the session storage and enters a successful page of terminal login.
The cost of rendering the real DOM is large, sometimes we modify some data, and rendering directly onto the real DOM causes redrawing and rearrangement of the whole DOM tree. We want to update only the small block dom that we modified, instead of the whole dom, diff algorithm helps us achieve this. The essence of the diff algorithm is: the difference between the two objects is found out in order to make the node multiplexing as possible. The object referred to herein is simply virtual dom tree in vue, i.e., js object is used to represent the dom structure in a page.
If the route data in the session storage does not exist either, the terminal page jumps to a preset unified login page for login, the unified login page is equivalent to a guest page or logs in after verification failure, a login address is unified for the condition that login information fails or login addresses are attached to current jump links, and generally, a set of login authentication mode needs to be developed for each terminal under the condition that the terminals are very many, and for the condition that the terminals do not need to develop authentication, a user can enter different terminals by using the same login address through a unified configuration mode, if the login address exists, the token is verified, and the cached encrypted login data is acquired.
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 codes through diff algorithm;
matching authority data of the user through the accessible menu information;
each authority data is generated into corresponding dynamic routing data, so that the current user can only access the configured address data, and the other addresses are uniformly redirected to 404 pages.
Specifically, screening menu information which can be accessed by a current user from a local menu according to code codes through diff algorithm; matching 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, uniformly redirecting other addresses to a 404 page, and displaying an interface and an authority button corresponding to the authority data to the user after entering a login success page.
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;
placing each node in the background tree into a temp object;
traversing the front-end routing tree by 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 the authority tree transmitted from the background; placing each node in the background tree into a temp object; traversing the front-end routing tree by 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 performing terminal page skip, 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 successful login page of the terminal, acquiring the authority data of the current page through a preset instruction.
Specifically, after entering a successful login page of the terminal, acquiring the permission data of the current page through a preset instruction, and displaying an interface or permission buttons and the like corresponding to the permission data to a user.
By applying the technical scheme, after entering a terminal page of the system, the encrypted login data of the cache is obtained 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 successful login page of the terminal, thereby solving the problem of different standard specifications of menu components, menu items, authentication modes and authority control under the multi-terminal environment of the SaaS system, improving the menu fusion efficiency and reducing the cost.
In order to further explain the technical idea of the invention, the technical scheme of the invention is described with specific application scenarios.
The embodiment of the application also provides a multi-terminal authority management device, as shown in fig. 2, which comprises:
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;
the first login module 202 is 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 encrypted login data of the cache is obtained 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 successful login page of the terminal, thereby solving the problem of different standard specifications of menu components, menu items, authentication modes and authority control under the multi-terminal environment of the SaaS system, improving the menu fusion efficiency and reducing the cost.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and are not limiting thereof; although the present application has been described in detail with reference to the foregoing embodiments, one of ordinary skill in the art will appreciate that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not drive the essence of the corresponding technical solutions to depart from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims (8)
1. The multi-terminal authority management method is characterized by being applied to a software-service SaaS system, and comprises the following steps:
after entering a terminal page of the system, obtaining 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;
storing the dynamic routing data into the session storage, and entering a successful login page of a terminal;
the method comprises the steps of entering a login page corresponding to the terminal based on dynamic routing data in the encrypted login data and routing data in session storage, wherein the login page specifically comprises the following steps:
judging whether dynamic routing data in the encrypted login data exists or not;
if yes, the user directly jumps to enter a successful login page of the terminal through the page of the terminal;
if not, entering a login page corresponding to the terminal based on the routing data in the session storage;
the method comprises the steps of entering a login page corresponding to the terminal based on routing data in session storage, wherein the login page specifically comprises the following steps:
if the route data in the session storage exists, creating the dynamic route data according to diff algorithm, storing the dynamic route data in the session storage, and entering a successful page of terminal login;
and if the routing data in the session storage does not exist, the terminal page jumps to a preset unified login page to log in.
2. The method of claim 1, further comprising, prior to obtaining the cached encrypted login data based on the token of the terminal entry address:
and configuring the association relation between the menu items and the terminals, the opening mode of the menu items and the positioning mode of pages corresponding to the menu items.
3. The method of claim 1, wherein the cached encrypted login data is obtained based on a token of a terminal entry address, specifically:
judging whether the token exists at the terminal entry address or not;
if yes, checking the token and acquiring the cached encrypted login data;
if not, the terminal page jumps to a preset unified login page to log in.
4. The method of claim 3, wherein the token is verified and the cached encrypted login data is obtained, in particular:
when the token is checked to pass, obtaining the cached encrypted login data;
and when the token check fails, the terminal page jumps to a preset unified login page.
5. The method according to claim 1, wherein the dynamic routing data is created according to a diff algorithm, in particular:
screening the menu information which can be accessed by the current user from the local menu according to the code through diff algorithm;
matching authority data of the user through the accessible menu information;
each authority data is generated into corresponding dynamic routing data, so that the current user can only access the configured address data, and the other addresses are uniformly redirected to 404 pages.
6. The method according to claim 5, wherein rights data of the user are matched by the accessible menu information, in particular:
flattening the authority tree transmitted by the background;
placing each node in the background tree into a temp object, wherein the temp object is a temporary object;
traversing the front-end routing tree by 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.
7. The method of claim 1, wherein the method further comprises:
and after entering the successful login page of the terminal, acquiring the authority data of the current page through a preset instruction.
8. A multi-terminal rights management device, the device comprising:
the acquisition module is used for acquiring cached encrypted login data based on a token of a terminal entry address after entering a terminal page of the system;
the first login module is used for 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;
the second login module is used for storing the dynamic routing data into the session storage and entering a successful login page of the terminal;
the second login module is specifically configured to:
judging whether dynamic routing data in the encrypted login data exists or not;
if yes, the user directly jumps to enter a successful login page of the terminal through the page of the terminal;
if not, entering a login page corresponding to the terminal based on the routing data in the session storage;
wherein, the second login module is further configured to:
if the route data in the session storage exists, creating the dynamic route data according to diff algorithm, storing the dynamic route data in the session storage, and entering a successful page of terminal login;
and if the routing data in the session storage does not exist, the terminal page jumps to a preset unified login page to log in.
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 CN113922986A (en) | 2022-01-11 |
| CN113922986B true 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 |
|---|---|
| CN113922986A (en) | 2022-01-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106612290B (en) | Cross-domain single sign-on method oriented to system integration | |
| US10320776B2 (en) | Protection of application passwords using a secure proxy | |
| EP3511821A1 (en) | Method and system for managing access to artifacts in a cloud computing environment | |
| KR102080156B1 (en) | Auto Recharge System, Method and Server | |
| CN108289098A (en) | Right management method and device, server, the medium of distributed file system | |
| CN112528262A (en) | Application program access method, device, medium and electronic equipment based on token | |
| JP6967074B2 (en) | Protecting your web server from malicious client applications | |
| CN112838951B (en) | Operation and maintenance method, device and system of terminal equipment and storage medium | |
| US20220253297A1 (en) | Automated deployment of changes to applications on a cloud computing platform | |
| US20200233699A1 (en) | Platform-based change management | |
| US20180324174A1 (en) | Saml sso ux improvements | |
| CN110221949A (en) | Automate operation management method, apparatus, equipment and readable storage medium storing program for executing | |
| CN102945337A (en) | On-line self-help management method and system of Subversion user password | |
| CN106254319A (en) | A kind of light application log-in control method and device | |
| CN111200593A (en) | Application login method and device and electronic equipment | |
| CN110324209A (en) | Micro services system monitoring method, apparatus, electronic equipment and computer-readable medium | |
| US11170080B2 (en) | Enforcing primary and secondary authorization controls using change control record identifier and information | |
| CN111191200A (en) | Page display method and device and electronic equipment | |
| EP3772686A1 (en) | Automatic restore for a failed virtual computing session | |
| CN113922986B (en) | Multi-terminal authority management method and equipment | |
| CN112491940B (en) | Request forwarding method and device of proxy server, storage medium and electronic equipment | |
| US20150121517A1 (en) | Bundle-to-bundle authentication in modular systems | |
| CN114553608A (en) | Method and device for accessing cloud platform | |
| CN116097259A (en) | Computer file metadata segmentation security system | |
| CN112464225A (en) | Request processing method, request processing device and computer readable storage medium |
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 |