WO2020155761A1 - 登录多个服务集群的方法、装置、计算机设备及存储介质 - Google Patents

登录多个服务集群的方法、装置、计算机设备及存储介质 Download PDF

Info

Publication number
WO2020155761A1
WO2020155761A1 PCT/CN2019/117705 CN2019117705W WO2020155761A1 WO 2020155761 A1 WO2020155761 A1 WO 2020155761A1 CN 2019117705 W CN2019117705 W CN 2019117705W WO 2020155761 A1 WO2020155761 A1 WO 2020155761A1
Authority
WO
WIPO (PCT)
Prior art keywords
account
terminal
service cluster
information
authorization token
Prior art date
Application number
PCT/CN2019/117705
Other languages
English (en)
French (fr)
Inventor
王建华
马琳
张晓东
Original Assignee
平安科技(深圳)有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 平安科技(深圳)有限公司 filed Critical 平安科技(深圳)有限公司
Publication of WO2020155761A1 publication Critical patent/WO2020155761A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40Support for services or applications

Definitions

  • This application belongs to the field of cloud technology and relates to methods, devices, computer equipment, and storage media for logging in to multiple service clusters.
  • multiple service clusters are used to realize the operation of multiple software products/services. Independently developing and deploying multiple software products/services in a distributed manner through multiple service clusters constitutes an open architecture, with more open ports, and the process of user login and access becomes more complicated.
  • the embodiments of the present application disclose methods, devices, computer equipment and storage media for logging in to multiple service clusters, aiming to log in to multiple service clusters conveniently and safely.
  • Some embodiments of the present application disclose a method for logging in to multiple service clusters.
  • the method for logging in to multiple service clusters includes: creating an associated account set in the relational database of the account login server, and the associated account set contains account information of at least one account registered by the same user; when the first service cluster is received When the login request of the terminal is redirected, it is determined whether the terminal has logged in to any service cluster; when the terminal has logged in to any service cluster, the first authorization token is created; and the terminal is redirected to the First service cluster, and transfer the first authorization token to the first service cluster; verify the second authorization token provided by the first service cluster; when the second authorization token passes the verification At the time, it is confirmed that the terminal has successfully logged in to the first service cluster.
  • An embodiment of the present application discloses a device for logging in to multiple service clusters.
  • the device for logging in to multiple service clusters includes: an associated account set creation module, configured to create an associated account set in a relational database of the login server, the associated account set contains account information of at least one account registered by the same user;
  • the login judgment module is used to determine whether the terminal logs in any service cluster when the login request of the terminal redirected from the first service cluster is received;
  • the token creation module is used to when the terminal has logged in to the any service cluster;
  • a first authorization token is created in a service cluster; a first redirection module is used to redirect the terminal to the first service cluster and transmit the first authorization token to the first service cluster
  • Token verification module used to verify the second authorization token provided by the first service cluster;
  • Token verification result feedback module used to confirm when the second authorization token passes the verification The terminal successfully logs in in the first service cluster.
  • Some embodiments of the present application disclose a computer device, including a memory and a processor.
  • the memory stores computer-readable instructions.
  • the processor executes the computer-readable instructions, any one of the above-mentioned logins is implemented. Steps of the method of serving the cluster.
  • Some embodiments of the present application disclose a computer non-volatile readable storage medium.
  • the computer non-volatile readable storage medium stores computer readable instructions.
  • the computer readable instructions are executed by a processor, The steps of any of the above methods for logging in to multiple service clusters are implemented.
  • the method for logging in to multiple service clusters is redirected to the account login server regardless of which service cluster the terminal requests to log in.
  • the account login server determines whether the terminal logs in to any service cluster. This allows the account login server to centrally manage and authorize logins to multiple service clusters. Therefore, fewer ports are opened through the method of logging in to multiple service clusters, and the possibility of network attacks is lower. Since any one of the service clusters does not independently verify the account provided by the terminal, but is centrally processed by the account login server, thus ensuring the response speed of any one of the service clusters, so that any one of the service clusters Not easy to backlog services.
  • the account login server redirects the terminal to the service cluster that requests login. Therefore, on the premise of ensuring security, unnecessary log-in information verification links are reduced, which facilitates the process of making the terminal request to log in to multiple service clusters more convenient.
  • FIG. 1 is a schematic diagram of a method for logging in to multiple service clusters in an embodiment of the application
  • Figure 2 is a schematic diagram of creating a set of associated accounts in the relational database in an embodiment of the application.
  • FIG. 3 is a schematic diagram of grouping 6 accounts into 3 linked account sets in an embodiment of the application
  • FIG. 4 is a schematic diagram of verifying the second authorization token provided by the service cluster in an embodiment of the application
  • FIG. 5 is a schematic diagram of a method for logging in to multiple service clusters in another embodiment of the application.
  • FIG. 6 is a schematic diagram of verifying the first account information in the login form in combination with a relational database in an embodiment of the application;
  • FIG. 7 is a schematic diagram of interaction among terminal a, service cluster A, service cluster B, and account login server se in an embodiment of the application;
  • FIG. 8 is a schematic diagram of an apparatus for logging in to multiple service clusters in an embodiment of the application.
  • FIG. 9 is a schematic diagram of the associated account set creation module 10 in an embodiment of this application.
  • FIG. 10 is a schematic diagram of the token verification module 50 in an embodiment of this application.
  • FIG. 11 is a schematic diagram of an apparatus for logging in to multiple service clusters in another embodiment of the application.
  • FIG. 12 is a schematic diagram of the account information verification module 90 in another embodiment of the application.
  • FIG. 13 is a schematic diagram of an apparatus for logging in to multiple service clusters according to another embodiment of the application.
  • FIG. 14 is a block diagram of the basic structure of the computer device 200 in an embodiment of the application.
  • An embodiment of the present application discloses a method for logging in to multiple service clusters.
  • One such service cluster usually runs a single software product.
  • the terminal first accesses the service cluster, and when the service cluster receives the access of the terminal, it redirects the terminal to the account login server.
  • the service cluster redirects the terminal to the account login server and sends its own address parameters to the account login server.
  • FIG. 1 is a schematic diagram of a method for logging in to multiple service clusters in an embodiment of the application.
  • the terminal requests to log in to multiple service clusters through the account login server, and the steps performed by the account login server include:
  • S1 Create an associated account set in the relational database of the account login server, where the associated account set contains account information of at least one account registered by the same user.
  • FIG. 2 it is a schematic diagram of creating a collection of associated accounts in the relational database in an embodiment of this application.
  • the step of creating a set of associated accounts in the relational database includes:
  • S11 Obtain characteristic information from the account information of each account from at least one dimension.
  • S12 Group accounts that contain the same feature information in the same dimension into the same set of associated accounts.
  • the dimensions include: user ID dimensions, fingerprint information dimensions, face information dimensions, voiceprint information dimensions, and iris information dimensions.
  • the user ID dimension mainly includes the user's ID card number, unique ID generated during registration, mobile phone number, and so on.
  • the fingerprint information dimension is usually the fingerprint information used as the login password when the user logs in through the account.
  • the face information dimension is usually the face information used as the login password when the user logs in through the account.
  • the voiceprint information dimension is usually the voiceprint information used as the login password when the user logs in through the account.
  • the iris information dimension is usually the iris information used as the login password when the user logs in through the account.
  • the multiple dimensions are sorted. Specifically, count the number of accounts involved in each dimension in all accounts. When the number of accounts involved in a dimension increases, the characteristic information is first obtained from the account information of all accounts according to the dimension, and accounts containing the same characteristic information in this dimension are included in the same associated account set.
  • FIG. 3 a schematic diagram of grouping 6 accounts into 3 linked account sets in an embodiment of this application.
  • the account information of the six accounts in Fig. 3 is only for schematic illustration.
  • account NO1 and account NO4 contain the same feature information swmm58974 in the voiceprint information dimension (used as a code for voiceprint information, and the same code indicates that the voiceprint information is owned by the same person).
  • the account NO1 and the account NO4 can be classified into the associated account set j1.
  • the account NO2 and the account NO3 contain the same feature information 154236 in the user ID dimension, so the account NO2 and the account NO3 can be classified into the associated account set j2.
  • Account NO3 and account NO5 contain the same characteristic information zwmm00265811 in the fingerprint information dimension (using the fingerprint information code, the same code indicates the fingerprint information owned by the same person), so the account NO5 can also be included in the associated account set j2 .
  • the account NO6 and the account NO1 to the account NO5 do not contain the same feature information, so the account NO6 is separately included in the associated account set j3.
  • the service cluster When the terminal successfully requests to log in to any one of the service clusters to the account login server, the service cluster generates a global session.
  • the global session records data generated by the terminal accessing the account login server. By analyzing the global session, it can be determined whether the terminal logs in to any service cluster.
  • S3 Create a first authorization token when the terminal has logged in to any of the service clusters.
  • S4 Redirect the terminal to the first service cluster, and transmit the authorization token to the first service cluster.
  • the account login server can pass through the account login server of the first service cluster.
  • the address parameter redirects the terminal to the first service cluster.
  • the first service cluster provides the second authorization token to the account login server, and the account login server verifies the second authorization token provided by the service cluster.
  • the account login server verifies the second authorization token provided by the service cluster.
  • FIG. 4 is a schematic diagram of verifying the second authorization token provided by the service cluster in an embodiment of this application.
  • the step of verifying the authorization token provided by the service cluster includes:
  • the terminal successfully logs in to the first service cluster.
  • the account login server generates a global session when confirming that the terminal successfully logs in to the service cluster requested to log in.
  • FIG. 5 is a schematic diagram of a method for logging in to multiple service clusters in another embodiment of the application.
  • the account login server when the terminal requests to log in to multiple service clusters through the account login server, the account login server performs the following steps in addition to S1 to S5:
  • S8 Receive a login form returned by the terminal based on the login page.
  • S7 to S9 are after the step of judging whether the terminal logs in to any service cluster.
  • FIG. 6 it is a schematic diagram of verifying the first account information in the login form in combination with the relational database in an embodiment of the application.
  • the step of verifying the first account information in the login form in combination with the relational database includes:
  • S91 Compare the first account information with the second account information of each account in the associated account set one by one.
  • a third authorization token is created when the first account information passes verification, and the third authorization token is transferred when the terminal is redirected to the first service cluster The cards are transferred to the first service cluster.
  • FIG. 7 it is a schematic diagram of interaction among terminal a, service cluster A, service cluster B, and account login server se in an embodiment of this application.
  • the terminal a is in communication connection with the service cluster A, the service cluster B, and the account login server se, and the service cluster A and the service cluster B are also connected to the Account login server se communication connection.
  • the terminal a requests to log in to the service cluster A to access certain resources of the service cluster A.
  • the service cluster A receives the login request of the terminal a, it redirects the terminal a to the account login server se, and attaches the address parameters of the service cluster A to the login of the terminal a
  • the request is sent to the account login server se.
  • the account login server se parses the login request of the terminal a, and queries whether the terminal a logs in the service cluster A or the service cluster B in the stored global session.
  • a login page is sent to the terminal a.
  • the first account information can be filled in the login page, and registration can also be performed.
  • the account login server se receives the login form returned by the terminal a based on the login page, and then verifies the first account information in the login form in combination with a relational database. Specifically, the account login server se compares the first account information of the login form with the second account information of each account in the associated account set one by one. When the account login server se compares and obtains that the first account information of the login form is consistent with the second account information of any account in the associated account set, the first account information passes the school Test. When the first account information in the login form passes the verification, the account login server se redirects the terminal a to the service cluster A.
  • the account login server se When the account login server se finds that the terminal a has logged in to any of the service clusters, the account login server se will generate a first authorization order for the terminal a's request to log in to the service cluster A this time Then, attach the first authorization token to the login request of the terminal a. When the account login server se redirects the terminal a to the service cluster A, the first authorization token will be provided to the service cluster A.
  • the service cluster A sends the second authorization token to the account login server se for verification.
  • the second authorization token is the same as the first authorization token obtained by the service cluster A.
  • the second authorization token cannot pass the verification of the account login server se.
  • the terminal a When the second authorization token passes the verification of the account login server se, the terminal a successfully logs in to the service cluster A. After the terminal a logs in to the service cluster A, the service cluster A generates and stores a local session, and records the login data of the terminal a. When the second authorization token does not pass the verification of the account login server se, the service cluster A feeds back the login failure to the terminal a. Specifically, the second authorization token often has a certain time limit, and the second authorization token will become invalid after a set time limit. Therefore, if the terminal a fails to succeed within the set time limit, the service cluster A will cause the second authorization token to expire, so that the second authorization token cannot log in to the server se through the account. check.
  • the terminal a when the terminal a is hijacked, it will log in to the service cluster A with a forged second authorization token. At this time, the second authorization token provided by the terminal a is checked by the account login server se. This is beneficial to prevent illegal acquisition of data resources of the service cluster A.
  • the service cluster B redirects the terminal a to the account login server se.
  • the account login server se queries whether the terminal a logs in the service cluster A or the service cluster B in a stored global session according to the account information in the login request.
  • the account login server se can query in the global session to obtain a record of the terminal a logging in to the service cluster A.
  • the process for the terminal a to log in to the service cluster B can refer to the request of the terminal a to log in to the service cluster A when it has logged in to any service cluster. the process of.
  • the method for logging in to multiple service clusters is redirected to the account login server regardless of which service cluster the terminal requests to log in.
  • the account login server determines whether the terminal logs in to any service cluster. This allows the account login server to centrally manage and authorize logins to multiple service clusters. Therefore, fewer ports are opened through the method of logging in to multiple service clusters, and the possibility of network attacks is lower.
  • the account login server determines that the terminal is not logged in to any of the service clusters
  • the account login server sends a login page to the terminal, and receives a login form returned by the terminal based on the login page,
  • the first account information in the login form is verified to ensure that the login request of the terminal is a safe request. Since any one of the service clusters no longer independently verifies the account provided by the terminal, but is processed by the account login server, which ensures the response speed of any one of the service clusters, so that any one of the services Clusters are not easy to backlog services.
  • the account login server redirects the terminal to the service cluster that requests login. Therefore, on the premise of ensuring security, unnecessary log-in information verification links are reduced, which facilitates the process of making the terminal request to log in to multiple service clusters more convenient.
  • An embodiment of the present application discloses a device for logging in to multiple service clusters.
  • FIG. 8 is a schematic diagram of an apparatus for logging in to multiple service clusters in an embodiment of this application.
  • the device for logging in to multiple service clusters includes:
  • the associated account set creation module 10 is configured to create an associated account set in the relational database of the login server, and the associated account set contains account information of at least one account registered by the same user.
  • the login judgment module 20 is configured to, when a login request of a terminal redirected from the first service cluster is received, determine whether the terminal logs in to any service cluster.
  • the token creation module 30 is configured to create a first authorization token when the terminal has logged in to any service cluster.
  • the first redirection module 40 is configured to redirect the terminal to the first service cluster and transmit the first authorization token to the first service cluster.
  • the token verification module 50 is used to verify the second authorization token provided by the first service cluster.
  • the token verification result feedback module 60 is configured to confirm that the terminal has successfully logged in to the first service cluster when the second authorization token passes the verification.
  • the associated account set creation module 10 includes: a feature information acquisition sub-module 11 for acquiring feature information from at least one dimension in the account information of each account .
  • the account categorization sub-module 12 categorizes the accounts that contain the same feature information in the same dimension into the same associated account set.
  • the token verification module 50 includes: a token comparison sub-module 51 for comparing the second authorization token with the first The authorization token is compared.
  • the token comparison result judgment sub-module 52 is used for judging that the second authorization token passes the verification when the second authorization token is consistent with the first authorization token.
  • the apparatus for logging in to multiple service clusters further includes: a page sending module 70, which is configured to: when the terminal is not logged in to any service cluster, Send a login page to the terminal.
  • the form receiving module 80 is configured to receive the login form returned by the terminal based on the login page.
  • the account information verification module 90 is configured to verify the first account information in the login form in combination with the relational database.
  • the second redirection module 100 is configured to redirect the terminal to the first service cluster when the account information in the login form passes verification.
  • FIG. 12 is a schematic diagram of the account information verification module 90 in an embodiment of this application.
  • the account information verification module 90 includes: an account information comparison submodule 91, configured to combine the first account information with the associated account set The second account information of each account in the system is compared one by one.
  • the account information verification result judgment sub-module 92 is configured to determine that the first account information passes the verification when the first account information is consistent with the second account information of any account in the associated account set. Test.
  • the token creation module 30 is further configured to create a third authorization token when the first account information passes verification.
  • the device for logging in to multiple service clusters transmits the third authorization token to the first service cluster through the second redirection module 100 when redirecting the terminal to the first service cluster.
  • the apparatus for logging in to multiple service clusters further includes a global session creation module 110.
  • the global session creation module 110 is configured to create a global session when the first account information in the login form passes the verification and when the first account information in the login form fails the verification.
  • FIG. 14 is a block diagram of the basic structure of the computer device 200 in an embodiment of the application.
  • the computer device 200 includes a memory 201, a processor 202, and a network interface 203 that are connected to each other in communication through a system bus. It should be pointed out that FIG. 14 only shows the computer device 200 with components 201-203, but it should be understood that it is not required to implement all the illustrated components, and more or fewer components may be implemented instead.
  • the computer device here is a device that can automatically perform numerical calculation and/or information processing in accordance with pre-set or stored instructions. Its hardware includes but is not limited to microprocessors and application specific integrated circuits. (Application Specific Integrated Circuit, ASIC), Programmable Gate Array (Field-Programmable Gate Array, FPGA), Digital Processor (Digital Signal Processor, DSP), embedded devices, etc.
  • the computer device may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a cloud server.
  • the computer device can interact with the user through a keyboard, a mouse, a remote control, a touch panel, or a voice control device.
  • the memory 201 includes at least one type of non-volatile readable storage medium, and the non-volatile readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), Random access memory (RAM), static random access memory (SRAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), programmable read only memory
  • non-volatile readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), Random access memory (RAM), static random access memory (SRAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), programmable read only memory
  • the memory 201 may be an internal storage unit of the computer device 200, such as a hard disk or memory of the computer device 200. In other embodiments, the memory 201 may also be an external storage device of the computer device 200, such as a plug-in hard disk, a smart media card (SMC), and a secure digital device equipped on the computer device 200. (Secure Digital, SD) card, flash card (Flash Card), etc. Of course, the memory 201 may also include both the internal storage unit of the computer device 200 and the external storage device thereof.
  • the memory 201 is generally used to store the operating system and various application software installed in the computer device 200, such as the computer-readable instructions of the above method for logging in to multiple service clusters.
  • the memory 201 can also be used to temporarily store various types of data that have been output or will be output.
  • the processor 202 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips.
  • the processor 202 is generally used to control the overall operation of the computer device 200.
  • the processor 202 is configured to execute computer-readable instructions or process data stored in the memory 201, for example, to execute the computer-readable instructions of the aforementioned method of logging in to multiple service clusters.
  • the network interface 203 may include a wireless network interface or a wired network interface, and the network interface 203 is generally used to establish a communication connection between the computer device 200 and other electronic devices.
  • This application also provides another implementation manner, that is, a computer non-volatile readable storage medium storing computer readable instructions for logging in to multiple service clusters.
  • the computer-readable instructions for logging into multiple service clusters may be executed by at least one processor, so that the at least one processor executes any of the steps of the method for logging into multiple service clusters.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请属于云技术领域,涉及登录多个服务集群的方法、装置、计算机设备及存储介质。该方法包括:在账户登录服务器的关系型数据库中创建关联账户集合,所述关联账户集合中包含同一用户注册的至少一个账户的账户信息;当接收到第一服务集群重定向过来的终端的登录请求时,判断所述终端是否登录任一服务集群;当所述终端已登录所述任一服务集群时创建第一授权令牌;将所述终端重定向到所述第一服务集群,并将所述第一授权令牌传送给所述第一服务集群;校验所述第一服务集群提供的第二授权令牌;当所述第二授权令牌通过校验时,确认所述终端在所述第一服务集群成功登录。该方法能够便捷且安全地登录多个服务集群。

