Authentication method and device based on universal object cloud storage system

By determining user parameters and sending authentication results in the business system, the problem of the inability of general object cloud storage systems to authenticate users is solved, thus improving data transmission efficiency and security.

CN118916865AInactive Publication Date: 2024-11-08GUANGZHOU SANQI DREAM NETWORK TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202411150986.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-20
Publication Date
2024-11-08
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

When receiving and uploading files, the general-purpose object cloud storage system cannot record in detail which specific user each file corresponds to, making it impossible to effectively authenticate users requesting access to files.

Method used

The business system provides a file access link to the user to be authenticated. By determining the parameters of the original user and the user to be authenticated, it determines whether the user to be authenticated has permission to access the file and sends the determination result to the general object cloud storage system so that it can determine whether to return the file.

Benefits of technology

It enables effective authentication of users in the general object cloud storage system, reduces the transfer of files between the business system and the cloud storage system, and improves data transmission efficiency and security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118916865A_ABST
    Figure CN118916865A_ABST
Patent Text Reader

Abstract

The invention provides an authentication method and device based on a universal object cloud storage system. A business system provides a file access link for a user to be authenticated; the file access link is a link which is returned by a general object cloud storage system and is used for accessing a file after an original user uploads the file to the general object cloud storage system, determining a first parameter corresponding to the original user in response to the access of the user to be authenticated to the file access link, and judging whether the to-be-authenticated user has permission to access the file access link or not according to the file access link corresponding to the to-be-authenticated user and user parameters corresponding to the to-be-authenticated user, and sending a judgment result to the universal object cloud storage system. And the universal object cloud storage system determines whether to return the file to the user to be authenticated or not according to the judgment result.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to an authentication method and device based on a general object cloud storage system. Background Art

[0002] At present, as the business scale of each company or organization continues to expand, the data information that needs to be stored has also shown explosive growth, and traditional storage solutions can no longer meet the growing data storage needs. Based on this, with the rapid development of big data and artificial intelligence, the use of object cloud storage services has become a common solution for enterprises to store and process data. The object cloud storage service occupies an important position in the field of cloud computing with its high scalability and flexibility. For example, for each business system that needs to store multiple user information, the business system will store each user's data in the cloud by using the object cloud storage service provided by each cloud service provider.

[0003] At the same time, business systems may need to switch cloud service providers due to technology updates and migrations, changes in the attributes of the business development environment, and changes in business needs. Because different cloud service providers usually provide their own unique API interfaces and function sets, when the business system switches cloud service providers, developers are required to write configuration codes based on the new development documents provided by the corresponding cloud service providers. This poses a great challenge to developers and maintenance personnel, especially in terms of authentication. Different object service and component providers use different authentication models, making development and maintenance difficult.

[0004] Based on this, by connecting all business systems of an enterprise or organization to a universal object cloud storage system, the business system no longer needs to be directly connected to each cloud service provider. It only needs to be configured once according to the development documentation provided by the universal object cloud storage system to connect to the universal object cloud storage system. Then, user data that needs to be uploaded to the cloud server can be uploaded to the corresponding cloud server through the universal object cloud storage system. Even if the cloud service provider is switched, there is no need to perform new configuration.

[0005] Among them, Figure 1 As shown, the general object cloud storage system can be connected to multiple business systems at the same time, and each user on each business system can upload the data to be uploaded to each cloud server through the general object cloud storage system. In this case, the user performs the data upload operation through the front-end interface of the business system. In this process, after obtaining authorization from the business system server, the user can directly transfer the files to be uploaded from the client of the business system to the general object cloud storage system, and upload the files to the cloud through the service of the general object cloud storage system. This process eliminates the step of transferring the files through the business system server, thereby improving the upload efficiency.

[0006] When the general object cloud storage system receives the file uploaded by the user and completes the upload, it will generate a file access link for accessing the uploaded file and return this link to the corresponding business system. This link is a unique identifier that the business system can provide to the user so that the user can access and download the file in the future.

[0007] However, since there are usually a large number of users in the business system who need to upload data, when receiving and uploading files, the general object cloud storage system only records which business system the file comes from, rather than recording in detail which specific user each file corresponds to. Therefore, when a user clicks a file access link to request access to a file, the general object cloud storage system cannot directly authenticate the user who clicked the link.

[0008] Therefore, how the general object cloud storage system authenticates users who request to access files on the cloud server has become an urgent problem to be solved. Summary of the invention

[0009] The embodiments of this specification provide an authentication method and device based on a general object cloud storage system to partially solve the problems existing in the above-mentioned prior art.

[0010] The embodiments of this specification adopt the following technical solutions:

