A cross-platform resource access method and unified login platform

Abstract

This invention provides a cross-platform resource access method and a unified login platform. The method includes: after a user creates a username on the unified login platform, they initiate a login request to the unified login platform, which returns a token; when a user initiates a login request to a third-party platform, the unified login platform sends a login request containing the username and token to the third-party platform, the third-party platform initiates a verification request to the unified login platform's backend, and the login platform's backend returns a verification result; if the token is invalid, the user is prompted with a login error message based on the information returned by the third-party platform; if the token is valid, the third-party platform checks if the username exists; if the username already exists, the third-party platform returns a token; the user logs in using the third-party platform token and is redirected to a new tab page to access resources. This solution simplifies the complex login process for cross-platform resource access, improves resource access efficiency, and ensures the security of access across platforms.

Description

Technical Field

[0001] This invention belongs to the field of software development, and in particular relates to a cross-platform resource access method and a unified login platform. Background Technology

[0002] When users need to access resources on multiple different platforms, they need to log in to each platform to access the resources. Due to the differences between the platforms, they need to frequently switch URLs and log in, and each platform requires the creation of a temporary account, which is not only complicated but also inefficient in terms of resource access. Summary of the Invention

[0003] In view of this, embodiments of the present invention provide a cross-platform resource access method and a unified login platform to solve the problems of complex and inefficient cross-platform resource access processes in the present invention.

[0004] In a first aspect of the present invention, a cross-platform resource access method is provided, comprising:

[0005] After a user creates a username on the unified login platform, they send a login request to the unified login platform, which then returns a Token.

[0006] When a user initiates a login request to a third-party platform, the unified login platform sends a login request containing the username and token to the third-party platform. The third-party platform then sends a verification request to the unified login platform backend, and the unified login platform backend returns the verification result.

[0007] If the verification result is that the token is invalid, the user will be prompted with a login error based on the information returned by the third-party platform.

[0008] If the verification result is that the Token is valid, the third-party platform will check if the username exists. If the username already exists, the third-party platform will return the Token.

[0009] Users log in using a third-party platform token and are redirected to a new tab page to access resources.

[0010] In a second aspect of the present invention, a unified login platform is provided, comprising:

[0011] The first request module is used to send a login request to the unified login platform after the user creates a username on the unified login platform and return the corresponding Token;

[0012] The second request module is used when a user initiates a login request to a third-party platform. The unified login platform will then send a login request containing the username and token to the third-party platform.

[0013] The login verification module is used to receive verification requests sent by third-party platforms and return the corresponding verification results.

[0014] The login access module is used to receive the token returned by the third-party platform when the token verification is valid and the corresponding username exists on the third-party platform. The token is used to log in and jump to a new tab page to access resources.

[0015] The error message module is used to prompt the user with a login error when the verification result is an invalid token, based on the information returned by the third-party platform.

[0016] In a third aspect of the present invention, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor executes the computer program to implement the steps of the method as described in the first aspect of the present invention.

[0017] In a fourth aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the method provided in the first aspect of the present invention.

[0018] In this embodiment of the invention, user login management based on a unified login platform enables resource access across different platforms. This not only avoids repeated switching between multiple platforms and simplifies the resource access process, but also improves resource access efficiency, achieving rapid login access. Simultaneously, it does not affect the original login functions of third-party platforms. Based on unified login management, it can improve access efficiency while ensuring platform access security. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a flowchart illustrating a cross-platform resource access method according to an embodiment of the present invention.

[0021] Figure 2 A timing diagram illustrating a cross-platform resource access method according to an embodiment of the present invention;

[0022] Figure 3 This is a schematic diagram of the structure of a unified login platform provided in one embodiment of the present invention;

[0023] Figure 4 This is a schematic diagram of the structure of an electronic device provided in one embodiment of the present invention. Detailed Implementation

[0024] To make the objectives, features, and advantages of this invention more apparent and understandable, the technical solutions of the embodiments of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the embodiments described below are only some embodiments of this invention, and not all embodiments. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.

[0025] It should be understood that the terms "comprising" and other similar expressions in the specification, claims, and accompanying drawings of this invention are intended to cover a non-exclusive inclusion, such as a process, method, system, or apparatus that includes a series of steps or units and is not limited to the listed steps or units. Furthermore, "first" and "second" are used to distinguish different objects and are not intended to describe a specific order.

[0026] Please see Figure 1 The present invention provides a flowchart illustrating a cross-platform resource access method, comprising:

[0027] S101. After a user creates a username on the unified login platform, they send a login request to the unified login platform, and the unified login platform returns a Token.

[0028] The unified login platform is used to manage user accounts and permissions for logging into third-party platforms. After registering on the unified login platform, users can generate a corresponding username and set a corresponding password. The password can be the platform's default password or a password set by the user.

[0029] The username is used to uniquely identify a user. It can be an automatically generated, non-repeating string by the platform or manually edited by the user. The token is a string generated by the server and used as a token for client requests. After the user logs in for the first time, the server generates a token and returns it to the client. In subsequent logins, the client only needs to carry the token when requesting data, without needing to use the username and password for verification.

