CN114024681A - System login method, device, equipment and computer readable storage medium - Google Patents
System login method, device, equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN114024681A CN114024681A CN202111032413.4A CN202111032413A CN114024681A CN 114024681 A CN114024681 A CN 114024681A CN 202111032413 A CN202111032413 A CN 202111032413A CN 114024681 A CN114024681 A CN 114024681A
- Authority
- CN
- China
- Prior art keywords
- name
- subsystem
- module
- selected module
- token
- 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.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 36
- 238000004590 computer program Methods 0.000 claims description 10
- 238000010586 diagram Methods 0.000 description 6
- 238000012795 verification Methods 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
-
- 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
Abstract
The application discloses a system login method, a device, equipment and a computer readable storage medium, wherein the method is applied to a front end and comprises the following steps: logging in a corresponding system according to the received login request, and receiving a module selection command and a token which is sent by a rear end and corresponds to the login request after successful login; acquiring the name of a selected module corresponding to the module selection command, and acquiring an access path of a subsystem corresponding to the selected module according to the name of the selected module and a preconfigured route; according to the access path of the subsystem, the name of the selected module and the token are carried to access the subsystem; and assigning the name of the selected module to the window. According to the technical scheme disclosed by the application, the front end realizes the jump and log-in avoidance among different systems by means of the pre-configured route and the token, so that the complexity and cost of system login are reduced.
Description
Technical Field
The present application relates to the field of technologies, and in particular, to a system login method, apparatus, device, and computer-readable storage medium.
Background
Single sign-on refers to a user having to log on once to access all mutually trusted applications among multiple applications.
At present, the existing single sign-on needs to integrate a CAS (Central Authentication Service) Service to perform jumping and login-free between application systems, but since the CAS Service needs to deploy many environments such as a CAS Service end and a CAS client, the CAS Service is excessively heavy to operate, has many dependence factors, and has a high cost.
In summary, how to reduce the complexity and cost of system login is a technical problem that needs to be solved by those skilled in the art.
Disclosure of Invention
In view of the above, an object of the present application is to provide a system login method, apparatus, device and computer readable storage medium, which are used to reduce the complexity and cost of system login.
In order to achieve the above purpose, the present application provides the following technical solutions:
a system login method is applied to a front end and comprises the following steps:
logging in a corresponding system according to the received login request, and receiving a module selection command and a token which is sent by a rear end and corresponds to the login request after successful login;
acquiring the name of a selected module corresponding to the module selection command, and acquiring an access path of a subsystem corresponding to the selected module according to the name of the selected module and a preconfigured route;
according to the access path of the subsystem, carrying the name of the selected module and the token to access the subsystem;
assigning the name of the selected module to a window.name, determining a page corresponding to the selected module according to the route and the window.name, and displaying the page.
Preferably, before accessing the subsystem according to the access path of the subsystem, carrying the name of the selected module and the token, further includes:
and judging whether the token is normal, if so, executing the step of carrying the name of the selected module and the token to access the subsystem according to the access path of the subsystem.
Preferably, after accessing the subsystem according to the access path of the subsystem, carrying the name of the selected module and the token, further includes:
and storing the name of the selected module.
Preferably, storing the name of the selected module includes:
and storing the name of the selected module by using Vuex.
Preferably, after the login is successful and before the module selection command is received, the method further includes:
and receiving the view information which corresponds to the login request and represents the authority of the user corresponding to the login request and is returned by the back end, and displaying the view information.
Preferably, after determining the page corresponding to the selected module according to the route and the window.
Judging whether a user corresponding to the login request has the authority to view the page or not;
and if so, executing the step of displaying the page.
A system login device is applied to a front end and comprises:
the receiving module is used for logging in a corresponding system according to the received login request, and receiving a module selection command and a token which is sent by the rear end and corresponds to the login request after the login is successful;
the acquisition module is used for acquiring the name of the selected module corresponding to the module selection command and acquiring the access path of the subsystem corresponding to the selected module according to the name of the selected module and a pre-configured route;
the access module is used for carrying the name of the selected module and the token to access the subsystem according to the access path of the subsystem;
and the display module is used for assigning the name of the selected module to the window.name, determining a page corresponding to the selected module according to the route and the window.name, and displaying the page.
Preferably, the method further comprises the following steps:
and the first judgment module is used for judging whether the token is normal or not before the subsystem is accessed by carrying the name of the selected module and the token according to the access path of the subsystem, and if so, executing the step of accessing the subsystem by carrying the name of the selected module and the token according to the access path of the subsystem.
A system login device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the system login method as claimed in any one of the above when executing said computer program.
A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the system login method according to any one of the preceding claims.
The application provides a system login method, a device, equipment and a computer readable storage medium, wherein the method is applied to a front end and comprises the following steps: logging in a corresponding system according to the received login request, and receiving a module selection command and a token which is sent by a rear end and corresponds to the login request after successful login; acquiring the name of a selected module corresponding to the module selection command, and acquiring an access path of a subsystem corresponding to the selected module according to the name of the selected module and a preconfigured route; according to the access path of the subsystem, the name of the selected module and the token are carried to access the subsystem; and assigning the name of the selected module to the window.
According to the technical scheme disclosed by the application, after logging in a corresponding system according to a received login request, a receiving module selects a command and a token returned by a rear end, acquires the name of a selected module according to the module selection command, determines an access path of a corresponding subsystem based on the name of the selected module and a preset route, carries the name of the selected module and the token access subsystem according to the access path of the subsystem so as to realize login-free of the subsystem through the carried token, assigns the name of the selected module to a window name so as to realize cross-module operation through the window name, determines a page corresponding to the selected module according to the route and the window name and displays the page so as to realize skip and login-free of different systems through a front end, and can realize skip and login-free of different systems without integrating a CAS (CAS) service, the complexity and cost of system login can be reduced, the number of middleware can be reduced, the generation probability of network storms can be reduced, and the occupation of network resources can be reduced.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a system login method according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a system login device according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a system login device according to an embodiment of the present application.
Detailed Description
The core of the application is to provide a system login method, a device, equipment and a computer readable storage medium, which are used for reducing the complexity and cost of system login.
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.
Referring to fig. 1, which shows a flowchart of a system login method provided in an embodiment of the present application, applied to a front end, may include:
s11: and logging in a corresponding system according to the received login request, and receiving a module selection command and a token which is sent by the rear end and corresponds to the login request after successful logging in.
When the user needs to log in the system and view the page, a login request for logging in the system can be sent. The front end can send the login request to the back end after receiving the login request sent by the user, the back end verifies the identity of the user according to the login request, if the verification is passed, a message that the verification is passed can be returned to the front end, at the moment, the front end can successfully log in a system corresponding to the login request, and the back end can return a token (token) corresponding to the login request to the front end after the login is successful, so that the front end can carry the token to realize login-free operation of mutually trusted subsystems in the system.
After successfully logging in the corresponding system, the front end may display modules included in the mutually trusted subsystems in the system on the display screen (specifically, information such as names and diagrams of the modules may be displayed), where each subsystem may include a plurality of modules, and each module may have a plurality of pages, that is, a one-to-many relationship may be formed between the modules and the pages.
After the modules of each subsystem are displayed, a user can send a module selection command by means of mouse clicking or touch screen clicking and the like, and the front end receives the sent module selection command received by the user.
S12: and acquiring the name of the selected module corresponding to the module selection command, and acquiring the access path of the subsystem corresponding to the selected module according to the name of the selected module and the preconfigured route.
The front end can acquire the name of the selected module corresponding to the module selection command after receiving the module selection command, wherein when acquiring the name of the selected module, the front end can specifically acquire the name of the selected module by using a standardSystemType field, that is, the standardSystemType field can represent the acquired name of the selected module, and then the front end can carry the name of the selected module by carrying the field.
After the front end obtains the name of the selected module, the access path of the subsystem corresponding to the selected module can be determined according to the name of the selected module and the preconfigured route. The pre-configured route includes information such as a name of the module, a subsystem corresponding to the module, an access path of the subsystem corresponding to the module, a page corresponding to the module, and a name of the page, and the route can be pre-configured by the front end, and the back end can maintain and comply with the front end together, so that the back end can know the route configuration.
S13: and according to the access path of the subsystem, carrying the name of the selected module and the token to access the subsystem.
After the access path of the subsystem corresponding to the selected module is obtained, the front end can carry the name and the token of the selected module, the front end reaches the subsystem according to the access path of the subsystem, and login-free access to the subsystem is achieved by the aid of the carried token.
S14: and assigning the name of the selected module to the window.
After the front end reaches the subsystem, the name of the selected module can be designated by using the window name (the name of the current window, namely the window name), that is, the name of the selected module is assigned to the window name, so that the cross-system and cross-module login is really realized by using the window name, that is, the login in the corresponding subsystem is really avoided. Name is a global attribute, and as long as in the window, no matter url (Uniform Resource Locator, also called a web address), as long as the window name is set, the window name will not be changed all the time.
After assigning the name of the selected module to the window.name, the front end may determine the page corresponding to the selected module according to the preconfigured route and the current assignment of the window.name, that is, may determine the page corresponding to the selected module from the preconfigured route, and may display the page, so that the user may view and browse the page, and the like.
According to the process, the login-free and jump of the system can be realized only by the aid of the front end without integrating CAS (CAS) services, so that the complexity of the login-free and jump of the system can be reduced, the running flexibility is improved, and the login-free and jump cost of the system is reduced. In addition, because the application does not need to integrate CAS (CAS) services, the use of message middleware can be avoided, so that the occupation of network resources can be reduced, and the generation probability of network storms can be reduced.
According to the technical scheme disclosed by the application, after logging in a corresponding system according to a received login request, a receiving module selects a command and a token returned by a rear end, acquires the name of a selected module according to the module selection command, determines an access path of a corresponding subsystem based on the name of the selected module and a preset route, carries the name of the selected module and the token access subsystem according to the access path of the subsystem so as to realize login-free of the subsystem through the carried token, assigns the name of the selected module to a window name so as to realize cross-module operation through the window name, determines a page corresponding to the selected module according to the route and the window name and displays the page so as to realize skip and login-free of different systems through a front end, and can realize skip and login-free of different systems without integrating a CAS (CAS) service, the complexity and cost of system login can be reduced, the number of middleware can be reduced, the generation probability of network storms can be reduced, and the occupation of network resources can be reduced.
The system login method provided in the embodiment of the present application, before accessing the subsystem by carrying the name of the selected module and the token according to the access path of the subsystem, may further include:
and judging whether the token is normal, if so, executing the step of carrying the name of the selected module and the token to access the subsystem according to the access path of the subsystem.
In the application, before accessing the subsystem by carrying the name of the selected module and the token according to the access path of the subsystem, whether the token is normal or not can be judged, if the token is determined to be abnormal, the token is indicated to be unsafe and unusable, at this time, in order to ensure the security of system login, the execution of accessing the subsystem corresponding to the selected module can be refused, and a prompt that the token is abnormal is sent, so that related personnel can take measures in time, if the token is determined to be normal, the token is indicated to be safe and have no problem, therefore, the steps of carrying the name of the selected module and the token to access the subsystem according to the access path of the subsystem can be executed, and the login-free access to the subsystem can be realized by using the token.
The safety and reliability of subsystem access can be ensured by judging whether the token is normal or not.
The system login method provided in the embodiment of the present application, after accessing the subsystem according to the access path of the subsystem and carrying the name of the selected module and the token, may further include:
and storing the name of the selected module.
In the application, after the name of the selected module and the token are carried to access the subsystem according to the access path of the subsystem, the name of the selected module can be stored first, so that the name of the selected module is prevented from being lost due to subsequent refreshing or other reasons, and the reliability of system login and page display is improved.
The system login method provided by the embodiment of the application stores the name of the selected module, and may include:
and storing the name of the selected module by using Vuex.
In the present application, when storing the name of the selected module, the name of the selected module may be specifically stored by using Vuex, where Vuex is a state management mode developed specifically for vue.
The system login method provided by the embodiment of the application, after login is successful and before a module selection command is received, may further include:
and receiving the view information which corresponds to the login request and represents the authority of the user corresponding to the login request and is returned by the back end, and displaying the view information.
In the application, after the user successfully logs in the system corresponding to the login request and before the module selection command is received, the back end can return the view information corresponding to the login request and representing the authority of the user corresponding to the login request to the front end after the identity of the user corresponding to the login request is verified and passes the verification. The front end can display the view information after receiving the view information returned by the back end, so that a user can know the self authority according to the displayed view information, and the corresponding view information is combined to issue a module selection command, so that the effectiveness of system login and page display is improved, and the user experience degree is improved.
In addition, the back end can return the user information of the user corresponding to the login request to the front end while returning the view information to the front end, and correspondingly, the front end receives the user information of the user corresponding to the login request returned by the back end and displays the user information, so that related personnel such as the user can obtain the corresponding user information in time.
The system login method provided by the embodiment of the application, after determining the page corresponding to the selected module according to the route and the window name, may further include:
judging whether a user corresponding to the login request has a permission to view a page or not;
and if so, executing the step of displaying the page.
In the application, after determining the page corresponding to the selected module according to the route and the window name, whether the user corresponding to the login request has the authority to view the page or not can be judged, if the user does not have the authority to view the page, the page can be rejected for display so as to ensure the safety, and if the user has the authority to view the page, the step of displaying the page can be executed, namely the page can be displayed, so that the user can normally view the corresponding page, and the user experience degree is improved.
In addition, in order to ensure the security of page login and display, the front end can simultaneously judge whether the operation of the user is correct operation or not while judging whether the user corresponding to the login request has the authority to view the page, if the user has the existing authority and the operation of the user is correct, the front end displays the page, and if the user does not have the authority and the operation of the user is incorrect, the front end refuses to display the page. In the application, it can be specifically determined whether the user corresponding to the login request has the right to view the page and whether the operation of the user is a correct operation by using a hook function (e.g., beforeroute enter) in Vuex, so as to improve convenience and accuracy of determination.
An embodiment of the present application further provides a system login apparatus, which is applied to a front end, and referring to fig. 2, a schematic structural diagram of the system login apparatus provided in the embodiment of the present application is shown, and the system login apparatus may include:
the receiving module 21 is configured to log in a corresponding system according to the received login request, and receive a module selection command and a token corresponding to the login request sent by the back end after the login is successful;
the obtaining module 22 is configured to obtain a name of the selected module corresponding to the module selection command, and obtain an access path of the subsystem corresponding to the selected module according to the name of the selected module and a preconfigured route;
the access module 23 is used for accessing the subsystem by carrying the name and the token of the selected module according to the access path of the subsystem;
and the display module 24 is used for assigning the name of the selected module to the window.
The system login device provided by the embodiment of the application can further include:
the first judgment module is used for judging whether the token is normal or not before the subsystem is accessed by carrying the name and the token of the selected module according to the access path of the subsystem, and if so, executing the step of carrying the name and the token of the selected module to access the subsystem according to the access path of the subsystem.
The system login device provided by the embodiment of the application can further include:
and the storage module is used for storing the name of the selected module after the subsystem is accessed by the token and the name of the selected module carried according to the access path of the subsystem.
In an embodiment of the present application, a system login apparatus includes:
and the storage unit is used for storing the name of the selected module by using Vuex.
The system login device provided by the embodiment of the application can further include:
and the display module is used for receiving the view information which corresponds to the login request and represents the authority of the user corresponding to the login request and is returned by the back end after the login is successful and before the module selection command is received, and displaying the view information.
The system login device provided by the embodiment of the application can further include:
the second judgment module is used for judging whether the user corresponding to the login request has the authority to view the page or not after determining the page corresponding to the selected module according to the route and the window name;
and the execution module is used for executing the step of displaying the page if the user corresponding to the login request has the authority to view the page.
An embodiment of the present application further provides a system login device, refer to fig. 3, which shows a schematic structural diagram of the system login device provided in the embodiment of the present application, and the schematic structural diagram may include:
a memory 31 for storing a computer program;
the processor 32, when executing the computer program stored in the memory 31, may implement the following steps:
logging in a corresponding system according to the received login request, and receiving a module selection command and a token which is sent by a rear end and corresponds to the login request after successful login; acquiring the name of a selected module corresponding to the module selection command, and acquiring an access path of a subsystem corresponding to the selected module according to the name of the selected module and a preconfigured route; according to the access path of the subsystem, the name of the selected module and the token are carried to access the subsystem; and assigning the name of the selected module to the window.
An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the following steps may be implemented:
logging in a corresponding system according to the received login request, and receiving a module selection command and a token which is sent by a rear end and corresponds to the login request after successful login; acquiring the name of a selected module corresponding to the module selection command, and acquiring an access path of a subsystem corresponding to the selected module according to the name of the selected module and a preconfigured route; according to the access path of the subsystem, the name of the selected module and the token are carried to access the subsystem; and assigning the name of the selected module to the window.
The computer-readable storage medium may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
For a description of a relevant part in a system login device, a device, and a computer readable storage medium provided in the embodiments of the present application, reference may be made to a detailed description of a corresponding part in a system login method provided in the embodiments of the present application, and details are not described herein again.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Furthermore, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include elements inherent in the list. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element. In addition, parts of the above technical solutions provided in the embodiments of the present application, which are consistent with the implementation principles of corresponding technical solutions in the prior art, are not described in detail so as to avoid redundant description.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A system login method is applied to a front end and comprises the following steps:
logging in a corresponding system according to the received login request, and receiving a module selection command and a token which is sent by a rear end and corresponds to the login request after successful login;
acquiring the name of a selected module corresponding to the module selection command, and acquiring an access path of a subsystem corresponding to the selected module according to the name of the selected module and a preconfigured route;
according to the access path of the subsystem, carrying the name of the selected module and the token to access the subsystem;
assigning the name of the selected module to a window.name, determining a page corresponding to the selected module according to the route and the window.name, and displaying the page.
2. The system login method according to claim 1, before accessing the subsystem by carrying the name of the selected module and the token according to the access path of the subsystem, further comprising:
and judging whether the token is normal, if so, executing the step of carrying the name of the selected module and the token to access the subsystem according to the access path of the subsystem.
3. The system login method according to claim 2, wherein after accessing the subsystem by carrying the name of the selected module and the token according to the access path of the subsystem, the method further comprises:
and storing the name of the selected module.
4. The system login method according to claim 3, wherein storing the name of the selected module comprises:
and storing the name of the selected module by using Vuex.
5. The system login method of claim 1, further comprising, after login is successful and before receiving a module selection command:
and receiving the view information which corresponds to the login request and represents the authority of the user corresponding to the login request and is returned by the back end, and displaying the view information.
6. The system login method of claim 1, wherein after determining the page corresponding to the selected module according to the route and the window.
Judging whether a user corresponding to the login request has the authority to view the page or not;
and if so, executing the step of displaying the page.
7. A system login device, applied to a front end, comprises:
the receiving module is used for logging in a corresponding system according to the received login request, and receiving a module selection command and a token which is sent by the rear end and corresponds to the login request after the login is successful;
the acquisition module is used for acquiring the name of the selected module corresponding to the module selection command and acquiring the access path of the subsystem corresponding to the selected module according to the name of the selected module and a pre-configured route;
the access module is used for carrying the name of the selected module and the token to access the subsystem according to the access path of the subsystem;
and the display module is used for assigning the name of the selected module to the window.name, determining a page corresponding to the selected module according to the route and the window.name, and displaying the page.
8. The system login apparatus according to claim 7, further comprising:
and the first judgment module is used for judging whether the token is normal or not before the subsystem is accessed by carrying the name of the selected module and the token according to the access path of the subsystem, and if so, executing the step of accessing the subsystem by carrying the name of the selected module and the token according to the access path of the subsystem.
9. A system login device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the system login method according to any one of claims 1 to 6 when executing said computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the system login method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111032413.4A CN114024681A (en) | 2021-09-03 | 2021-09-03 | System login method, device, equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111032413.4A CN114024681A (en) | 2021-09-03 | 2021-09-03 | System login method, device, equipment and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114024681A true CN114024681A (en) | 2022-02-08 |
Family
ID=80054028
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111032413.4A Withdrawn CN114024681A (en) | 2021-09-03 | 2021-09-03 | System login method, device, equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114024681A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115473754A (en) * | 2022-07-27 | 2022-12-13 | 青岛海尔科技有限公司 | Multi-system access management method and device and multi-system management platform |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109150800A (en) * | 2017-06-16 | 2019-01-04 | 中兴通讯股份有限公司 | Login access method, system and storage medium |
| CN110516454A (en) * | 2019-08-13 | 2019-11-29 | 苏州浪潮智能科技有限公司 | Exchange method, system, device and the computer readable storage medium of more equipment |
| CN111181941A (en) * | 2019-12-23 | 2020-05-19 | 杭州安恒信息技术股份有限公司 | Page login method, system and related device |
-
2021
- 2021-09-03 CN CN202111032413.4A patent/CN114024681A/en not_active Withdrawn
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109150800A (en) * | 2017-06-16 | 2019-01-04 | 中兴通讯股份有限公司 | Login access method, system and storage medium |
| CN110516454A (en) * | 2019-08-13 | 2019-11-29 | 苏州浪潮智能科技有限公司 | Exchange method, system, device and the computer readable storage medium of more equipment |
| CN111181941A (en) * | 2019-12-23 | 2020-05-19 | 杭州安恒信息技术股份有限公司 | Page login method, system and related device |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115473754A (en) * | 2022-07-27 | 2022-12-13 | 青岛海尔科技有限公司 | Multi-system access management method and device and multi-system management platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9130927B2 (en) | Single certificate service system and operational method thereof | |
| CN111181941B (en) | Page login method, system and related device | |
| CN112070457A (en) | Project management method and device, electronic equipment and storage medium | |
| US9971908B2 (en) | Method and apparatus for determining permission of application program | |
| CN110781485B (en) | Single sign-on method and device | |
| CN106408096B (en) | Data processing method in online ticketing system and online ticketing system | |
| US20170019407A1 (en) | Method and server for providing image captcha | |
| CN107104923B (en) | Account binding and service processing method and device | |
| CN105897663A (en) | Method for determining access authority, device and equipment | |
| EP3468128B1 (en) | Method and device for preventing server from being attacked | |
| CN110909379A (en) | Storage cluster permission determination method, device, equipment and storage medium | |
| CN114090975A (en) | Cloud database resource processing method and device, electronic equipment and storage medium | |
| CN111259355A (en) | Single sign-on method, portal system and service platform | |
| CN112350978A (en) | Service processing method, system, device and storage medium | |
| CN114024681A (en) | System login method, device, equipment and computer readable storage medium | |
| CN113868602A (en) | Application authorization method, distributed cluster system, electronic device and storage medium | |
| CN109711193B (en) | Storage space sharing method and device | |
| CN109299053B (en) | File operation method, device and computer storage medium | |
| CN108243229B (en) | Request processing method and device | |
| CN114528542A (en) | Login management method and device, electronic equipment and storage medium | |
| CN114048457A (en) | Multi-platform user relationship creation method, device, system and storage medium | |
| CN113032188B (en) | Method, device, server and storage medium for determining main server | |
| US20160014543A1 (en) | Simultaneous multiline m2m activation | |
| CN113777935B (en) | Control method and device of intelligent equipment and computer readable storage medium | |
| CN111245772B (en) | CNAME processing method and device and electronic equipment |
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 | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20220208 |