[0011] This specification provides an authentication method based on a general object cloud storage system, the method comprising:

[0012] The business system provides a file access link to the user to be authenticated; the file access link is a link for accessing the file returned by the general object cloud storage system after the original user uploads the file to the general object cloud storage system;

[0013] In response to the access of the file access link by the user to be authenticated, determining a first parameter corresponding to the original user and a user parameter corresponding to the user to be authenticated;

[0014] Determining whether the user to be authenticated has the authority to access the file access link according to the user parameter and the first parameter;

[0015] The judgment result is sent to the general object cloud storage system, so that the general object cloud storage system determines whether to return the file to the user to be authenticated according to the judgment result.

[0016] Optionally, before the business system provides the file access link to the user to be authenticated, the method further includes:

[0017] Determine the file to be uploaded by the original user;

[0018] Uploading the file to be uploaded to the cloud server through the general object cloud storage system;

[0019] A file access link for accessing the file to be uploaded, which is returned by the general object cloud storage system after uploading the file to be uploaded, is received.

[0020] Optionally, uploading the file to be uploaded to the cloud server through the general object cloud storage system specifically includes:

[0021] Receiving metadata of the file to be uploaded sent by the client where the original user is located;

[0022] Determine and store a first parameter corresponding to the original user according to the metadata;

[0023] Sending the first parameter to the general object cloud storage system;

[0024] Receiving the upload credential returned by the general object cloud storage system according to the first parameter;

[0025] The upload credential is returned to the client where the original user is located, so that the client where the original user is located sends the upload credential and the file to be uploaded to the general object cloud storage system, so that the general object cloud storage system uploads the file to be uploaded to the cloud server according to the upload credential and returns a file access link.

[0026] Optionally, determining user parameters corresponding to the user to be authenticated specifically includes:

[0027] Receive the user parameters called back by the general object cloud storage system to the business system; the user parameters are the user parameters corresponding to the user to be authenticated and sent by the client where the user to be authenticated is located and received by the general object cloud storage system in response to accessing the file access link.

[0028] Optionally, receiving the user parameter called back by the general object cloud storage system to the business system specifically includes:

[0029] Receiving the secret parameter called back by the general object cloud storage system to the business system; the secret parameter is a secret parameter obtained by encrypting the user parameter after the general object cloud storage system receives the user parameter sent by the client where the user to be authenticated is located;

[0030] The secret parameters are decrypted to determine the user parameters corresponding to the user to be authenticated.

[0031] Optionally, decrypting the secret state parameter specifically includes:

[0032] According to the system identifier carried by the confidentiality parameter, determining whether the confidentiality parameter is returned by the general object cloud storage system;

[0033] If so, decrypt the secret parameters.

[0034] Optionally, determining user parameters corresponding to the user to be authenticated specifically includes:

[0035] In response to the to-be-authenticated user accessing the file access link, the user parameter is obtained from a client where the to-be-authenticated user is located.

[0036] This specification provides an authentication device based on a general object cloud storage system, the device comprising:

[0037] A module is provided, which is used for the business system to provide a file access link to the user to be authenticated; the file access link is a link for accessing the file returned by the general object cloud storage system after the original user uploads the file to the general object cloud storage system;

[0038] A determination module, configured to determine, in response to the access of the to-be-authenticated user to the file access link, a first parameter corresponding to the original user and a user parameter corresponding to the to-be-authenticated user;

[0039] An authentication module, used to determine whether the user to be authenticated has the authority to access the file access link according to the user parameter and the first parameter;

[0040] The sending module is used to send the judgment result to the general object cloud storage system, so that the general object cloud storage system determines whether to return the file to the user to be authenticated according to the judgment result.

[0041] This specification provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned authentication method based on the general object cloud storage system is implemented.

[0042] This specification provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned authentication method based on the general object cloud storage system when executing the program.

[0043] At least one of the above technical solutions adopted in the embodiments of this specification can achieve the following beneficial effects:

[0044] The embodiment of the specification discloses an authentication method based on a general object cloud storage system, wherein a business system provides a file access link to a user to be authenticated, and in response to the user to be authenticated accessing the file access link, determines a first parameter corresponding to the original user and a user parameter corresponding to the user to be authenticated, and judges whether the user to be authenticated has the right to access the file access link according to the user parameter and the first parameter, and sends the judgment result to the general object cloud storage system, so that the general object cloud storage system determines whether to return the file to the user to be authenticated according to the judgment result. Through this method, after the user to be authenticated accesses the file access link, the business system obtains the user parameter of the user to be authenticated, authenticates the user to be authenticated according to the user parameter, and sends the judgment result to the general object cloud storage system that can obtain the file corresponding to the file access link from the cloud server but cannot authenticate the user to be authenticated, so that the general object cloud storage system can authenticate the user to be authenticated according to the judgment result and determine whether to return the file corresponding to the file access link to the user to be authenticated. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The drawings described herein are used to provide a further understanding of this specification and constitute a part of this specification. The illustrative embodiments and descriptions of this specification are used to explain this specification and do not constitute an improper limitation on this specification. In the drawings:

