Multi-platform jump login method, device and equipment and readable storage medium
By receiving the ciphertext of the docking platform and decrypting it using the license and JAR decryption toolkit, the problem of large amount of code transformation and insufficient security in multi-platform jump login is solved, and the secure storage and use of keys is realized, and the overall security is improved.
Patent Information
- Application Number
- CN202411938979.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-26
- Publication Date
- 2025-03-28
AI Technical Summary
In the prior art, when logging in with multiple platforms via jump, the docking platform code transformation is large and not secure enough, and the key storage in the server configuration file may lead to leakage.
By receiving the ciphertext from the docking platform, the ciphertext is decrypted using the license key and the JAR decryption toolkit to obtain user identity information, and the key is encrypted and stored in the license before decryption, ensuring that the key is not disclosed to the public.
It reduces the amount of code transformation of docking platform, improves security, ensures the secure storage and use of keys, and reduces the risk of key leakage.
Smart Images

Figure CN119728271A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of login, and in particular to a multi-platform jump login method, device, equipment and readable storage medium. Background Art
[0002] User identity information is the only identifier across multiple platforms, but the user authentication methods on different platforms are different. Some may be cookies (a string stored in the user's browser), some may be tokens (a string used to prove the user's identity), or other methods. Unifying the platforms into one authentication method to achieve multi-platform interoperability login requires a lot of research and development time because the platforms are already mature when they are connected, and the keys on the server configuration files may also be leaked.
[0003] Therefore, how to reduce the transformation of the docking platform when jumping to login on multiple platforms, simplify code work, improve efficiency and ensure security is an urgent problem that needs to be solved. Summary of the invention
[0004] In view of this, the purpose of the present invention is to provide a multi-platform jump login method, device, equipment and readable storage medium, which solves the problems of large amount of docking platform code modification and insufficient security when multi-platform jump login in the prior art.
[0005] In order to solve the above technical problems, the present invention provides a multi-platform jump login method, comprising:
[0006] Receiving a ciphertext from the docking platform, where the ciphertext is obtained by encrypting the user identity information using a JAR encryption toolkit on the docking platform;
[0007] Decrypt the ciphertext using the key of the license certificate and the JAR decryption toolkit to obtain the user identity information;
[0008] When the user identity information is verified, the login is successful.
[0009] Optionally, when the user identity information is verified, before jumping to login success, the process further includes:
[0010] Obtaining the prediction model markup language file of the docking platform by actively subscribing;
[0011] Calculate the credibility according to the device dimension value stored in the prediction model markup language file;
[0012] Verifying whether the device corresponding to the docking platform is credible according to the credibility;
[0013] Correspondingly, when the user identity information is verified, the jump to login is successful, including:
[0014] When the user identity information is verified and the device verification is credible, the jump login is successful.
[0015] Optionally, when the user identity information is verified and the device verification is credible, the jump login is successful, including:
[0016] If the user identity information is in the whitelist and the credibility is greater than the preset credibility threshold, the jump login is successful.
[0017] Optionally, the prediction model markup language file of the docking platform pre-sets the characteristic dimension indicators of the docking device as the input fields of the prediction model, and the output fields are the device dimension values; the characteristic dimension indicators include hardware information, browser information, geographic information and network protocol address.
[0018] Optionally, before decrypting the ciphertext using the key of the license certificate and the JAR decryption toolkit, the method further includes:
[0019] Encrypting the key of the JAR encryption toolkit to obtain an encryption key;
[0020] storing the encryption key in the license certificate;
[0021] Correspondingly, the decryption of the ciphertext using the key of the license certificate and the JAR decryption toolkit includes:
[0022] Decrypt the encryption key in the license to obtain the key;
[0023] The ciphertext is decrypted using the key and the JAR decryption toolkit.
[0024] Optionally, before decrypting the ciphertext using the key of the license certificate and the JAR decryption toolkit, the method further includes:
[0025] Obtain the license validity period from the license;
[0026] Determining whether the license has expired according to the validity period of the license;
[0027] If it expires, decryption fails;
[0028] If successful, the decryption is successful.
[0029] Optionally, the license certificate also includes product type, license type and application name.
[0030] The present invention also provides a multi-platform jump login device, which is applied to a main platform and includes:
[0031] A receiving module, used to receive a ciphertext from a docking platform, wherein the ciphertext is obtained by encrypting user identity information by the docking platform using a JAR encryption toolkit;
[0032] A decryption module, used to decrypt the ciphertext using the key of the license certificate and the JAR decryption toolkit to obtain the user identity information;
[0033] The verification module is used to jump to login success when the user identity information is verified.
[0034] The present invention also provides a multi-platform jump login device, comprising:
[0035] Memory for storing computer programs;
[0036] A processor is used to implement the multi-platform jump login method as described above when executing the computer program.
[0037] The present invention also provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are loaded and executed by a processor, the multi-platform jump login method as described above is implemented.
[0038] It can be seen that the present invention receives the ciphertext of the docking platform through the main platform, and the ciphertext is obtained by the docking platform using the JAR encryption toolkit to encrypt the user identity information; the ciphertext is decrypted using the key of the license certificate and the JAR decryption toolkit to obtain the user identity information; when the user identity information is verified, the jump login is successful. In the present invention, no matter which authentication method the docking platform uses, the docking platform only needs to use the JAR encryption toolkit provided by the main platform to encrypt the user identity information, which has little impact on the docking platform and a small amount of code; and the encryption key is stored in the license certificate of the main platform, so that the key is not disclosed to the outside, and the entire jump login process is encrypted transmission, which is highly secure.
[0039] In addition, the present invention also provides a multi-platform jump login device, equipment and storage medium, which also have the above-mentioned beneficial effects. BRIEF DESCRIPTION OF THE DRAWINGS
[0040] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.
[0041] Figure 1 A flowchart of a multi-platform jump login method provided by an embodiment of the present invention;
[0042] Figure 2 An example flow chart of a multi-platform jump login method provided by an embodiment of the present invention;
[0043] Figure 3 A schematic diagram of the structure of a multi-platform jump login device provided by an embodiment of the present invention;
[0044] Figure 4 A schematic diagram of the structure of a multi-platform jump login device provided in an embodiment of the present invention. DETAILED DESCRIPTION
[0045] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0046] With the rapid development and popularization of the Internet, network information security issues have become increasingly prominent. Information security refers to the collection of measures, policies and technologies that protect information systems from unauthorized access, disclosure, destruction, modification or illegal use. From the initial simple password protection to later firewalls, intrusion detection systems (IDS), security protocols (such as SSL / TLS), identity authentication technologies (such as Kerberos, OAuth), etc., information security technology has continued to evolve to adapt to the increasingly complex threat environment.
[0047] In the field of financial risk control, the main platform usually implements multi-platform jump login with other docking platforms, that is, the user identity information between multiple platforms is interoperable, so data protection and identity authentication are more important. User identity information is the only identifier across multiple platforms, but the user authentication methods between different platforms are different. Some may be cookies, some may be tokens, or other methods. When the main platform and other platforms are docking, each platform is mature. If each docking platform is to be transformed to achieve multi-platform jump login and unify it into one authentication method, it will generate a lot of customized work hours, prolong the R&D time, and placing the key in the server configuration file may also cause leakage, which has poor security.
[0048] Based on the above problems, the present invention provides a multi-platform jump login method, which can be specifically referred to Figure 1 , Figure 1 A flowchart of a multi-platform jump login method provided by an embodiment of the present invention. The method may include:
[0049] S101: receiving a ciphertext from the docking platform, where the ciphertext is obtained by encrypting the user identity information using a JAR encryption toolkit on the docking platform.
[0050] The execution subject of this embodiment is the main platform or the main system. It should be noted that the multi-platform jump login in this embodiment refers to one or more docking platforms jumping to log in to the main platform. The docking platform and the main platform in this embodiment can be platforms in the field of financial risk control, or platforms with multi-platform jump login requirements. The JAR encryption toolkit in this embodiment is provided by the main platform to the docking platform, so that the docking platform only needs to use the JAR encryption toolkit to encrypt the user identity information (plaintext) to obtain the ciphertext, and transmit the ciphertext to the main platform. The JAR tool is a lightweight Java application that includes encryption and decryption programs, and the JAR file simplifies the distribution process of the application. Developers only need to provide a JAR file, and users can easily download, install and run the entire Java application without having to deal with multiple separate class files or resources.
[0051] When the main platform receives the ciphertext, it is known that the user wants to jump from the docking platform to log in to the main platform. It is understandable that the JAR encryption toolkit contains encryption algorithms and keys. This embodiment does not limit the encryption algorithm. The national cipher can be used. The national cipher is a domestic encryption algorithm recognized by the State Cryptography Bureau, which includes a variety of specific algorithms, such as SM1, SM2, SM3, SM4, etc. This embodiment can use the SM4 algorithm. The ciphertext generation method may also require a specific shell command, so that the ciphertext generation is more secure and reliable.
[0052] Based on the docking platform, the key storage is placed in the JAR encryption toolkit, and then the JAR package is placed on the server. As a packaging method for Java applications, the JAR encryption toolkit has a certain degree of encapsulation. In addition, the key can be encrypted using an encryption algorithm before being stored in the JAR encryption toolkit. In this way, even if the JAR encryption toolkit is leaked, the attacker cannot directly obtain the unencrypted key, which can avoid the key file being directly exposed in the server's file system, thereby reducing the risk of direct access. Using the JAR encryption toolkit can simplify the deployment process of Java applications. Packaging the key and the encryption program into a JAR encryption toolkit can ensure that the key is also correctly deployed on the server when the encryption program is deployed.
[0053] S102: Decrypt the ciphertext using the key of the license certificate and the JAR decryption toolkit to obtain the user identity information.
[0054] In this embodiment, the main platform uses the license certificate and the JAR decryption toolkit to decrypt the ciphertext to obtain the user identity information. It should be noted that the ciphertext decryption requires the use of the license certificate and the JAR decryption toolkit, and the license certificate stores the key used by the JAR encryption toolkit. In other words, the key is stored in the license certificate and is not exposed to the outside, which is safer than storing it in the server configuration file. The license certificate is a file with a lic suffix, and the license certificate is placed in the startup directory of the main platform.
[0055] S103: When the user identity information is verified, the login is successful.
[0056] The user's identity information is verified. If the verification is successful, the user can jump to the main platform through the docking platform to log in without having to enter the login information on the main platform.
[0057] Furthermore, in order to improve the security of the jump login, when the user identity information is verified, before the jump login is successful, the following steps may also be included:
[0058] Step 21: Obtain the prediction model markup language file of the docking platform by actively subscribing;
[0059] Step 22: Calculate the credibility according to the device dimension value stored in the prediction model markup language file;
[0060] Step 23: Check whether the device corresponding to the docking platform is credible according to the credibility;
[0061] Correspondingly, the above step S103 may specifically include: when the user identity information is verified and the device verification is credible, the jump login is successful.
[0062] Specifically, in order to further enhance the security of jump login, this embodiment also provides a safety shield for device credibility verification. How to identify trusted devices in an environment with diverse devices and reject the problem of illegal or irregular devices logging in through other means, this embodiment pre-adopts the pmml (Predictive Model Markup Language) model to collect the device dimension values of the docking platform and store them in the predictive model markup language file (Pmml file). In this embodiment, the main platform obtains the device dimension value by actively subscribing to the predictive model markup language file of each docking platform, and calculates the credibility based on the device dimension value, and judges whether the device is trustworthy based on the credibility. Correspondingly, the jump login can only be successful after the user identity information and the device credibility are verified.
[0063] Furthermore, when the user identity information is verified and the device verification is credible, the jump login is successful, which may specifically include the following steps:
[0064] If the user identity information is in the whitelist and the credibility is greater than the preset credibility threshold, the jump login is successful.
[0065] Specifically, this embodiment verifies the user identity information based on the whitelist and verifies the credibility of the device based on the preset credibility threshold. When the user identity information is in the whitelist and the credibility is greater than the preset credibility threshold, the jump login is successful. The security of the jump login is guaranteed by double verification of the jump login device and the jump login user identity.
[0066] Furthermore, the prediction model markup language file of the above-mentioned docking platform pre-uses the characteristic dimension indicators of the docking device as the input field of the prediction model, and the output field is the device dimension value; the characteristic dimension indicators include hardware information, browser information, geographic information and network protocol address.
[0067] Specifically, the prediction model markup language file of the docking platform is obtained in advance based on the prediction model. The characteristic dimension indicators of the docking device (i.e., device fingerprint related information) are preprocessed as the input field of the prediction model, and the output field is the specific dimension value of the input field. The credibility is calculated based on the output field. Among them, the characteristic dimension indicators can include hardware information, browser information, geographic information, and network protocol address. The pmml model file is generated using the python environment and the scikit-learn (an open source machine learning library for the Python programming language) library for machine learning model training.
[0068] Furthermore, before decrypting the ciphertext using the key of the license certificate and the JAR decryption toolkit, the following steps may also be included:
[0069] Step 31: Encrypt the key of the JAR encryption toolkit to obtain an encryption key;
[0070] Step 32: Store the encryption key in the license certificate;
[0071] Correspondingly, the ciphertext is decrypted using the key of the license certificate and the JAR decryption toolkit, including: decrypting the encryption key in the license certificate to obtain the key; and decrypting the ciphertext using the key and the JAR decryption toolkit.
[0072] Specifically, considering the importance of user identity information, this embodiment encrypts the key encrypted with the user identity information before storing it in the license certificate, and stores the encrypted encryption key in the license certificate. In this way, even if the license certificate is leaked, the attacker cannot directly obtain the unencrypted key, and the key file can be prevented from being directly exposed in the file system of the server, thereby reducing the risk of being directly accessed.
[0073] Furthermore, before decrypting the ciphertext using the key of the license certificate and the JAR decryption toolkit, the following steps may also be included:
[0074] Step 41: Obtain the validity period of the license from the license;
[0075] Step 42: judging whether the license certificate has expired according to the validity period of the license certificate;
[0076] Step 43: If it is expired, decryption fails;
[0077] Step 44: If successful, the decryption is successful.
[0078] Specifically, the license also includes a validity period, which can be understood as the validity period of the key or the validity period of the license. Because when the license expires, the key is unavailable and decryption cannot be completed; when the key expires, decryption cannot be completed. After receiving the ciphertext, the main platform also needs to monitor whether the license has expired. When it expires, decryption fails. In this way, the license file can be updated and applied for regularly, which improves security and reliability.
[0079] Furthermore, the above license certificate may also include product type, license type and application name.
[0080] The multi-platform jump login method provided by the embodiment of the present invention is applied, and the main platform receives the ciphertext of the docking platform, and the ciphertext is obtained by the docking platform using the JAR encryption toolkit to encrypt the user identity information; the ciphertext is decrypted using the key of the license certificate and the JAR decryption toolkit to obtain the user identity information; when the user identity information is verified, the jump login is successful. In the present invention, no matter which authentication method the docking platform uses, the docking platform only needs to use the JAR encryption toolkit provided by the main platform to encrypt the user identity information, which has little impact on the docking platform and a small amount of code; and the encryption key is stored in the license certificate of the main platform, so that the key is not disclosed to the outside, and the entire jump login process is encrypted transmission, which is highly secure.
[0081] In order to make the present invention easier to understand, please refer to Figure 2 , Figure 2An example flow chart of a multi-platform jump login process provided by an embodiment of the present invention may specifically include:
[0082] The process on the left is the decryption process; the process on the right is the device credibility verification process. The first license-core.jar on the upper left is the JAR encryption toolkit (JAR package for short) for the docking platform, the second license-core.jar on the lower left is the JAR encryption toolkit, and the large box below is the main platform. The main platform stores the Lic certificate (i.e., license certificate, including national secret key, license validity period, license, etc.) and JAR encryption toolkit, and actively subscribes to and updates the pmml files (prediction model markup language files) of each docking platform.
[0083] The docking platform uses the shell command to use the JAR package to encrypt the plaintext user identity information, obtain the ciphertext in the form of a ciphertext string, and transmit the ciphertext (SSOEncryptStr) to the main platform. The docking platform uses the Python program (which includes the pmml model) to obtain the pmml file of the docking platform. Among them, the input of the pmml model is the device dimension indicator of the docking platform, and the output is the device dimension value.
[0084] After receiving the ciphertext, the main platform uses the lic certificate and JAR encryption toolkit to decrypt the ciphertext to obtain the username (i.e., user identity information, SystemUsername), and determines whether the username exists in the whitelist of the main platform. It also obtains the pmml file of the docking platform by actively subscribing, and calculates the device trust threshold (i.e., credibility) of the docking platform based on the device dimension value stored in the pmml file; if the trust threshold is within the preset range and the username exists in the whitelist of the main platform, the login is agreed and the jump login is successful; otherwise, the jump login fails.
[0085] The multi-platform jump login device provided in an embodiment of the present invention is introduced below. The multi-platform jump login device described below and the multi-platform jump login method described above can be referenced to each other.
[0086] Please refer to Figure 3 , Figure 3 A schematic diagram of the structure of a multi-platform jump login device provided by an embodiment of the present invention may include:
[0087] The receiving module 100 is used to receive the ciphertext from the docking platform, where the ciphertext is obtained by encrypting the user identity information by the docking platform using the JAR encryption toolkit;
[0088] The decryption module 200 is used to decrypt the ciphertext using the key of the license certificate and the JAR decryption toolkit to obtain the user identity information;
[0089] The verification module 300 is used to jump to the login success when the user identity information is verified.
[0090] Based on the above embodiment, the multi-platform jump login device may further include:
[0091] A file acquisition module, used to acquire the prediction model markup language file of the docking platform by actively subscribing;
[0092] A credibility calculation module, used to calculate credibility according to the device dimension value stored in the prediction model markup language file;
[0093] A device trust judgment module, used to verify whether the device corresponding to the docking platform is trustworthy according to the trustworthiness;
[0094] Accordingly, the verification module 300 may include:
[0095] The verification unit is used to jump to login successfully when the user identity information is verified and the device verification is credible.
[0096] Based on the above embodiment, the verification unit may include:
[0097] The verification subunit is used to jump to login successfully if the user identity information is in the whitelist and the credibility is greater than a preset credibility threshold.
[0098] Based on the above embodiment, the prediction model markup language file of the docking platform pre-sets the characteristic dimension indicators of the docking device as the input field of the prediction model, and the output field is the device dimension value; the characteristic dimension indicators include hardware information, browser information, geographic information and network protocol address.
[0099] Based on the above embodiment, the multi-platform jump login device may further include:
[0100] A key encryption module, used to encrypt the key of the JAR encryption toolkit to obtain an encryption key;
[0101] A storage module, used for storing the encryption key in the license certificate;
[0102] Accordingly, the decryption module 200 may include:
[0103] A first decryption unit, used for decrypting the encryption key in the license certificate to obtain the key;
[0104] The second decryption unit is used to decrypt the ciphertext using the key and the JAR decryption toolkit.
[0105] Based on the above embodiment, the multi-platform jump login device may further include:
[0106] A validity period acquisition module, used to obtain the validity period of the license certificate from the license certificate;
[0107] A usage judgment module, used for judging whether the license certificate has expired according to the validity period of the license certificate;
[0108] The first result module is used to decrypt if it is expired;
[0109] The second result module is used to decrypt successfully if the result is successful.
[0110] Based on the above embodiment, the license certificate further includes product type, license type and application name.
[0111] It should be noted that the order of the modules and units in the above-mentioned platform jump login device can be changed before or after without affecting the logic.
[0112] The platform jump login device provided by the embodiment of the present invention is used to receive the ciphertext of the docking platform through the receiving module 100, and the ciphertext is obtained by the docking platform using the JAR encryption toolkit to encrypt the user identity information; the decryption module 200 is used to decrypt the ciphertext using the key of the license certificate and the JAR decryption toolkit to obtain the user identity information; the verification module 300 is used to successfully jump login when the user identity information is verified. In the present invention, no matter which authentication method the docking platform uses, the docking platform only needs to use the JAR encryption toolkit provided by the main platform to encrypt the user identity information, which has little impact on the docking platform and a small amount of code; and the encryption key is stored in the license certificate of the main platform, so that the key is not disclosed to the outside, and the entire jump login process is encrypted transmission, which is highly secure.
[0113] The multi-platform jump login device provided in an embodiment of the present invention is introduced below. The multi-platform jump login device described below and the multi-platform jump login method described above can be referenced to each other.
[0114] Please refer to Figure 4 , Figure 4 A schematic diagram of the structure of a multi-platform jump login device provided by an embodiment of the present invention may include:
[0115] A memory 10, used for storing computer programs;
[0116] The processor 20 is used to execute a computer program to implement the above-mentioned multi-platform jump login method.
[0117] The memory 10 , the processor 20 , and the communication interface 31 all communicate with each other via the communication bus 32 .
[0118] In the embodiment of the present invention, the memory 10 is used to store one or more programs, and the program may include program code, and the program code includes computer operation instructions. In the embodiment of the present invention, the memory 10 may store programs for implementing the following functions:
[0119] Receive the ciphertext from the docking platform. The ciphertext is obtained by encrypting the user identity information using the JAR encryption toolkit on the docking platform.
[0120] Use the license key and JAR decryption toolkit to decrypt the ciphertext and obtain the user identity information;
[0121] When the user identity information is verified, the login is successful.
[0122] In a possible implementation, the memory 10 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application required for at least one function, etc.; the data storage area may store data created during use.
[0123] In addition, the memory 10 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A portion of the memory may also include an NVRAM. The memory stores an operating system and operating instructions, executable modules or data structures, or a subset thereof, or an extended set thereof, wherein the operating instructions may include various operating instructions for implementing various operations. The operating system may include various system programs for implementing various basic tasks and processing hardware-based tasks.
[0124] The processor 20 may be a central processing unit (CPU), an application specific integrated circuit, a digital signal processor, a field programmable gate array or other programmable logic device, a microprocessor or any conventional processor, etc. The processor 20 may call a program stored in the memory 10 .
[0125] The communication interface 31 may be an interface of a communication module, and is used to connect to other devices or systems.
[0126] Of course, it should be noted that Figure 4 The structure shown does not constitute a limitation on the multi-platform jump login device in the embodiment of the present invention. In actual applications, the multi-platform jump login device may include Figure 4 More or fewer components than shown, or combinations of certain components.
[0127] The computer-readable storage medium provided in an embodiment of the present invention is introduced below. The computer-readable storage medium described below and the multi-platform jump login method described above can be referenced to each other.
[0128] The present invention also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned multi-platform jump login method are implemented.
[0129] The computer-readable storage medium may include: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.
[0130] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.
[0131] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.
[0132] Finally, it should be noted that, in this article, relationships such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprises" or any other variations are intended to cover non-exclusive inclusion, so that a process, method, article or device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device.
[0133] The above is a detailed introduction to a multi-platform jump login method, device, equipment and computer-readable storage medium provided by the present invention. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for general technical personnel in this field, according to the idea of the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.
Claims
1. A multi-platform jump login method, characterized in that: Applied to the main platform, including: Receiving a ciphertext from the docking platform, where the ciphertext is obtained by encrypting the user identity information using a JAR encryption toolkit on the docking platform; Decrypt the ciphertext using the key of the license certificate and the JAR decryption toolkit to obtain the user identity information; When the user identity information is verified, the login is successful.
2. The platform jump login method according to claim 1, characterized in that: When the user identity information is verified, before jumping to login success, it also includes: Obtaining the prediction model markup language file of the docking platform by actively subscribing; Calculate the credibility according to the device dimension value stored in the prediction model markup language file; Verifying whether the device corresponding to the docking platform is credible according to the credibility; Correspondingly, when the user identity information is verified, the jump to login is successful, including: When the user identity information is verified and the device verification is credible, the jump login is successful.
3. The platform jump login method according to claim 2, characterized in that: When the user identity information is verified and the device verification is credible, the jump login is successful, including: If the user identity information is in the whitelist and the credibility is greater than the preset credibility threshold, the jump login is successful.
4. The platform jump login method according to claim 2, characterized in that: The prediction model markup language file of the docking platform pre-sets the characteristic dimension indicators of the docking device as the input fields of the prediction model, and the output fields are the device dimension values; the characteristic dimension indicators include hardware information, browser information, geographic information and network protocol address.
5. The platform jump login method according to claim 1, characterized in that: Before decrypting the ciphertext using the key of the license certificate and the JAR decryption toolkit, the method further includes: Encrypting the key of the JAR encryption toolkit to obtain an encryption key; storing the encryption key in the license certificate; Correspondingly, the decryption of the ciphertext using the key of the license certificate and the JAR decryption toolkit includes: Decrypt the encryption key in the license to obtain the key; The ciphertext is decrypted using the key and the JAR decryption toolkit.
6. The platform jump login method according to claim 1, characterized in that: Before decrypting the ciphertext using the key of the license certificate and the JAR decryption toolkit, the method further includes: Obtain the license validity period from the license; Determining whether the license has expired according to the validity period of the license; If it expires, decryption fails; If successful, the decryption is successful.
7. The platform jump login method according to claim 1, characterized in that: The license certificate also includes product type, license type and application name.
8. A multi-platform jump login device, characterized in that: Applied to the main platform, including: A receiving module, used to receive a ciphertext from a docking platform, wherein the ciphertext is obtained by encrypting user identity information by the docking platform using a JAR encryption toolkit; A decryption module, used to decrypt the ciphertext using the key of the license certificate and the JAR decryption toolkit to obtain the user identity information; The verification module is used to jump to login success when the user identity information is verified.
9. A multi-platform jump login device, characterized in that: include: Memory for storing computer programs; A processor, used to implement the multi-platform jump login method as described in any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are loaded and executed by the processor, the multi-platform jump login method as described in any one of claims 1 to 7 is implemented.