[0030] When creating a username for a user, the unified login platform configures the user's permissions to access third-party platforms. In other words, the unified login platform will configure the user's permissions to log in and access third-party platforms, informing the user which third-party resources they can access.

[0031] It's understandable that both unified login platforms and third-party platforms use token-based login verification.

[0032] S102. When a user initiates a login request to a third-party platform, the unified login platform sends a login request containing the username and token to the third-party platform. The third-party platform then initiates a verification request to the unified login platform backend, and the unified login platform backend returns the verification result.

[0033] When a user is redirected to a third-party platform through the unified login platform, they need to send their unified login platform username, token, and third-party platform ID to access the third-party platform. Upon receiving the request, the third-party platform will return a token to the unified login platform and check if a corresponding username exists and if access permissions are granted.

[0034] The verification result includes whether the token verification is valid or invalid.

[0035] S103. If the verification result is that the token is invalid, the user will be prompted with a login error based on the information returned by the third-party platform.

[0036] When the token is invalid, the third-party platform will return an error message and notify the user through the unified login platform front-end.

[0037] S104. If the verification result is that the Token is valid, the third-party platform will determine whether the username exists. If the username already exists, the third-party platform will return the Token.

[0038] If the username requested for login already exists in the third-party platform's database and the token verification is valid, then the user is determined to be able to log in to the third-party platform. After the login is determined, the third-party platform token is returned to the unified login platform.

[0039] It is understandable that there are some differences between third-party platform tokens and unified login platform tokens.

[0040] If the username does not exist on the third-party platform, the third-party platform will create the user based on the username and assign a default password and default permissions.

[0041] S105. Users log in using a third-party platform token and are redirected to a new tab page to access resources.

[0042] After receiving a third-party platform token, the unified login platform can redirect users to web pages based on the third-party platform token.

[0043] Users access third-party platform resources by carrying a third-party platform token. They are redirected to a new tab (the third-party platform page) via the unified login platform to access page or database resources.

[0044] In one embodiment, such as Figure 2 As shown, when a user logs in and initiates a login request, the unified login platform backend generates a token and returns it. When a user initiates a login request to a third-party platform, the unified login platform frontend sends the username, token, and other information to the third-party platform. The third-party platform then requests the unified login platform backend to verify the token and sends the verification result back to the third-party platform.

[0045] When the token is invalid, the third-party platform returns an error message, which is then displayed to the user via the unified login platform's front end. When the token is valid, the third-party platform checks if the requested username exists in its database. If it does, it returns the third-party platform's token, allowing the user to be redirected to a new page. Otherwise, the third-party platform needs to create a user account and assign a default password and permissions. Based on the redirected page, the user accesses resources by carrying the third-party platform token.

[0046] In this embodiment, a unified login platform allows for quick access to resources on different third-party platforms, avoiding repeated switching between multiple platforms, simplifying resource access operations, and improving resource access efficiency. Simultaneously, it does not affect the original login functionality of the third-party platforms and ensures the security of access to each platform. Based on unified access control, it can prevent issues such as abuse of third-party platform permissions and password leaks.

[0047] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0048] Figure 3 This is a schematic diagram of a unified login platform provided in an embodiment of the present invention. The platform includes:

[0049] The first request module 310 is used to send a login request to the unified login platform after the user creates a username on the unified login platform and return the corresponding Token;

[0050] The creation of a username by the user on the unified login platform also includes:

[0051] The unified login platform configures user permissions to access third-party platforms.

[0052] The second request module 320 is used to send a login request containing the username and token to the third-party platform when a user initiates a login request to the third-party platform.

[0053] The login verification module 330 is used to receive verification requests sent by third-party platforms and return the corresponding verification results.

[0054] The login access module 340 is used to receive the token returned by the third-party platform when the token verification is valid and the corresponding username exists on the third-party platform, so as to log in and jump to a new tab page to access resources based on the third-party platform token;

[0055] Error message module 350 is used to prompt the user with a login error based on information returned by a third-party platform when the verification result is an invalid token.

[0056] Specifically, the step of accessing resources by logging in using a third-party platform token and redirecting to a new tab page includes:

[0057] Users access third-party platform resources by carrying a third-party platform token.

[0058] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the systems and modules described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0059] Figure 4 This is a schematic diagram of an electronic device according to an embodiment of the present invention. The electronic device is used to enable cross-platform resource access. Figure 4 As shown, the electronic device 4 in this embodiment includes a memory 410, a processor 420, and a system bus 430. The memory 410 includes an executable program 4101 stored thereon. As those skilled in the art will understand, Figure 4 The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0060] The following is combined Figure 4 A detailed introduction to each component of the electronic device:

[0061] The memory 410 can be used to store software programs and modules. The processor 420 executes various functional applications and data processing of the electronic device by running the software programs and modules stored in the memory 410. The memory 410 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device (such as cached data), etc. In addition, the memory 410 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0062] The memory 410 contains an executable program 4101 for network request methods. This executable program 4101 can be divided into one or more modules / units, which are stored in the memory 410 and executed by the processor 420 for tasks such as indoor positioning and mapping. Each module / unit can be a series of computer program instruction segments capable of performing a specific function, describing the execution process of the computer program 4101 in the electronic device 4. For example, the computer program 4101 can be divided into functional modules such as a first request module, a second request module, a login verification module, a login access module, and an error message module.

[0063] The processor 420 is the control center of the electronic device. It connects various parts of the electronic device via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 410, and by calling data stored in the memory 410, it performs various functions and processes data, thereby monitoring the overall status of the electronic device. Optionally, the processor 420 may include one or more processing units; preferably, the processor 420 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, application programs, etc., and the modem processor mainly handles wireless communication. It is understood that the modem processor may also not be integrated into the processor 420.

[0064] The system bus 430 is used to connect various functional components inside the computer, transmitting data, address, and control information. Its type can be, for example, a PCI bus, an ISA bus, or a CAN bus. Instructions from the processor 420 are transmitted to the memory 410 via the bus, and the memory 410 sends data back to the processor 420. The system bus 430 is responsible for data and instruction exchange between the processor 420 and the memory 410. Of course, the system bus 430 can also connect to other devices, such as network interfaces and display devices.

[0065] In this embodiment of the invention, the executable program executed by the processing 420 of the electronic device includes:

[0066] After a user creates a username on the unified login platform, they send a login request to the unified login platform, which then returns a Token.

[0067] When a user initiates a login request to a third-party platform, the unified login platform sends a login request containing the username and token to the third-party platform. The third-party platform then sends a verification request to the unified login platform backend, and the unified login platform backend returns the verification result.

[0068] If the verification result is that the token is invalid, the user will be prompted with a login error based on the information returned by the third-party platform.

[0069] If the verification result is that the Token is valid, the third-party platform will check if the username exists. If the username already exists, the third-party platform will return the Token.

[0070] Users log in using a third-party platform token and are redirected to a new tab page to access resources.

[0071] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and modules described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0072] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0073] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A cross-platform resource access method, characterized in that, include: After a user creates a username on the unified login platform, they send a login request to the unified login platform frontend. The unified login platform frontend forwards the request to the backend, and the unified login platform backend returns a Token to the unified login platform frontend. When a user initiates a login request to a third-party platform through the unified login platform frontend, the unified login platform frontend sends a login request containing the username and token to the third-party platform, and the third-party platform then initiates a verification request to the unified login platform backend, and the unified login platform backend returns the verification result. If the verification result is that the token is invalid, the user will be prompted with a login error based on the information returned by the third-party platform. If the verification result is that the Token is valid, the third-party platform will check if the username exists. If the username already exists, the third-party platform will return the Token to the unified login platform frontend. The Token returned by the third-party platform and the Token returned by the unified login platform backend are different. Users access resources by logging in through the unified login platform front end and being redirected to a new tab page based on their third-party platform token.

2. The method according to claim 1, characterized in that, After a user creates a username on the unified login platform, the process of initiating a login request to the unified login platform frontend also includes: The unified login platform configures user permissions to access third-party platforms.

3. The method according to claim 1, characterized in that, If the verification result indicates that the Token is valid, the third-party platform checks whether the username exists. If the username already exists, the third-party platform returns the Token to the unified login platform frontend, including: If the username does not exist on the third-party platform, the third-party platform will create the user based on the username and assign a default password and default permissions.

4. The method according to claim 1, characterized in that, The process of users accessing resources by logging in through the unified login platform front-end and being redirected to a new tab page based on a third-party platform token includes: Users access third-party platform resources by carrying a third-party platform token.

5. A unified login platform, characterized in that, At least include: The first request module is used when a user creates a username on the unified login platform. The unified login platform frontend receives the login request, forwards the request to the backend, and the unified login platform backend returns a Token to the unified login platform frontend. The second request module is used to send a login request containing the username and token to the third-party platform when a user initiates a login request to the third-party platform through the unified login platform front end. The login verification module is used to receive verification requests sent by third-party platforms and return the corresponding verification results. The login access module is used to receive the token returned by the third-party platform when the token verification is valid and the corresponding username exists on the third-party platform. The unified login platform front-end then uses the token from the third-party platform to log in and jump to a new tab page to access resources. The token returned by the third-party platform and the token returned by the unified login platform back-end are different. The error message module is used to prompt the user with a login error when the verification result is an invalid token, based on the information returned by the third-party platform.

6. The platform according to claim 5, characterized in that, The creation of a username by a user on the unified login platform also includes: The unified login platform configures user permissions to access third-party platforms.

7. The platform according to claim 5, characterized in that, The method of accessing resources by logging in using a third-party platform token and redirecting to a new tab page includes: Users access third-party platform resources by carrying a third-party platform token.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of a cross-platform resource access method as described in any one of claims 1 to 4.

9. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed, it implements the steps of a cross-platform resource access method as described in any one of claims 1 to 4.

Images