[0046] Figure 1 It is a schematic diagram of the architecture of a business system provided in an embodiment of this specification storing files in a cloud server based on a general object cloud storage system;

[0047] Figure 2 A flowchart of an authentication method based on a general object cloud storage system provided in an embodiment of this specification;

[0048] Figure 3 A schematic diagram of a multi-party process for an original user to upload a file to be uploaded provided in an embodiment of this specification;

[0049] Figure 4 A schematic diagram of a multi-party process for obtaining user parameters by a business system provided in an embodiment of this specification;

[0050] Figure 5 A schematic diagram of the structure of an authentication device based on a general object cloud storage system provided in an embodiment of this specification;

[0051] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0052] In order to make the purpose, technical solutions and advantages of this specification more clear, the technical solutions of this specification will be clearly and completely described below in combination with the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0053] The technical solutions provided by the embodiments of this specification are described in detail below in conjunction with the accompanying drawings.

[0054] Figure 2 The following is a flowchart of an authentication method based on a general object cloud storage system in this specification, which may specifically include the following steps:

[0055] S200: The business system provides a file access link to the user to be authenticated; the file access link is a link for accessing the file returned by the general object cloud storage system after the original user uploads the file to the general object cloud storage system.

[0056] In the embodiments of this specification, the business system may be a platform or software that provides specific services or functions for each user to use. For example, the business system may be a game system, an office system, or a data storage system. In the process of using the software, users on the business system can upload files obtained from the business system or files from other platforms through the file upload interface provided by the business system and store them in the cloud server. When files are needed, they can obtain the corresponding files according to the file access link corresponding to the required files provided by the business system.

[0057] Furthermore, in order to reduce the configuration work required when the business system is connected to different cloud servers, the business system does not directly connect to each cloud service provider, but connects to a general object cloud storage system, such as Figure 1 In this way, the business system only needs to configure once according to the development document provided by the general object cloud storage system to access the general object cloud storage system, and then the user data that needs to be uploaded to the cloud server can be uploaded to each corresponding cloud server through the general object cloud storage system, and no new configuration is required even if the cloud service provider is switched.

[0058] It should be noted that a general object cloud storage system can be connected to multiple business systems. For each business system, each user on the business system can upload files to the server through the file upload interface provided by the business system. In addition, the general object cloud storage system also supports a variety of cloud service providers and cloud storage services, so that business systems can flexibly select and use them.

[0059] Specifically, after the business system is connected to the general object cloud storage system, when the users of the business system upload data, although the original users perform data upload operations in the front-end interface provided by the business system, in fact, after obtaining authorization from the business system server, the files that the users need to upload can be directly transmitted from the client of the business system to the general object cloud storage system, and uploaded to the cloud server through the general object cloud storage service without passing through the server of the business system.

[0060] Furthermore, after the general object cloud storage system obtains the files to be uploaded and uploads them, it will return the file access link for accessing the uploaded files to the server of the corresponding business system. Once the file access link is clicked, the general object cloud storage system will send a request to the cloud to obtain the file according to the parameters in the link.

[0061] In the embodiment of the present specification, the user who has historically uploaded the file corresponding to the file access link through the general object cloud storage system is regarded as the original user, and the user who wishes to access the uploaded file corresponding to the file access link is regarded as the user to be authenticated, wherein the user to be authenticated can be the original user or other users.

[0062] Based on this, the server connected to the background of the business system can provide the file access link to the user to be authenticated. Specifically, in response to the operation of the user to be authenticated on the client of the business system, the server of the business system can determine the file identifier of the file that the user to be authenticated needs to access, and determine the file access link returned by the general object cloud storage system for accessing the file corresponding to the file identifier based on the file identifier, and provide the file access link to the user to be authenticated. Of course, the business system can also directly provide the file access link to the user to be authenticated after obtaining the file access link returned by the general object cloud storage system. The specific method of providing the file access link is not limited in the embodiments of this specification.

[0063] S202: In response to the to-be-authenticated user accessing the file access link, determining a first parameter corresponding to the original user and a user parameter corresponding to the to-be-authenticated user.