Description

登录多个服务集群的方法、装置、计算机设备及存储介质
本申请以2019年1月28日提交的申请号为201910080752.6,名称为“登录多个服务集群的方法、装置、计算机设备及存储介质”的中国发明专利申请为基础,并要求其优先权。
技术领域
本申请属于云技术领域,涉及登录多个服务集群的方法、装置、计算机设备及存储介质。
背景技术
伴随着软件产品业务的扩展,衍生出的软件产品/服务也会相应的增加,一般通过多个服务集群来实现多个软件产品/服务的运行。通过多个服务集群以分散方式独立开发和部署多个软件产品/服务构成的是一个开放架构,开放的端口较多,用户登录和访问的过程变得更为复杂。
在实现本申请的过程中,发明人意识到现有的实现方式至少存入如下问题:现有的技术条件下,对于用户通过终端登录不同的服务集群往往是分别授权和管理的,在安全性和故障率上都存在一定的不足。例如,由于开放的端口更多,遭受网络攻击的可能性会更大。此外,如果存在网络问题或服务自身的问题容易引发服务调用故障或者延迟,严重时会因为服务积压过多导致服务雪崩。
发明内容
本申请实施例公开了登录多个服务集群的方法、装置、计算机设备及存储介质,旨便捷且安全地登录多个服务集群。
本申请的一些实施例公开了一种登录多个服务集群的方法。
所述登录多个服务集群的方法包括:在账户登录服务器的关系型数据库中创建关联账户集合,所述关联账户集合中包含同一用户注册的至少一个账户的账户信息;当接收到第一服务集群重定向过来的终端的登录请求时,判断所述终端是否登录任一服务集群;当所述终端已登录所述任一服务集群时创建第一授权令牌;将所述终端重定向到所述第一服务集群,并将所述第一授权令牌传送给所述第一服务集群;校验所述第一服务集群提供的第二授权令牌;当所述 第二授权令牌通过校验时,确认所述终端在所述第一服务集群成功登录。
本申请的一实施例公开了一种登录多个服务集群的装置。
所述登录多个服务集群的装置包括:关联账户集合创建模块,用于在登录服务器的关系型数据库中创建关联账户集合,所述关联账户集合中包含同一用户注册的至少一个账户的账户信息;登录判断模块,用于当接收到第一服务集群重定向过来的终端的登录请求时,判断所述终端是否登录任一服务集群;令牌创建模块,用于当所述终端已登录所述任一服务集群时创建第一授权令牌;第一重定向模块,用于将所述终端重定向到所述第一服务集群,并将所述第一授权令牌传送给所述第一服务集群;令牌校验模块,用于校验所述第一服务集群提供的第二授权令牌;令牌校验结果反馈模块,用于当所述第二授权令牌通过校验时,确认所述终端在所述第一服务集群成功登录。
本申请的一些实施例公开了一种计算机设备,包括存储器和处理器,所述存储器中存储有计算机可读指令,所述处理器执行所述计算机可读指令时实现上述任一种登录多个服务集群的方法的步骤。
本申请的一些实施例公开了一种计算机非易失性可读存储介质,所述计算机非易失性可读存储介质上存储有计算机可读指令,所述计算机可读指令被处理器执行时实现上述任一种登录多个服务集群的方法的步骤。
与现有技术相比,本申请公开的技术方案主要有以下有益效果:
在本申请的实施例中,所述登录多个服务集群的方法不管所述终端请求登录哪一个服务集群,均重定向至所述账户登录服务器。由所述账户登录服务器判断所述终端是否登录任一服务集群。使得所述账户登录服务器对登录多个服务集群进行集中管理,并集中授权。因此通过所述登录多个服务集群的方法开放的端口更少,遭受网络攻击的可能性更低。由于任一所述服务集群不在单独对所述终端提供的账户进行验证,而是由所述账户登录服务器集中处理,因此确保了任一所述服务集群的响应速度,使得任一所述服务集群不易积压服务。当所述终端已登录所述任一服务集群时,所述账户登录服务器将所述终端重定向到请求登录的服务集群。因此在确保安全的前提下减少了不必要的登录信息校验环节,有利于让所述终端请求登录多个服务集群的过程更为便捷。
附图说明
为了更清楚地说明本申请实施例的技术方案,下面将对实施例中所需要使 用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本申请的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动性的前提下,还可以根据这些附图获得其它的附图。
图1为本申请的一实施例中所述登录多个服务集群的方法的示意图;
图2为本申请的一实施例中在所述关系型数据库中创建关联账户集合的示意图。
图3为本申请的一实施例中将6个账户归入3个关联账户集合的示意图;
图4为本申请的一实施例中校验所述服务集群提供的第二授权令牌的示意图;
图5为本申请的另一实施例中所述登录多个服务集群的方法的示意图;
图6为本申请的一实施例中所述结合关系型数据库对所述登录表单中的第一账户信息进行校验的示意图;
图7为本申请的一实施例中终端a、服务集群A、服务集群B以及账户登录服务器se之间的交互示意图;
图8为本申请的一实施例中所述登录多个服务集群的装置的示意图;
图9为本申请的一实施例中所述关联账户集合创建模块10的示意图;
图10为本申请的一实施例中所述令牌校验模块50的示意图;
图11为本申请的另一实施例中所述登录多个服务集群的装置的示意图;
图12为本申请的又一实施例中所述账户信息校验模块90的示意图;
图13为本申请的又一实施例中所述登录多个服务集群的装置的示意图;
图14为本申请的一实施例中计算机设备200基本结构框图。
附图标记说明:
Figure PCTCN2019117705-appb-000001
Figure PCTCN2019117705-appb-000002
具体实施方式
为了便于理解本申请,下面将参照相关附图对本申请进行更全面的描述。附图中给出了本申请的较佳实施例。但是,本申请可以以许多不同的形式来实现,并不限于本文所描述的实施例。相反地,提供这些实施例的目的是使对本申请的公开内容的理解更加透彻全面。
除非另有定义,本文所使用的所有的技术和科学术语与属于本申请的技术领域的技术人员通常理解的含义相同。本文中在本申请的说明书中所使用的术语只是为了描述具体的实施例的目的,不是旨在于限制本申请。
本申请的一实施例公开一种登录多个服务集群的方法。
一个所述服务集群通常运行一个单独的软件产品。所述终端首先访问所述服务集群,而所述服务集群接收到所述终端的访问时,将所述终端重定向到账户登录服务器。所述服务集群将所述终端重定向到账户登录服务器会将自己的地址参数发送给所述账户登录服务器。
参考图1,为本申请的一实施例中所述登录多个服务集群的方法的示意图。
如图1中所示意的,所述终端通过所述账户登录服务器请求登录多个服务集群,所述账户登录服务器执行的步骤包括:
S1:在账户登录服务器的关系型数据库中创建关联账户集合,所述关联账户集合中包含同一用户注册的至少一个账户的账户信息。
参考图2,为本申请的一实施例中在所述关系型数据库中创建关联账户集合的示意图。
如图2中所示意的,在本申请的一些实施方式中,所述在所述关系型数据库中创建关联账户集合的步骤包括:
S11:从至少一个维度在各账户的账户信息中获取特征信息。
S12:将在同一维度包含相同所述特征信息的账户归入同一所述关联账户集合。
所述维度包括:用户ID维度、指纹信息维度、人脸信息维度、声纹信息维度以及虹膜信息维度。所述用户ID维度主要包括用户的身份证号码、注册时生成的具有唯一性的ID、手机号码等。所述指纹信息维度通常为用户通过账号录 入时作为登录密码的指纹信息。所述人脸信息维度通常为用户通过账号录入时作为登录密码的人脸信息。所述声纹信息维度通常为用户通过账号录入时作为登录密码的声纹信息。所述虹膜信息维度通常为用户通过账号录入时作为登录密码的虹膜信息。
当可以从多个维度在所有账户的账户信息中获取特征信息时,对所述多个维度进行排序。具体而言,在所有的账户中统计每一个维度涉及的账户的数量。当一个维度涉及的账户的数量越多时,优先根据该维度在所有账户的账户信息中获取特征信息,将在该维度包含相同特征信息的账户归入同一关联账户集合。
下面将举例对S11和S12进行说明:
参考图3,为本申请的一实施例中将6个账户归入3个关联账户集合的示意图。图3中的6个账户的账户信息只是作为示意性的说明。
如图3中所示意的,账户NO1与账户NO4在所述声纹信息维度包含了相同特征信息swmm58974(用作声纹信息的代号,相同的代号表明是同一个人所有的声纹信息),因此所述账户NO1与所述账户NO4可以归入关联账户集合j1。账户NO2与账户NO3在所述用户ID维度包含了相同特征信息154236,因此所述账户NO2与所述账户NO3可以归入关联账户集合j2。账户NO3与账户NO5在所述指纹信息维度包含了相同特征信息zwmm00265811(用指纹信息的代号,相同的代号表明是同一个人所有的指纹信息),因此所述账户NO5也可以归入关联账户集合j2。账户NO6与账户NO1至账户NO5均不包含相同特征信息,因此所述账户NO6单独归入关联账户集合j3。
S2:当接收到第一服务集群重定向过来的终端的登录请求时,判断所述终端是否登录任一服务集群。
当所述终端向所述账户登录服务器成功请求登录任一所述服务集群时,所述服务集群会生成全局会话。所述全局会话记录有所述终端访问所述账户登录服务器产生的数据。通过对所述全局会话进行解析,便能够判断得出所述终端是否登录任一服务集群。
S3:当所述终端已登录所述任一服务集群时创建第一授权令牌。
S4:将所述终端重定向到所述第一服务集群,并将所述授权令牌传送给所述第一服务集群。
由于所述第一服务集群将所述终端重定向到所述账户登录服务器会将自己的地址参数发送给所述账户登录服务器,因此所述账户登录服务器可以通过所 述第一服务集群的所述地址参数,将所述终端重定向到所述第一服务集群。
S5:校验所述第一服务集群提供的第二授权令牌。
所述第一服务集群将所述第二授权令牌提供给所述账户登录服务器,所述账户登录服务器对所述服务集群提供的所述第二授权令牌进行校验。通过校验所述服务集群提供的所述第二授权令牌,可以防止所述终端提供伪造的授权令牌实现在所述服务集群的登录,有利于提高所述服务集群的安全性能。
参考图4,为本申请的一实施例中校验所述服务集群提供的第二授权令牌的示意图。
如图4中所示意的,在本申请的一些实施方式中,所述校验所述服务集群提供的授权令牌的步骤包括:
S51:将所述第二授权令牌与所述第一授权令牌进行比对。
S52:当所述第二授权令牌与所述第一授权令牌一致时,所述第二授权令牌通过校验。
S6:当所述第二授权令牌通过校验时,确认所述终端在所述第一服务集群成功登录。
对于所述第一服务集群而言,当所述第一服务集群通过所述账户登录服务器校验得到所述第二授权令牌有效时,所述终端在所述第一服务集群登录成功。所述账户登录服务器在确认所述终端成功登录请求登录的服务集群时会生成全局会话。
参考图5,为本申请的另一实施例中所述登录多个服务集群的方法的示意图。
如图5中所示意的,所述终端通过所述账户登录服务器请求登录多个服务集群时,所述账户登录服务器除了执行S1至S5之外,还执行以下步骤:
S7:当所述终端没有登录所述任一服务集群时,向所述终端发送登录页面。
S8:接收所述终端基于所述登录页面返回的登录表单。
S9:结合所述关系型数据库对所述登录表单中的第一账户信息进行校验。
S7至S9在所述判断所述终端是否登录任一服务集群的步骤之后。
参考图6,为本申请的一实施例中所述结合关系型数据库对所述登录表单中的第一账户信息进行校验的示意图。
如图6中所示意的,所述结合所述关系型数据库对所述登录表单中的第一账户信息进行校验的步骤包括:
S91:将所述第一账户信息与所述关联账户集合中各账户的第二账户信息逐一进行比对。
S92:当所述第一账户信息与所述关联账户集合中任一账户的所述第二账户信息一致时,所述第一账户信息通过校验。
在本申请的一些实施例中,当所述第一账户信息通过校验时创建第三授权令牌,并在把所述终端重定向到所述第一服务集群时将所述第三授权令牌传送给所述第一服务集群。
S10:当所述第一账户信息通过校验时,把所述终端重定向到所述第一服务集群。
参考图7,为本申请的一实施例中终端a、服务集群A、服务集群B以及账户登录服务器se之间的交互示意图。
下面将简述终端a请求登录服务器se登录服务集群A和服务集群B的过程,以进一步说明所述登录多个服务集群的方法。
如图7中所示意的,所述终端a分别与所述服务集群A、所述服务集群B以及所述账户登录服务器se通信连接,所述服务集群A与所述服务集群B还与所述账户登录服务器se通信连接。
所述终端a请求登录所述服务集群A,以访问所述服务集群A的某些资源。所述服务集群A在收到所述终端a的登录请求时,将所述终端a重定向到所述账户登录服务器se,并将所述服务集群A的地址参数附在所述终端a的登录请求中发送给所述账户登录服务器se。
所述账户登录服务器se解析所述终端a的登录请求,在存储的全局会话中查询所述终端a是否登录所述服务集群A或者所述服务集群B。在所述终端a既没有登录所述服务集群A,又没有登录所述服务集群B时,向所述终端a发送登录页面。通过所述终端a可以在所述登录页面填入第一账户信息,也可以进行注册。
所述账户登录服务器se接收所述终端a基于所述登录页面返回的登录表单,然后结合关系型数据库对所述登录表单中的所述第一账户信息进行校验。具体而言,所述账户登录服务器se将所述登录表单的所述第一账户信息与所述关联账户集合中各账户的第二账户信息逐一进行比对。所述账户登录服务器se比对得出所述登录表单的所述第一账户信息与所述关联账户集合中的任一账户的所述第二账户信息一致时,所述第一账户信息通过校验。当所述登录表单中的所 述第一账户信息通过校验时,所述账户登录服务器se将所述终端a重定向到所述服务集群A。
当所述账户登录服务器se得出所述终端a已登录所述任一服务集群时,所述账户登录服务器se会为所述终端a的此次请求登录所述服务集群A生成第一授权令牌和全局会话,然后将所述第一授权令牌附在所述终端a的登录请求中。在所述账户登录服务器se将所述终端a重定向至所述服务集群A时,所述第一授权令牌会提供给所述服务集群A。
所述服务集群A将第二授权令牌发送所述账户登录服务器se进行校验。在所述第二授权令牌没有被伪造时,所述第二授权令牌与所述服务集群A获得的所述第一授权令牌相同。当所述第二授权令牌被伪造时,所述第二授权令牌将无法通过所述账户登录服务器se的校验。通过将所述第二授权令牌在所述账户登录服务器se进行校验,可以防止所述终端a被劫持并以伪造的所述第二授权令牌登录所述服务集群A,非法获取所述服务集群A的数据资源。
当所述第二授权令牌通过所述账户登录服务器se的校验时,所述终端a在所述服务集群A登录成功。所述终端a在所述服务集群A登录成后所述服务集群A生成并存储本地会话,记录所述终端a的登录数据。当所述第二授权令牌没有通过所述账户登录服务器se的校验时,所述服务集群A向所述终端a反馈登录失败。具体而言,所述第二授权令牌往往具有一定的时限性,超过设定的期限所述第二授权令牌将会失效。因此如果在设定的期限内所述终端a没能够成功所述服务集群A将会造成所述第二授权令牌过期,使得所述第二授权令牌不能够通过所述账户登录服务器se的校验。此外,所述终端a被劫持时会以伪造的第二授权令牌登录所述服务集群A,此时通过所述账户登录服务器se对所述终端a提供的所述第二授权令牌进行校验,有利于防止非法获取所述服务集群A的数据资源。
当所述终端a请求登录所述服务集群B时,所述服务集群B将所述终端a重定向至所述账户登录服务器se。所述账户登录服务器se根据所述登录请求中的账户信息在存储的全局会话中查询所述终端a是否登录所述服务集群A或者所述服务集群B。
由于所述终端a已经成功登录所述服务集群A,因此所述账户登录服务器se能够在所述全局会话中查询获得所述终端a登录所述服务集群A的记录。此时由于所述终端a已经登录所述服务集群A,因此所述终端a登录所述服务集群 B的过程,可以参考所述终端a在已经登录任一服务集群时请求登录所述服务集群A的过程。
在本申请的实施例中,所述登录多个服务集群的方法不管所述终端请求登录哪一个服务集群,均重定向至所述账户登录服务器。由所述账户登录服务器判断所述终端是否登录任一服务集群。使得所述账户登录服务器对登录多个服务集群进行集中管理,并集中授权。因此通过所述登录多个服务集群的方法开放的端口更少,遭受网络攻击的可能性更低。当所述账户登录服务器判断得出所述终端没有登录所述任一服务集群时,由所述账户登录服务器向所述终端发送登录页面,接收所述终端基于所述登录页面返回的登录表单,并结合关系型数据库对所述登录表单中的第一账户信息进行校验,确保所述终端的登录请求是安全的请求。由于任一所述服务集群不再单独对所述终端提供的账户进行验证,而是由所述账户登录服务器集中处理,因此确保了任一所述服务集群的响应速度,使得任一所述服务集群不易积压服务。当所述终端已登录所述任一服务集群时,所述账户登录服务器将所述终端重定向到请求登录的服务集群。因此在确保安全的前提下减少了不必要的登录信息校验环节,有利于让所述终端请求登录多个服务集群的过程更为便捷。
本申请的一实施例公开了一种登录多个服务集群的装置。
参考图8,为本申请的一实施例中所述登录多个服务集群的装置的示意图。
如图8中所示意的,所述登录多个服务集群的装置包括:
关联账户集合创建模块10,用于在登录服务器的关系型数据库中创建关联账户集合,所述关联账户集合中包含同一用户注册的至少一个账户的账户信息。
登录判断模块20,用于当接收到第一服务集群重定向过来的终端的登录请求时,判断所述终端是否登录任一服务集群。
令牌创建模块30,用于当所述终端已登录所述任一服务集群时创建第一授权令牌。
第一重定向模块40,用于将所述终端重定向到所述第一服务集群,并将所述第一授权令牌传送给所述第一服务集群。
令牌校验模块50,用于校验所述第一服务集群提供的第二授权令牌。
令牌校验结果反馈模块60,用于当所述第二授权令牌通过校验时,确认所述终端在所述第一服务集群成功登录。
参考图9,为本申请的一实施例中所述关联账户集合创建模块10的示意图。 如图9中所示意的,在本申请的一些实施例中,所述关联账户集合创建模块10包括:特征信息获取子模块11,用于从至少一个维度在各账户的账户信息中获取特征信息。账户归入子模块12,将在同一维度包含相同所述特征信息的账户归入同一所述关联账户集合。
参考图10,为本申请的一实施例中所述令牌校验模块50的示意图。如图10中所示意的,在本申请的一些实施例中,所述令牌校验模块50包括:令牌比对子模块51,用于将所述第二授权令牌与所述第一授权令牌进行比对。令牌比对结果判断子模块52,用于当所述第二授权令牌与所述第一授权令牌一致时,判断得出所述第二授权令牌通过校验。
参考图11,为本申请的另一实施例中所述登录多个服务集群的装置的示意图。如图11中所示意的,在本申请的一些实施例中,所述登录多个服务集群的装置还包括:页面发送模块70,用于当所述终端没有登录所述任一服务集群时,向所述终端发送登录页面。表单接收模块80,用于接收所述终端基于所述登录页面返回的登录表单。账户信息校验模块90,用于结合所述关系型数据库对所述登录表单中的第一账户信息进行校验。第二重定向模块100,用于当所述登录表单中的账户信息通过校验时,把所述终端重定向到所述第一服务集群。
参考图12,为本申请的一实施例中所述账户信息校验模块90的示意图。
如图12中所示意的,在本申请的一些实施例中,所述账户信息校验模块90包括:账户信息比对子模块91,用于将所述第一账户信息与所述关联账户集合中各账户的第二账户信息逐一进行比对。账户信息校验结果判断子模块92,用于当所述第一账户信息与所述关联账户集合中任一账户的所述第二账户信息一致时,判断得出所述第一账户信息通过校验。
在本申请的一些实施例中,所述令牌创建模块30还用于当所述第一账户信息通过校验时创建第三授权令牌。所述登录多个服务集群的装置通过所述第二重定向模块100在把所述终端重定向到所述第一服务集群时将所述第三授权令牌传送给所述第一服务集群。
参考图13,为本申请的又一实施例中所述登录多个服务集群的装置的示意图。如图13中所示意的,在本申请的一些实施例中,所述登录多个服务集群的装置还包括全局会话创建模块110。所述全局会话创建模块110用于当所述登录表单中的所述第一账户信息通过校验时和当所述登录表单中的所述第一账户信息没有通过校验时创建全局会话。
本申请的一实施例公开了一种计算机设备。具体请参考图14,为本申请的一实施例中计算机设备200基本结构框图。
如图14中所示意的,所述计算机设备200包括通过***总线相互通信连接存储器201、处理器202、网络接口203。需要指出的是,图14中仅示出了具有组件201-203的计算机设备200,但是应理解的是,并不要求实施所有示出的组件,可以替代的实施更多或者更少的组件。本技术领域技术人员应当理解,这里的计算机设备是一种能够按照事先设定或存储的指令,自动进行数值计算和/或信息处理的设备,其硬件包括但不限于微处理器、专用集成电路(Application Specific Integrated Circuit,ASIC)、可编程门阵列(Field-Programmable Gate Array,FPGA)、数字处理器(Digital Signal Processor,DSP)、嵌入式设备等。
所述计算机设备可以是桌上型计算机、笔记本、掌上电脑及云端服务器等计算设备。所述计算机设备可以与用户通过键盘、鼠标、遥控器、触摸板或声控设备等方式进行人机交互。
所述存储器201至少包括一种类型的非易失性可读存储介质,所述非易失性可读存储介质包括闪存、硬盘、多媒体卡、卡型存储器(例如,SD或DX存储器等)、随机访问存储器(RAM)、静态随机访问存储器(SRAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、可编程只读存储器
(PROM)、磁性存储器、磁盘、光盘等。在一些实施例中,所述存储器201可以是所述计算机设备200的内部存储单元,例如该计算机设备200的硬盘或内存。在另一些实施例中,所述存储器201也可以是所述计算机设备200的外部存储设备,例如该计算机设备200上配备的插接式硬盘,智能存储卡(Smart Media Card,SMC),安全数字(Secure Digital,SD)卡,闪存卡(Flash Card)等。当然,所述存储器201还可以既包括所述计算机设备200的内部存储单元也包括其外部存储设备。本实施例中,所述存储器201通常用于存储安装于所述计算机设备200的操作***和各类应用软件,例如上述登录多个服务集群的方法的计算机可读指令等。此外,所述存储器201还可以用于暂时地存储已经输出或者将要输出的各类数据。
所述处理器202在一些实施例中可以是中央处理器(Central Processing Unit,CPU)、控制器、微控制器、微处理器、或其他数据处理芯片。该处理器202通常用于控制所述计算机设备200的总体操作。本实施例中,所述处理器202用于运行所述存储器201中存储的计算机可读指令或者处理数据,例如运行上述 登录多个服务集群的方法的计算机可读指令。
所述网络接口203可包括无线网络接口或有线网络接口,该网络接口203通常用于在所述计算机设备200与其他电子设备之间建立通信连接。
本申请还提供了另一种实施方式,即提供一种计算机非易失性可读存储介质,所述计算机非易失性可读存储介质存储有登录多个服务集群的计算机可读指令,所述登录多个服务集群计算机可读指令可被至少一个处理器执行,以使所述至少一个处理器执行上述任意一种登录多个服务集群的方法的步骤。
最后应说明的是,显然以上所描述的实施例仅仅是本申请一部分实施例,而不是全部的实施例,附图中给出了本申请的较佳实施例,但并不限制本申请的专利范围。本申请可以以许多不同的形式来实现,相反地,提供这些实施例的目的是使对本申请的公开内容的理解更加透彻全面。尽管参照前述实施例对本申请进行了详细的说明,对于本领域的技术人员来而言,其依然可以对前述各具体实施方式所记载的技术方案进行修改,或者对其中部分技术特征进行等效替换。凡是利用本申请说明书及附图内容所做的等效结构,直接或间接运用在其他相关的技术领域,均同理在本申请专利保护范围之内。

Claims (20)

  1. 一种登录多个服务集群的方法,其特征在于,包括:
    在账户登录服务器的关系型数据库中创建关联账户集合,所述关联账户集合中包含同一用户注册的至少一个账户的账户信息;
    当接收到第一服务集群重定向过来的终端的登录请求时,判断所述终端是否登录任一服务集群;
    当所述终端已登录所述任一服务集群时创建第一授权令牌;
    将所述终端重定向到所述第一服务集群,并将所述第一授权令牌传送给所述第一服务集群;
    校验所述第一服务集群提供的第二授权令牌;当所述第二授权令牌通过校验时,确认所述终端在所述第一服务集群成功登录。
  2. 根据权利要求1所述登录多个服务集群的方法,其特征在于,所述在账户登录服务器的关系型数据库中创建关联账户集合的步骤包括:
    从至少一个维度在各账户的账户信息中获取特征信息;
    将在同一维度包含相同所述特征信息的账户归入同一所述关联账户集合。
  3. 根据权利要求2所述登录多个服务集群的方法,其特征在于,所述维度包括:用户ID维度、指纹信息维度、人脸信息维度、声纹信息维度以及虹膜信息维度。
  4. 根据权利要求1所述登录多个服务集群的方法,其特征在于,所述判断所述终端是否登录任一服务集群还包括:
    当所述终端没有登录所述任一服务集群时,向所述终端发送登录页面;
    接收所述终端基于所述登录页面返回的登录表单;
    结合所述关系型数据库对所述登录表单中的第一账户信息进行校验;
    当所述第一账户信息通过校验时,把所述终端重定向到所述第一服务集群。
  5. 根据权利要求4所述登录多个服务集群的方法,其特征在于,所述结合所述关系型数据库对所述登录表单中的第一账户信息进行校验的步骤包括:
    将所述第一账户信息与所述关联账户集合中各账户的第二账户信息逐一进行比对;
    当所述第一账户信息与所述关联账户集合中任一账户的所述第二账户信息一致时,所述第一账户信息通过校验。
  6. 根据权利要求4所述登录多个服务集群的方法,其特征在于,当所述第一账户信息通过校验时创建第三授权令牌,并在把所述终端重定向到所述第一服务集群时将所述第三授权令牌传送给所述第一服务集群。
  7. 根据权利要求1所述登录多个服务集群的方法,其特征在于,所述校验所述第一服务集群提供的第二授权令牌的步骤包括:
    将所述第二授权令牌与所述第一授权令牌进行比对;
    当所述第二授权令牌与所述第一授权令牌一致时,所述第二授权令牌通过校验。
  8. 一种登录多个服务集群的装置,其特征在于,包括:
    关联账户集合创建模块,用于在登录服务器的关系型数据库中创建关联账户集合,所述关联账户集合中包含同一用户注册的至少一个账户的账户信息;
    登录判断模块,用于当接收到第一服务集群重定向过来的终端的登录请求时,判断所述终端是否登录任一服务集群;
    令牌创建模块,用于当所述终端已登录所述任一服务集群时创建第一授权令牌;
    第一重定向模块,用于将所述终端重定向到所述第一服务集群,并将所述第一授权令牌传送给所述第一服务集群;
    令牌校验模块,用于校验所述第一服务集群提供的第二授权令牌;
    令牌校验结果反馈模块,用于当所述第二授权令牌通过校验时,确认所述终端在所述第一服务集群成功登录。
  9. 如去权利要求8所述的登录多个服务集群的装置,其特征在于,所述关联账户集合创建模块包括:
    特征信息获取子模块,用于从至少一个维度在各账户的账户信息中获取特征信息;
    账户归入子模块,用于将在同一维度包含相同所述特征信息的账户归入同一所述关联账户集合。
  10. 根据权利要求8所述登录多个服务集群的装置,其特征在于,所述令牌校验模块包括:
    令牌比对子模块,用于将所述第二授权令牌与所述第一授权令牌进行比对;
    令牌比对结果判断子模块,用于当所述第二授权令牌与所述第一授权令牌一致时,所述第二授权令牌通过校验。
  11. 一种计算机设备,包括存储器和处理器,其特征在于,所述存储器中存储有计算机可读指令,所述处理器执行所述计算机可读指令时实现如下登录多个服务集群的方法的步骤:
    在账户登录服务器的关系型数据库中创建关联账户集合,所述关联账户集合中包含同一用户注册的至少一个账户的账户信息;
    当接收到第一服务集群重定向过来的终端的登录请求时,判断所述终端是否登录任一服务集群;
    当所述终端已登录所述任一服务集群时创建第一授权令牌;
    将所述终端重定向到所述第一服务集群,并将所述第一授权令牌传送给所述第一服务集群;
    校验所述第一服务集群提供的第二授权令牌;当所述第二授权令牌通过校验时,确认所述终端在所述第一服务集群成功登录。
  12. 根据权利要求11所述的计算机设备,其特征在于,所述在账户登录服务器的关系型数据库中创建关联账户集合的步骤包括:
    从至少一个维度在各账户的账户信息中获取特征信息;
    将在同一维度包含相同所述特征信息的账户归入同一所述关联账户集合。
  13. 根据权利要求12所述的计算机设备,其特征在于,所述维度包括:用户ID维度、指纹信息维度、人脸信息维度、声纹信息维度以及虹膜信息维度。
  14. 根据权利要求11所述的计算机设备,其特征在于,所述处理器执行所述计算机可读指令时还实现如下步骤:
    当所述终端没有登录所述任一服务集群时,向所述终端发送登录页面;
    接收所述终端基于所述登录页面返回的登录表单;
    结合所述关系型数据库对所述登录表单中的第一账户信息进行校验;
    当所述第一账户信息通过校验时,把所述终端重定向到所述第一服务集群。
  15. 根据权利要求14所述的计算机设备,其特征在于,所述结合所述关系型数据库对所述登录表单中的第一账户信息进行校验的步骤包括:
    将所述第一账户信息与所述关联账户集合中各账户的第二账户信息逐一进行比对;
    当所述第一账户信息与所述关联账户集合中任一账户的所述第二账户信息一致时,所述第一账户信息通过校验。
  16. 一种计算机非易失性可读存储介质,其特征在于,所述计算机非易失性 可读存储介质上存储有计算机可读指令,所述计算机可读指令被处理器执行时实现如下登录多个服务集群的方法的步骤:
    在账户登录服务器的关系型数据库中创建关联账户集合,所述关联账户集合中包含同一用户注册的至少一个账户的账户信息;
    当接收到第一服务集群重定向过来的终端的登录请求时,判断所述终端是否登录任一服务集群;
    当所述终端已登录所述任一服务集群时创建第一授权令牌;
    将所述终端重定向到所述第一服务集群,并将所述第一授权令牌传送给所述第一服务集群;
    校验所述第一服务集群提供的第二授权令牌;当所述第二授权令牌通过校验时,确认所述终端在所述第一服务集群成功登录。
  17. 根据权利要求16所述的非易失性可读存储介质,其特征在于,所述在账户登录服务器的关系型数据库中创建关联账户集合的步骤包括:
    从至少一个维度在各账户的账户信息中获取特征信息;
    将在同一维度包含相同所述特征信息的账户归入同一所述关联账户集合。
  18. 根据权利要求17所述的非易失性可读存储介质,其特征在于,所述维度包括:用户ID维度、指纹信息维度、人脸信息维度、声纹信息维度以及虹膜信息维度。
  19. 根据权利要求16所述的非易失性可读存储介质,其特征在于,所述所述计算机可读指令所述处理器执行时,使得所述处理器还执行如下步骤:
    当所述终端没有登录所述任一服务集群时,向所述终端发送登录页面;
    接收所述终端基于所述登录页面返回的登录表单;
    结合所述关系型数据库对所述登录表单中的第一账户信息进行校验;
    当所述第一账户信息通过校验时,把所述终端重定向到所述第一服务集群。
  20. 根据权利要求19所述的非易失性可读存储介质,其特征在于,所述结合所述关系型数据库对所述登录表单中的第一账户信息进行校验的步骤包括:
    将所述第一账户信息与所述关联账户集合中各账户的第二账户信息逐一进行比对;
    当所述第一账户信息与所述关联账户集合中任一账户的所述第二账户信息一致时,所述第一账户信息通过校验。
PCT/CN2019/117705 2019-01-28 2019-11-12 登录多个服务集群的方法、装置、计算机设备及存储介质 WO2020155761A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910080752.6 2019-01-28
CN201910080752.6A CN109936565A (zh) 2019-01-28 2019-01-28 登录多个服务集群的方法、装置、计算机设备及存储介质

Publications (1)

Publication Number Publication Date
WO2020155761A1 true WO2020155761A1 (zh) 2020-08-06

Family

ID=66985271

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/117705 WO2020155761A1 (zh) 2019-01-28 2019-11-12 登录多个服务集群的方法、装置、计算机设备及存储介质

Country Status (2)

Country Link
CN (1) CN109936565A (zh)
WO (1) WO2020155761A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113259342A (zh) * 2021-05-11 2021-08-13 鸬鹚科技(深圳)有限公司 登录验证方法、装置、计算机设备及介质
CN113810468A (zh) * 2021-08-13 2021-12-17 济南浪潮数据技术有限公司 K8s架构下网关分发请求的方法、***、设备和存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109936565A (zh) * 2019-01-28 2019-06-25 平安科技(深圳)有限公司 登录多个服务集群的方法、装置、计算机设备及存储介质
CN111147496B (zh) * 2019-12-27 2022-04-08 北京奇艺世纪科技有限公司 数据处理方法及装置
CN112714166B (zh) * 2020-12-22 2022-03-29 新华三大数据技术有限公司 分布式存储***的多集群管理方法及装置
CN113127846B (zh) * 2021-05-17 2022-12-09 济南博观智能科技有限公司 一种软件授权方法、装置、设备及存储介质
CN113395326B (zh) * 2021-05-20 2023-03-24 网易(杭州)网络有限公司 基于网络服务的登录方法、设备和计算机可读存储介质
CN113949710B (zh) * 2021-10-15 2024-04-05 北京奇艺世纪科技有限公司 一种数据处理方法及服务器集群

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105472052A (zh) * 2014-09-03 2016-04-06 阿里巴巴集团控股有限公司 一种跨域服务器的登录方法和***
CN106375270A (zh) * 2015-07-24 2017-02-01 华为技术有限公司 令牌生成并认证的方法及认证服务器
US20180075231A1 (en) * 2016-09-14 2018-03-15 Oracle International Corporation Single sign-on functionality for a multi-tenant identity and data security management cloud service
CN109936565A (zh) * 2019-01-28 2019-06-25 平安科技(深圳)有限公司 登录多个服务集群的方法、装置、计算机设备及存储介质

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102469075A (zh) * 2010-11-09 2012-05-23 中科正阳信息安全技术有限公司 一种基于web单点登录的集成认证方法
CN102065131A (zh) * 2010-12-03 2011-05-18 湖南大学 单点登录的方式和登录认证
JP6256116B2 (ja) * 2014-03-10 2018-01-10 富士通株式会社 通信端末、セキュアログイン方法、及びプログラム
CN105024975B (zh) * 2014-04-23 2019-02-26 腾讯科技(北京)有限公司 账号登录的方法、装置及***
US10171447B2 (en) * 2015-06-15 2019-01-01 Airwatch Llc Single sign-on for unmanaged mobile devices
CN106375259B (zh) * 2015-07-20 2019-12-10 阿里巴巴集团控股有限公司 一种同用户账户识别方法及装置
CN105577667A (zh) * 2015-12-28 2016-05-11 上海赞越软件服务中心 多帐号一键登录及认证机制

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105472052A (zh) * 2014-09-03 2016-04-06 阿里巴巴集团控股有限公司 一种跨域服务器的登录方法和***
CN106375270A (zh) * 2015-07-24 2017-02-01 华为技术有限公司 令牌生成并认证的方法及认证服务器
US20180075231A1 (en) * 2016-09-14 2018-03-15 Oracle International Corporation Single sign-on functionality for a multi-tenant identity and data security management cloud service
CN109936565A (zh) * 2019-01-28 2019-06-25 平安科技(深圳)有限公司 登录多个服务集群的方法、装置、计算机设备及存储介质

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113259342A (zh) * 2021-05-11 2021-08-13 鸬鹚科技(深圳)有限公司 登录验证方法、装置、计算机设备及介质
CN113810468A (zh) * 2021-08-13 2021-12-17 济南浪潮数据技术有限公司 K8s架构下网关分发请求的方法、***、设备和存储介质

Also Published As

Publication number Publication date
CN109936565A (zh) 2019-06-25

Similar Documents

Publication Publication Date Title
WO2020155761A1 (zh) 登录多个服务集群的方法、装置、计算机设备及存储介质
US11403413B2 (en) Avoiding user session misclassification using configuration and activity fingerprints
US9491182B2 (en) Methods and systems for secure internet access and services
US20210006410A1 (en) Method for providing virtual asset service based on decentralized identifier and virtual asset service providing server using them
US7607008B2 (en) Authentication broker service
WO2020119506A1 (zh) 一种基于联盟链的身份认证方法及终端设备
JP2018116708A (ja) ネットワーク接続自動化
US7770214B2 (en) Apparatus, system, and method for establishing a reusable and reconfigurable model for fast and persistent connections in database drivers
US11356458B2 (en) Systems, methods, and computer program products for dual layer federated identity based access control
US20140365762A1 (en) Method and Apparatus for Securely Synchronizing Password Systems
CN105577835B (zh) 一种基于云计算的跨平台单点登录***
WO2020181809A1 (zh) 基于接口校验的数据处理的方法、***和计算机设备
US9178874B2 (en) Method, device and system for logging in through a browser application at a client terminal
CN110753944A (zh) 用于基于区块链的数据管理的***和方法
WO2019205389A1 (zh) 电子装置、基于区块链的身份验证方法、程序和计算机存储介质
CN112118269A (zh) 一种身份认证方法、***、计算设备及可读存储介质
TWM595792U (zh) 跨平台授權存取資源的授權存取系統
CN114039759A (zh) 一种面向信创领域的高性能网关鉴权方法与***
CN109413203A (zh) 一种交易数据获取方法及装置
US20230328063A1 (en) Method for Determining Trusted Terminal and Related Apparatus
US8027921B1 (en) Method and software for migrating protected authentication data
CN102571874A (zh) 一种分布式***中的在线审计方法及装置
US20040083296A1 (en) Apparatus and method for controlling user access
KR100639992B1 (ko) 클라이언트 모듈을 안전하게 배포하는 보안 장치 및 그방법
CN111935716B (zh) 一种认证方法、认证***及计算设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19913463

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19913463

Country of ref document: EP

Kind code of ref document: A1