[0064] Specifically, when the user to be authenticated attempts to access a file through a file access link, the business system triggers an authentication process and determines the first parameter corresponding to the original user according to the file access link. Specifically, the original user corresponding to the file identifier corresponding to the file access link can be queried in a database to determine the first parameter corresponding to the original user.

[0065] Furthermore, the first parameter may include the identity information of the original user, such as the user ID, role, permission group, etc. of the original user, which is used to subsequently determine whether the user to be authenticated has the authority to access the file corresponding to the file access link. In addition, the first parameter may also include the permission level parameter and sharing setting parameter of the file. Among them, the permission level parameter can determine the permission level of the file corresponding to the file access link, such as whether the file is private, public or read-only, editable and other specific permission levels, which users, thereby determining which users can access the file and what operations they can perform on the file. The sharing setting parameters are specific sharing rules set by the original user, such as the validity period of the link, access password or a specific user list. These sharing setting parameters can also determine which users can access the file through the link. It should be noted that the specific content of the first parameter corresponding to the original user is not limited in the embodiments of this specification.

[0066] Furthermore, the business system can also directly respond to the operation of the user to be authenticated on the front-end interface, or determine the user parameters of the user to be authenticated through the response of the general object cloud storage system to the file access link. Specifically, the user parameters include the identity information of the user to be authenticated, such as user ID, user name or email address, etc., which are used to subsequently verify the identity of the user and retrieve its related permissions. Of course, the user parameters can also include information such as access credentials and access history, which are used to prove the information of the user to be authenticated and to judge the frequency and intention of the user to be authenticated to access files, etc. The specific user parameters are not limited in the embodiments of this specification.

[0067] S204: Determine, based on the user parameter and the first parameter, whether the user to be authenticated has the authority to access the file access link.

[0068] Furthermore, after obtaining the user parameters and the first parameter, the business system will authenticate the identity of the user to be authenticated according to the identity information in the user parameters, and check whether the identity information provided by the user to be authenticated matches the information stored in the system. After successful authentication, according to the authority judgment mechanism preset by the system, it is judged whether the user to be authenticated has the authority to access the file access link according to the user parameters and the first parameter.

[0069] Furthermore, if the business system performs authentication based on roles or permission groups, the business system will determine the permission group or user role of the user who can access the file corresponding to the file access link based on the first parameter, and then determine based on the user parameters whether the role or permission group to which the user to be authenticated belongs has permission to access the file; if so, the user to be authenticated has permission to access the file corresponding to the file access link; otherwise, the user to be authenticated does not have permission to access the file corresponding to the file access link.

[0070] If the business system determines whether the user to be authenticated has the right to access the file based on the file's permission level, it will first determine whether the file is public based on the first parameter. When the file is set to private, the business system will determine whether the user to be authenticated belongs to the user group that has the right to access the file based on the user parameters. The user to be authenticated must be explicitly added to the list of users allowed to access the file, or the role / permission group to which he belongs is authorized to access the file. If the file is set to public, the system will usually allow all users to access the file without further verifying the identity or permissions of the user to be authenticated.

[0071] Of course, in some embodiments, the user to be authenticated may need specific credentials, such as a password, verification code or token, to access the file to ensure that only authenticated users can access the file. The business system can then determine the first credential that can access the file based on the first parameter, and determine the user credential provided by the user to be authenticated based on the user parameter. Then, the user to be authenticated is authenticated based on the first credential and the user credential. If the credential verification is successful, the user to be authenticated has the right to access the file corresponding to the file access link, otherwise, the system will reject the access request and may require the user to be authenticated to re-enter the credential or provide other forms of identity authentication.

[0072] It should be noted that the specific method by which the business system determines whether the user to be authenticated has the authority to access the file corresponding to the file access link according to the first parameter and the user parameter is not limited in this embodiment of the specification.

[0073] S206: Send the judgment result to the general object cloud storage system, so that the general object cloud storage system determines whether to return the file to the user to be authenticated according to the judgment result.

[0074] Specifically, since when the original user uploads the file, the file is directly uploaded to the server through the general object cloud storage system, and the file access link is also returned by the general object cloud storage system, the general object cloud storage system will respond to the access of the file access link by the user to be authenticated, and determine the file identifier of the file corresponding to the file access link according to the link parameters in the file access link. Then, according to the file identifier, a file access request is sent to the cloud server, so that the cloud server receives the file access request and returns the file corresponding to the file access link to the general object cloud storage system according to the file access request.

[0075] Furthermore, after the general object cloud storage system obtains the file, it is unable to directly authenticate the user to be authenticated, so the business system will send the judgment result determined according to the user parameters to the general object cloud storage system, so that the general object cloud storage system can determine whether to return the file obtained from the server to the user to be authenticated based on the judgment result.

[0076] It should be noted that after the general object cloud storage system obtains the file and determines that the user to be authenticated has the right to access the file, the general object cloud storage system will directly return the file to the client of the user to be authenticated, rather than returning the file to the server of the business system, avoiding unnecessary transfer of files between the business system and the general object cloud storage system, thereby reducing the load on the business system server. At the same time, this also improves the efficiency of data transmission, because files can be directly transferred from the cloud storage system to the user end faster, reducing the delay on the transmission path.

[0077] In addition, in order to ensure the security of file transmission, the general object cloud storage system can also implement a series of security measures before returning the file to the user to be authenticated. For example, the file is encrypted to ensure that the file content is not stolen or tampered with by unauthorized parties during the transmission process. When the file safely arrives at the user terminal corresponding to the user to be authenticated, the user can use the corresponding key to decrypt it, thereby accessing the original content of the file. The specific transmission process is not limited in this embodiment of the specification.

[0078] based on Figure 2An authentication method based on a general object cloud storage system is provided. After a user to be authenticated accesses a file access link, a business system obtains user parameters of the user to be authenticated, authenticates the user to be authenticated according to the user parameters, and sends a judgment result to a general object cloud storage system that can obtain the file corresponding to the file access link from a cloud server but cannot authenticate the user to be authenticated, so that the general object cloud storage system can authenticate the user to be authenticated according to the judgment result and determine whether to return the file corresponding to the file access link to the user to be authenticated.

[0079] Furthermore, before the business system provides the file access link to the user to be authenticated, it will also determine the file to be uploaded by the original user, upload the file to be uploaded to the cloud server through the general object cloud storage system, and receive the file access link for accessing the file to be uploaded, which is returned by the general object cloud storage system after uploading the file to be uploaded.

[0080] Specifically, the file access link is a link for accessing the uploaded file to be uploaded, which is returned by the general object cloud storage system to the business system after the original user uploads the file to be uploaded. When the original user uploads the file to be uploaded, the business system will determine the file to be uploaded of the original user based on the operation of the original user in the user interface of the business system, and verify the file to be uploaded, such as checking the file size, type, whether it contains malware, etc. If the verification is successful, the client of the business system where the original user is located will send the file to be uploaded to the general object cloud storage through the general object cloud storage system, so that the file to be uploaded is uploaded to the cloud server through the general object cloud storage system.

[0081] After the file is successfully uploaded, the general object cloud storage system will generate a file access link for accessing the file to be uploaded, and return the link to the business system so that the business system can subsequently provide the file access link to the user to be authenticated.

[0082] Furthermore, when the business system receives the file access link returned by the general object cloud storage system, it associates the link with the original user, the file to be uploaded, and other permission information related to the file to be uploaded, and stores it in the database or other storage system of the business system as the first parameter corresponding to the original user, which will be used for subsequent authentication of the user to be authenticated by the business system.

[0083] Furthermore, uploading the file to be uploaded to the cloud server through the universal object cloud storage system can be specifically as follows: receiving metadata of the file to be uploaded sent by the client where the original user is located, determining and storing a first parameter corresponding to the original user based on the metadata, sending the first parameter to the universal object cloud storage system, receiving an upload credential returned by the universal object cloud storage system based on the first parameter, and returning the upload credential to the client where the original user is located, so that the client where the original user is located sends the upload credential and the file to be uploaded to the universal object cloud storage system, so that the universal object cloud storage system uploads the file to be uploaded to the cloud server based on the upload credential, and returns a file access link.

[0084] Specifically, Figure 3 As shown, when the original user uploads the file to be uploaded to the cloud server, he will select the file to be uploaded through his client and trigger the upload operation. In this process, the client of the original user will obtain the metadata of the file to be uploaded, such as key information such as file name, size, type, etc., and then send these metadata to the server of the business system. After receiving the metadata, the server of the business system will determine the first parameters such as file access rights and original user related information based on business logic and security policies.

[0085] Next, the business system will send the first parameter to the general object cloud storage system so that the general object cloud storage system generates an upload credential for the file to be uploaded. After verifying the legitimacy of the first parameter, the general object cloud storage system will generate a unique upload credential containing information such as a signature, a key or an upload URL, and return the credential securely to the business system. After receiving the upload credential, the business system will immediately pass it to the client of the original user through a secure channel.

[0086] Furthermore, after receiving the upload credential, the client of the original user will encapsulate it together with the file to be uploaded in a file upload request, and send it to the general object cloud storage system through an encrypted communication protocol, so that the general object cloud storage system can verify the validity of the upload credential and check the integrity of the file content after receiving the file upload request. Once the verification is passed, the general object cloud storage system will store the file to be uploaded on the designated cloud server and set the corresponding access rights according to the first parameter determined previously.

[0087] Furthermore, after the file to be uploaded is successfully uploaded to the cloud server, the general object cloud storage system will generate a unique file access link, and based on the session when obtaining the upload credential, return the file access link to the business system, so that the business system stores the file access link and determines the original user corresponding to the file access link, as well as the first parameter corresponding to the original user.

[0088] Furthermore, when authenticating the user to be authenticated, the business system determines the user parameters corresponding to the user to be authenticated, which may be specifically, receiving the user parameters callback by the general object cloud storage system to the business system, wherein the user parameters are the user parameters corresponding to the user to be authenticated and sent by the client where the user to be authenticated is located, received by the general object cloud storage system in response to access to the file access link.

[0089] In other words, Figure 4 As shown, in response to the access of the to-be-authenticated user to the file access link, the general object cloud storage system obtains the file from the cloud server storing the file corresponding to the file access link, and also obtains the user parameters of the to-be-authenticated user from the client where the to-be-authenticated user is located. These user parameters may include but are not limited to the user's authentication token, user name, user ID, session information and other key information used to verify the user's identity and authority.

[0090] Furthermore, since the general object cloud storage system cannot authenticate the user to be authenticated according to the user parameters, the general object cloud storage system will call back the user parameters to the business system according to the preset callback address, so that the business system can authenticate the user to be authenticated according to the received user parameters. Specifically, after receiving the callback request and the user parameters therein, the business system will perform a series of processing according to the determined first parameter and the user parameters to verify the identity and authority of the user to be authenticated, so as to confirm the validity of the user parameters and whether the user to be authenticated has the authority to access the specific file, which will not be described in detail here.

[0091] Furthermore, if the verification is successful, that is, the user to be authenticated does have the permission to access the file, the business system will return a successful authentication response to the general object cloud storage system. This response can be a simple confirmation signal, or it can contain some additional authentication information or tokens for the cloud storage system to continue processing the original file access request. If the verification fails, that is, the user to be authenticated does not have the access rights, the business system will return an authentication failure response. After receiving this response, the cloud storage system will reject the file access request of the user to be authenticated accordingly, such as displaying an error message to the user to be authenticated or redirecting to the login page. The specific access rejection operation is not limited in the embodiments of this specification.

[0092] Furthermore, the business system receives the user parameters that the general object cloud storage system calls back to the business system, which can be specifically: receiving the confidential parameters that the general object cloud storage system calls back to the business system, the confidential parameters being the confidential parameters obtained by encrypting the user parameters after the general object cloud storage system receives the user parameters sent by the client where the user to be authenticated is located, decrypting the confidential parameters to determine the user parameters corresponding to the user to be authenticated.

[0093] Specifically, in order to prevent user parameters from being intercepted or tampered with during transmission and to further ensure the accuracy of user parameters, the general object cloud storage system can obtain user parameters from the client where the user to be authenticated is located, and then use one or more encryption algorithms to encrypt them to obtain confidential parameters corresponding to the user parameters, and then call back the confidential parameters to the business system.

[0094] Correspondingly, after receiving the secret state parameters called back by the general object cloud storage system to the business system, the business system will decrypt the secret state parameters through the decryption method corresponding to the encryption method to obtain the user parameters corresponding to the user to be authenticated. It should be noted that the general object cloud storage system can encrypt the user parameters through asymmetric encryption, and of course, the user parameters can also be encrypted through homomorphic encryption and other methods. The specific encryption method is not limited in this embodiment of the specification.

[0095] Taking asymmetric encryption as an example, the general object cloud storage system will generate or pre-acquire a public key. This public key can be generated by the general object cloud storage system itself, or provided by the business system and shared with the general object cloud storage system through a secure channel. Then, the general object cloud storage system will use the public key to encrypt the user parameters to obtain the secret parameters. After encryption, even if the secret parameters are intercepted during transmission, the attacker cannot decrypt them to obtain the original user parameters. Correspondingly, the business system will generate or pre-acquire a private key corresponding to the public key of the general object cloud storage system, which is used to decrypt the secret parameters to obtain the original user parameters.

[0096] Furthermore, the business system decrypts the confidential parameters, which may be specifically determined by judging whether the confidential parameters are returned by the general object cloud storage system according to the system identifier carried by the confidential parameters, and if so, decrypting the confidential parameters.

[0097] When the business system processes the secret parameters called back from the general object cloud storage system, in order to ensure the security and accuracy of the decryption operation, the business system will take a series of verification measures to confirm the source and validity of the secret parameters. Specifically, when the business system receives a callback request from the general object cloud storage system, it will first extract the secret parameters and the system identifier associated with it from the request. The system identifier is a unique identifier used to identify different systems or services, which is included in the request header, request body, or a specific encrypted field.

[0098] Then, the business system will compare the extracted system ID with the pre-stored or configured legal system ID. If the comparison result is consistent, that is, the system ID matches a system ID recognized by the business system, then the business system can assume that this secret parameter is returned by the general object cloud storage system, and continue the subsequent decryption operation. If the comparison result is inconsistent, that is, the system ID cannot match any legal system ID, then the business system will refuse to process this secret parameter.

[0099] Furthermore, determining the user parameter corresponding to the user to be authenticated may specifically be obtaining the user parameter from a client where the user to be authenticated is located in response to the user to be authenticated accessing the file access link.

[0100] In other words, for business systems corresponding to uploaded files that do not require high file confidentiality, or business systems with a higher security level, when obtaining the parameters of the user to be authenticated, the business system does not need to rely on the user parameters called back by the general object cloud storage system, but can directly respond to the access of the file access link by the user to be authenticated on the client to obtain the corresponding user parameters.

[0101] It should be noted that although the general object cloud storage system will respond to the access to the file access link, obtain the file from the cloud server and directly return it to the client of the user to be authenticated, the business system cannot obtain the specific file. However, the business system can still respond to the access to the file access link by the user to be authenticated at the same time as the general object cloud storage system responds to the access to the file access link, and only obtain the user parameters from the client of the user to be authenticated. Then, the authentication operation is performed on the user to be authenticated based on the user parameters, and it is determined whether the user to be authenticated has the authority to access the file access link, and the judgment result is sent to the general object cloud storage system.

[0102] The above is an authentication method based on a general object cloud storage system provided in an embodiment of this specification. Based on the same idea, this specification also provides corresponding devices, storage media and electronic devices.

[0103] Figure 5A schematic diagram of a structure of an authentication based on a general object cloud storage system provided in an embodiment of this specification, wherein the device comprises:

[0104] A module 500 is provided, which is used by the business system to provide a file access link to the user to be authenticated; the file access link is a link for accessing the file returned by the general object cloud storage system after the original user uploads the file to the general object cloud storage system;

[0105] A determination module 502, configured to determine, in response to the to-be-authenticated user accessing the file access link, a first parameter corresponding to the original user and a user parameter corresponding to the to-be-authenticated user;

[0106] An authentication module 504, configured to determine whether the user to be authenticated has the authority to access the file access link according to the user parameter and the first parameter;

[0107] The sending module 506 is used to send the judgment result to the general object cloud storage system, so that the general object cloud storage system determines whether to return the file to the user to be authenticated according to the judgment result.

[0108] Optionally, the providing module 500 is also used to determine the files to be uploaded by the original user; upload the files to be uploaded to the cloud server through the general object cloud storage system; and receive a file access link for accessing the files to be uploaded, which is returned by the general object cloud storage system after uploading the files to be uploaded.

[0109] Optionally, the providing module 500 is also used to receive metadata of the file to be uploaded sent by the client where the original user is located; determine and store a first parameter corresponding to the original user based on the metadata; send the first parameter to the general object cloud storage system; receive the upload credential returned by the general object cloud storage system based on the first parameter; return the upload credential to the client where the original user is located, so that the client where the original user is located sends the upload credential and the file to be uploaded to the general object cloud storage system, so that the general object cloud storage system uploads the file to be uploaded to the cloud server based on the upload credential, and returns a file access link.

[0110] Optionally, the determination module 502 is specifically used to receive the confidential parameters that the general object cloud storage system calls back to the business system; the confidential parameters are the confidential parameters obtained by the general object cloud storage system after receiving the user parameters sent by the client where the user to be authenticated is located, and encrypting the user parameters; decrypting the confidential parameters to determine the user parameters corresponding to the user to be authenticated.

[0111] Optionally, the determination module 502 is specifically configured to determine, based on a system identifier carried by the confidential parameter, whether the confidential parameter is returned by the general object cloud storage system; if so, decrypt the confidential parameter.

[0112] Optionally, the determining module 502 is specifically configured to obtain the user parameter from a client where the user to be authenticated is located in response to the user to be authenticated accessing the file access link.

[0113] This specification also provides a computer-readable storage medium, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, it can be used to perform the above Figure 2 An authentication method based on a general object cloud storage system is provided.

[0114] based on Figure 2 The authentication method based on the general object cloud storage system shown in the present specification also provides Figure 6 The structural diagram of the electronic device shown in FIG. Figure 6 At the hardware level, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, and may also include other hardware required for the business. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it to achieve the above Figure 2 The authentication method based on the general object cloud storage system.

[0115] Of course, in addition to software implementation, this specification does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is to say, the executor of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0116] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0117] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.

[0118] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0119] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0120] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, this specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0121] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0122] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0123] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0124] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0125] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0126] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0127] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including 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, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0128] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems or computer program products. Therefore, this specification may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0129] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0130] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0131] The above description is only an embodiment of the present specification and is not intended to limit the present specification. For those skilled in the art, the present specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification shall be included in the scope of the claims of the present specification.

Claims

1. An authentication method based on a general object cloud storage system, It is characterized in that The method is applied to a business system, and the method comprises: The business system provides a file access link to the user to be authenticated; the file access link is a link for accessing the file returned by the general object cloud storage system after the original user uploads the file to the general object cloud storage system; In response to the access of the file access link by the user to be authenticated, determining a first parameter corresponding to the original user and a user parameter corresponding to the user to be authenticated; Determining whether the user to be authenticated has the authority to access the file access link according to the user parameter and the first parameter; The judgment result is sent to the general object cloud storage system, so that the general object cloud storage system determines whether to return the file to the user to be authenticated according to the judgment result.

2. The method according to claim 1, It is characterized in that Before the business system provides the file access link to the user to be authenticated, the method further includes: Determine the file to be uploaded by the original user; Uploading the file to be uploaded to the cloud server through the general object cloud storage system; A file access link for accessing the file to be uploaded, which is returned by the general object cloud storage system after uploading the file to be uploaded, is received.

3. The method according to claim 2, It is characterized in that Uploading the file to be uploaded to the cloud server through the general object cloud storage system specifically includes: Receiving metadata of the file to be uploaded sent by the client where the original user is located; Determine and store a first parameter corresponding to the original user according to the metadata; Sending the first parameter to the general object cloud storage system; Receiving the upload credential returned by the general object cloud storage system according to the first parameter; The upload credential is returned to the client where the original user is located, so that the client where the original user is located sends the upload credential and the file to be uploaded to the general object cloud storage system, so that the general object cloud storage system uploads the file to be uploaded to the cloud server according to the upload credential and returns a file access link.

4. The method according to claim 1, It is characterized in that Determining the user parameters corresponding to the user to be authenticated specifically includes: Receive the user parameters called back by the general object cloud storage system to the business system; the user parameters are the user parameters corresponding to the user to be authenticated and sent by the client where the user to be authenticated is located and received by the general object cloud storage system in response to accessing the file access link.

5. The method according to claim 4, It is characterized in that Receiving the user parameter called back by the general object cloud storage system to the business system specifically includes: Receiving the secret parameter called back by the general object cloud storage system to the business system; the secret parameter is a secret parameter obtained by encrypting the user parameter after the general object cloud storage system receives the user parameter sent by the client where the user to be authenticated is located; The secret parameters are decrypted to determine the user parameters corresponding to the user to be authenticated.

6. The method according to claim 5, It is characterized in that Decrypting the secret parameters specifically includes: According to the system identifier carried by the confidentiality parameter, determining whether the confidentiality parameter is returned by the general object cloud storage system; If so, decrypt the secret parameters.

7. The method according to claim 1, It is characterized in that Determining the user parameters corresponding to the user to be authenticated specifically includes: In response to the to-be-authenticated user accessing the file access link, the user parameter is obtained from a client where the to-be-authenticated user is located.

8. An authentication device based on a general object cloud storage system, It is characterized in that The device is applied to a business system, and the device includes: A module is provided, which is used for the business system to provide a file access link to the user to be authenticated; the file access link is a link for accessing the file returned by the general object cloud storage system after the original user uploads the file to the general object cloud storage system; A determination module, configured to determine, in response to the access of the to-be-authenticated user to the file access link, a first parameter corresponding to the original user and a user parameter corresponding to the to-be-authenticated user; An authentication module, used to determine whether the user to be authenticated has the authority to access the file access link according to the user parameter and the first parameter; The sending module is used to send the judgment result to the general object cloud storage system, so that the general object cloud storage system determines whether to return the file to the user to be authenticated according to the judgment result.

9. A computer-readable storage medium, It is characterized in that The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, It is characterized in that When the processor executes the program, the method described in any one of claims 1 to 7 is implemented.

Citation Information

Patent Citations

  • Remote memory system applied to robot monitoring module

    CN104219477A

  • Method and device for achieving sharing of cloud storage space

    CN104468640A

  • A data sharing secondary authentication method and system

    CN109670322A

  • Service processing method, device, equipment and business system

    CN111541717A

  • Systems and Methods for Facilitating Access to Private Files Using a Cloud Storage System

    US20230367895A1