CN111625854B - Document encryption method, access method, server and system - Google Patents
Document encryption method, access method, server and system Download PDFInfo
- Publication number
- CN111625854B CN111625854B CN202010451486.6A CN202010451486A CN111625854B CN 111625854 B CN111625854 B CN 111625854B CN 202010451486 A CN202010451486 A CN 202010451486A CN 111625854 B CN111625854 B CN 111625854B
- Authority
- CN
- China
- Prior art keywords
- document
- token
- client
- access request
- user identity
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
Abstract
The embodiment of the application provides a document encryption method, an access method, a server and a system, wherein the document encryption method comprises the following steps: receiving a document access request from a client; verifying whether the document access request contains a token, wherein the token is sent to the client by the server according to the login information of the client, the token comprises encrypted user identity information, and the user identity information corresponds to the login information; if the document access request contains the token, checking whether the user identity information corresponding to the token has the access right of the document corresponding to the document access request; and if the user identity information corresponding to the token has the access right of the document corresponding to the document access request, adding an encrypted identifier corresponding to the user identity information in the document corresponding to the document access request, generating and sending the encrypted document to the client. According to the embodiment of the application, the encrypted identification corresponding to the user identity information is added into the document when the user acquires the document, so that the risk of document leakage is reduced.
Description
Technical Field
The present application relates to the field of document encryption technologies, and in particular, to a document encryption method, an access method, a server, and a system.
Background
Within an enterprise, there is often a need to share documents, which requires that one enterprise user upload a document to a designated location over a network, and that other enterprise users be able to obtain the document from the designated location. Some open software or systems, such as QQ, wechat, hundredth library, lan sharing disk, etc., may provide the document sharing function, however, many documents inside the enterprise are confidential and should not be distributed outside the enterprise, and the open software or system cannot meet the security requirement. In the related art, some document management applications can implement a certain encryption function, for example, when a user uploads a document at a client of the document management application, the client can add a watermark to the uploaded document, and the watermark can play a certain warning role when the document is spread, however, if the document is finally leaked, a specific leaking person cannot be traced, so that the document still has a high leakage risk.
Disclosure of Invention
In order to solve the technical problem, the application provides a document encryption method, an access method, a server and a system.
In a first aspect, an embodiment of the present application provides a document encryption method, where the method includes:
receiving a document access request from a client;
verifying whether the document access request contains a token, wherein the token is sent to a client by a server according to login information of the client, the token comprises encrypted user identity information, and the user identity information corresponds to the login information;
if the document access request contains the token, checking whether the user identity information corresponding to the token has the access right of the document corresponding to the document access request;
and if the user identity information corresponding to the token has the access authority of the document corresponding to the document access request, adding an encrypted identifier corresponding to the user identity information in the document corresponding to the document access request, generating and sending an encrypted document to the client.
In a second aspect, an embodiment of the present application provides a document access method, where the method includes:
receiving document access information input by a user, and generating a document access request according to the document access information and a token, wherein the token is sent to a client by a server according to login information of the client, the token comprises encrypted user identity information, and the user identity information corresponds to the login information;
sending the document access request to the server;
and receiving an encrypted document from the server, wherein the server acquires the user identity information according to a token in the document access request, verifies whether the user identity information has the access right of the document corresponding to the document access request, adds an encrypted identifier corresponding to the user identity information in the document corresponding to the document access request if the user identity information has the access right of the document corresponding to the document access request, and generates and sends the encrypted document to the client.
In a third aspect, an embodiment of the present application provides a server, where the server is configured to:
receiving a document access request from the client;
verifying whether the document access request contains the token or not, wherein the token is sent to a client by a server according to login information of the client, the token comprises encrypted user identity information, and the user identity information corresponds to the login information;
if the document access request contains the token, checking whether the user identity information corresponding to the token has the access right of the document corresponding to the document access request;
and if the user identity information corresponding to the token has the access right of the document corresponding to the document access request, adding an encrypted identifier corresponding to the user identity information in the document corresponding to the document access request, generating and sending an encrypted document to the client.
In a fourth aspect, an embodiment of the present application provides a document management system, which includes a client and the server in the third aspect, wherein the client is configured to:
receiving document access information input by a user, and generating a document access request according to the document access information and a token, wherein the token is sent to a client by a server according to login information of the client, the token comprises encrypted user identity information, and the user identity information corresponds to the login information;
sending the document access request to the server;
and receiving an encrypted document from the server, wherein the server acquires the user identity information according to a token in the document access request, verifies whether the user identity information has the access right of the document corresponding to the document access request, adds an encrypted identifier corresponding to the user identity information in the document corresponding to the document access request if the user identity information has the access right of the document corresponding to the document access request, and generates and sends the encrypted document to the client.
The document encryption method, the document access method, the server and the system provided by the application have the beneficial effects that:
according to the method and the device, when the user acquires the document, the encryption identification corresponding to the user identity information is added to the document, so that the documents acquired by different users have different encryption identifications, when the document is leaked, the user acquiring the document can be traced according to the encryption identification on the leaked document, and the risk of document leakage is reduced.
Drawings
In order to more clearly explain the technical solution of the present application, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious to those skilled in the art that other drawings can be obtained according to the drawings without any creative effort.
FIG. 1 is a flowchart illustrating a document encryption method according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a token generation method according to an embodiment of the present disclosure;
FIG. 3 is a diagram of an encrypted document provided by an embodiment of the present application;
FIG. 4 is a flowchart illustrating a document access method according to an embodiment of the present application;
fig. 5 is a schematic flowchart of a login method according to an embodiment of the present application;
fig. 6 is a schematic interaction diagram of a client and a server according to an embodiment of the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort shall fall within the protection scope of the present application.
In order to reduce the risk of document leakage, in a first aspect, embodiments of the present application provide a document encryption method, where the encryption method may be used in a server of a document management application, and the document management application may be a browser. Referring to fig. 1, the document encryption method includes the steps of:
step S110: a document access request is received from a client.
The client is a platform for interaction between the document management application program and the user, and the user can upload the document to the server through the client and can also acquire the document in the server through the client.
In some embodiments, when the document management application is a browser, the client is the web front-end of the browser.
If the user accesses a certain document, a document access request is generated at the client side, the document access request is sent to the server through the client side, and the server receives the document access request.
Step S120: and checking whether the document access request contains a token, wherein the token is sent to the client by the server according to the login information of the client, the token comprises encrypted user identity information, and the user identity information corresponds to the login information.
The token is generated by the server according to the login information of the client and is sent to the client. The token generation method can be seen in fig. 2, comprising steps S101-S102.
Step S101: and receiving login information from the client.
In some embodiments, the document access request can be generated only when the configurable client is in the login state, so as to improve the document access security.
The user can input login information at the client, the login information can include an account and a password of the user, wherein the account is an identifier capable of distinguishing identity information of different users and can be any one or more of a user name, a user mailbox, a user mobile phone number and a user work number, in this embodiment, the account can be the user name, and the login information includes the user name and the password. The client is in communication connection with the server, login information is sent to the server, and the server receives the login information from the client.
In some embodiments, if the client is logged into by a new user of the document management application, the new user may need to perform a user registration on the client prior to logging into the client, so that the user identity information is submitted to the server by the client. The server stores the user identity information, so that after login information from the client is received, the login information is verified according to the user identity information, if the login information does not correspond to the user identity information, login failure information is returned to the client, and the client displays the login failure information, such as information of password error or account error.
Step S102: and generating and sending a token to the client according to the login information.
In some embodiments, the server checks the login information according to the pre-stored user identity information, and if the login information corresponds to the user identity information, the user is determined to be logged in successfully. After the user logs in successfully, the server randomly generates a string of character strings, sets and stores the corresponding relation between the character strings and the user identity information to obtain a token, and the token becomes the encrypted user identity information. The server sends the token to the client for the client to store, so that the client can carry the token in the document access request when generating the document access request for the server to verify.
Further, when the token is generated, the server may set a validity period of the token, where the validity period may be set to a time for acquiring and applying the document after the user logs in the client under a normal condition, and if the validity period is exceeded for three days, it is considered that the risk of document leakage is increased.
The document access request generated by the client side contains the token by default. In some embodiments, the user may know that the token in the document access request contains the user identity information of the user, and delete or modify the token for the purpose of preventing tracking the document to be obtained by the user, so that the document access request does not contain the token generated by the server when the user successfully logs in. Therefore, when the document access request does not contain a token or the contained token does not correspond to the login information of the user, it can be determined that the risk of document leakage is increased.
After receiving the document access request, the server can extract a token from the document access request, and check whether the token is consistent with a token generated by the server when the user successfully logs in.
If the server determines that the document access request does not contain a token, the server directly proceeds to step S150 to prompt the user that the document acquisition has failed.
Step S130: and if the document access request contains the token, checking whether the user identity information corresponding to the token has the access right of the document in the document access request.
In order to prevent a document from being acquired by all users of the enterprise, the document uploader may set access rights when uploading the document to limit the users who can acquire the document.
When the server judges that the document access request contains the token generated by the server when the user successfully logs in, the user identity information corresponding to the token and the access authority of the document corresponding to the document access request are searched, and whether the user has the access authority of the document is checked.
In some embodiments, the token sets a validity period, so that if the document access request includes a token generated by the server when the user successfully logs in, whether the token is in the validity period is further determined, and when the token is in the validity period, whether the user identity information corresponding to the token has the access right of the document in the document access request is verified. When the token exceeds the validity period, or the token is within the validity period but has no access right, the process goes to step S150.
Step S140: and if the user identity information corresponding to the token has the access right of the document in the document access request, adding an encrypted identifier corresponding to the user identity information into the document, generating and sending an encrypted document to the client.
And the server adds the encrypted identifier to the document, generates and sends the encrypted document to the client.
In some embodiments, the client is a web front end of a browser, and only can show documents in a picture format, but cannot show documents in other formats, such as word, PPT, txt formats, and therefore, after a document uploader uploads documents in other than the picture format to the server, the server converts the documents into the picture format for storage.
Fig. 3 is a schematic diagram of an encrypted document according to an embodiment of the present application, as shown in fig. 3, the encrypted document is in a picture format, the encrypted identifier may be a watermark, and the content of the watermark corresponds to user identity information, such as part name, employee name, and job number. The server sends the encrypted document to the client, so that the user can obtain the encrypted document through the client, if the encrypted document is revealed, the user obtaining the encrypted document can be traced according to the encrypted identifier on the encrypted document, and the user is judged to be a document leakage person.
In the encrypted document, the denser the encrypted identifier is, the lower the success of the user in intercepting the document without the encrypted identifier is, so that the risk of document leakage is reduced, but the definition of the document content is also reduced; the more sparse the encrypted identification is, the higher the definition of the document content is, but the higher the success of a user in intercepting the document without the encrypted identification is, so that the risk of document leakage is increased. In order to balance document leakage risk with document content clarity, in some embodiments, a document uploader may set an encryption level for a document when uploading the document to a server via a client. When the server adds the encryption identifier to the document, the encryption identifier added to the document is denser according to the higher encryption level; and according to the lower encryption level, the encryption identifier added to the document is sparser.
Step S150: and generating and sending the access prohibition information to the client.
If the server determines that the document access request does not include the token, or the token exceeds the validity period, or the token is within the validity period but does not have access rights, then access prohibition information is generated.
The access prohibition information may be 403, and the server returns 403 to the client, prohibiting the user from accessing the document.
In a second aspect, embodiments of the present application further provide a server, which may be configured to execute the document encryption method shown in fig. 1 and the token generation method shown in fig. 2.
In a third aspect, corresponding to the above document encryption method, the present embodiment also provides a document access method, which is applicable to a client of a document management application, and referring to fig. 4, the document access method includes the following steps:
step S210: receiving document access information input by a user, and generating a document access request according to the document access information and a token, wherein the token is sent to a client by a server according to login information of the client, the token comprises encrypted user identity information, and the user identity information corresponds to the login information.
The token is generated by the server and sent to the client after the user successfully logs in the client, wherein the login method can refer to fig. 5, and comprises steps S201 to S203.
Step S201: and receiving login information input by a user.
The client can be provided with a login interface, and login information input by a user, such as a user name and a password, can be received at the login interface.
Step S202: and sending the login information to a server, so that the server generates a token according to the login information.
After receiving the login information, the client may send the login information to the server through the network, so that the server checks whether the login information corresponds to the user identity information, and if the login information corresponds to the user identity information, a token is generated, and the token generation process may refer to step S102, which is not described herein again. And after the server generates the token, the server sends the token to the client.
If the server verifies that the login information does not correspond to the user identity information, login failure information is returned to the client, the client is made to display the login failure information, such as password error or account error, and the user is prompted to input the login information again.
Step S203: receiving a token from the server.
And after receiving the token from the server, the client stores the token.
Further, the client can determine that the login is successful according to the token received from the server, and switch the login interface to the interface after the login.
In some embodiments, the interface of the client after logging in may be provided with a document query entry, such as a document search box, through which a user may search for a document, and when the user searches for a certain document, if the user wants to acquire the document, the user may input document access information by clicking a download control or a reading control on a page. And after receiving the document access information, the client generates a document access request according to the document access information and the token. The document access request can be a website, a command corresponding to the document access information and a token are set in the website by default, and the user can delete or modify the token.
Step S220: and sending the document access request to the server, enabling the server to acquire the user identity information according to the token, checking whether the user identity information has the access right of the document in the document access request, and generating and sending an encrypted document to the client if the user identity information has the access right of the document in the document access request.
The method comprises the steps that a client sends a document access request to a server, the server extracts document access information and a token from the document access request, if the server can extract the token, the token corresponds to login information of a user, in a valid period, user identity information corresponding to the token has access authority of a document corresponding to the document access information, an encryption identifier corresponding to the user identity information is added to the document corresponding to the document access request, and an encrypted document is generated and sent to the client.
In some embodiments, if the user deletes or modifies the token, or the server detects that the token is invalid, or the user does not have access, prior to step S220, the server will return no access information to the client.
Step S230: an encrypted document is received from the server.
After receiving the encrypted document, the client can display the encrypted document to a user or store the encrypted document to a preset path, so that the user can obtain the content of the encrypted document.
In a fourth aspect, embodiments of the present application further provide a client, where the client may be configured to execute the document access method shown in fig. 4 and the login method shown in fig. 5.
In order to further introduce the interaction flow between the server and the client, an interaction diagram between the client and the server is shown in the embodiment of the application. Referring to fig. 6, a user is a person who needs to obtain a document, a Web front end refers to a client, such as a Web end of a browser, a service system and an account system both belong to a server, and data of the server can be managed conveniently by setting the service system and the account system in the server. The Web front end, the service system and the account system form a document management system so as to realize the function of a document management application program.
The service system has a document uploading function, an access right checking function and a document encryption function. The document uploading person can call the document uploading function of the service system through the Web front end, upload the document to the service system, set the encryption level and the access authority of the document, and store the encryption level and the access authority of the document to the service system. The access right checking function is used for checking whether the user has the access right of the document. The document encryption function is used for encrypting the document according to the encryption level.
The account system stores user identity information, and the user identity information can be generated when a user registers in the document management system. The account system has a login verification function, a token issuing function and a token checking function. The login authentication function is used for verifying whether the user name and the password correspond to the user identity information, and if so, the login information is verified to be passed. the token issuance function is for issuing a token in accordance with the issuance. the token checking function is used for checking whether the token is consistent with the token stored in the account system or not and checking whether the token is in the valid period or not.
As shown in fig. 6, a user can access a system by inputting a user name and a password to a Web front end, wherein the system refers to a document management system, and the document management system comprises the Web front end, a business system and an account system.
And after receiving the user name and the password, the Web front end sends the user name and the password as login information to a service system for login. And the business system sends the login information to the account system to check the user name and the password in the login information. The account system verifies the user name and the password according to the user identity information, if the login information passes the verification, the token is issued by using a token issuing function, the token is sent to the service system, and the service system returns the token to the Web front end.
When a user accesses a document, the user inputs document access information to the Web front end, the Web front end generates a document access request according to the document access information and the token, the token is carried in the document access request, and the document access request is sent to a service system so as to request a document picture address. It should be noted that, in some embodiments, the Web front end based on the browser can only display a picture, and cannot display a document in a non-picture format, such as word, PPT, txt, or the like, and therefore, the Web front end can request a document picture address from a service system in a document access request to obtain document content.
And after receiving the document access request, the service system extracts the token from the document access request, and if the token can be extracted, namely the token exists, the service system sends the token to the account system to check the token.
After the account system receives the token, checking whether the token is consistent with the token stored in the account system, if so, generating a checking result that the token passes the checking if the token is consistent with the token in the valid period, and if not, generating a checking result that the token is invalid if the token is not consistent with the token in the valid period. And the account system sends the verification result of the token to the service system.
If the service system receives the check result that the token passes the check, the service system obtains user identity information according to the token, compares the user identity information with the document access authority stored in the service system, judges whether the user has the authority to access the document, if the user has the authority, the user information can be used as a watermark to synthesize a picture, and the picture information is returned to the Web front end, namely the encrypted document.
After receiving the picture information, the Web front end stores the picture information in a storage path preset by a user, or displays the picture information, so that the user can obtain the content of the picture information.
And if the Web front end cannot extract the token from the document access request, namely the token does not exist, or a verification result that the token is invalid is received, or the Web front end judges that the user does not have the right to access the document, returning 403 to the Web front end and forbidding the user to access the document.
In a fifth aspect, an embodiment of the present application further provides a document management system, where the document management system includes a client and a server, where the client may include the Web front end in the foregoing embodiment, and the server may include the business system and the account system in the foregoing embodiment.
According to the embodiment, the encryption identification corresponding to the user identity information is added to the document when the user acquires the document, so that the documents acquired by different users have different encryption identifications, when the document is leaked, the user acquiring the document can be traced according to the encryption identification on the leaked document, and the risk of document leakage is reduced.
Since the above embodiments are all described by referring to and combining with other embodiments, the same portions are provided between different embodiments, and the same and similar portions between the various embodiments in this specification may be referred to each other. And will not be described in detail herein.
It is noted that, in this specification, relational terms such as "first" and "second," and the like, are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a circuit structure, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such circuit structure, article, or apparatus. Without further limitation, the presence of an element defined by the phrase "comprising … …" does not preclude the presence of additional like elements in a circuit structure, article, or apparatus that comprises the element.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims. The above embodiments of the present application do not limit the scope of the present application.
Claims (9)
1. A method for encrypting a document, comprising:
receiving a document access request from a client;
verifying whether the document access request contains a token, wherein the token is sent to a client by a server according to login information of the client, the token comprises encrypted user identity information, and the user identity information corresponds to the login information;
if the document access request contains the token, checking whether the user identity information corresponding to the token has the access right of the document corresponding to the document access request;
if the user identity information corresponding to the token has the access authority of the document corresponding to the document access request, determining the watermark density according to the encryption level of the document, adding an encryption identifier corresponding to the user identity information in the document according to the watermark density, generating and sending an encrypted document to the client, wherein the encryption level is obtained according to data input by a document uploader when the document is uploaded by the client, and the higher the encryption level is, the higher the watermark density is.
2. The document encryption method according to claim 1, wherein the token includes a randomly generated character string, the character string being set to correspond to the user identification information.
3. The document encryption method according to claim 1, wherein the verifying whether the user identity information corresponding to the token has the access right of the document corresponding to the document access request further comprises:
checking whether the token is within a validity period.
4. The document encryption method according to claim 1, wherein the method further comprises: and if the document access request does not contain the token, or the token is not in the period of validity, or the user identity information corresponding to the token does not have the access right of the document in the document access request, generating and sending access forbidding information to the client.
5. A document access method, comprising:
receiving document access information input by a user, and generating a document access request according to the document access information and a token, wherein the token is sent to a client by a server according to login information of the client, the token comprises encrypted user identity information, and the user identity information corresponds to the login information;
sending the document access request to the server;
receiving an encrypted document from the server, wherein the server acquires the user identity information according to a token in the document access request, checks whether the user identity information has the access right of the document corresponding to the document access request, determines the watermark density according to the encryption level of the document if the user identity information has the access right of the document corresponding to the document access request, adds an encryption identifier corresponding to the user identity information in the document according to the watermark density, generates and sends the encrypted document to the client, wherein the encryption level is obtained according to data input by a document uploader when uploading the document on the client, and the higher the encryption level is, the higher the watermark density is.
6. The document access method of claim 5, the method further comprising:
and receiving access prohibition information from the server, wherein the server generates and sends the access prohibition information to the client according to the fact that the document access request does not contain the token, or the token is not in the validity period, or the user identity information corresponding to the token does not have the access right of the document in the document access request.
7. The document access method of claim 5, the method further comprising:
and displaying the encrypted document.
8. A server, wherein the server is configured to:
receiving a document access request from a client;
verifying whether the document access request contains a token, wherein the token is sent to a client by a server according to login information of the client, the token comprises encrypted user identity information, and the user identity information corresponds to the login information;
if the document access request contains the token, checking whether the user identity information corresponding to the token has the access right of the document corresponding to the document access request;
if the user identity information corresponding to the token has the access authority of the document corresponding to the document access request, determining the watermark density according to the encryption level of the document, adding an encryption identifier corresponding to the user identity information in the document according to the watermark density, generating and sending an encrypted document to the client, wherein the encryption level is obtained according to data input by a document uploader when the document is uploaded at the client, and the higher the encryption level is, the higher the watermark density is.
9. A document management system comprising a client and the server of claim 8, wherein the client is configured to:
receiving document access information input by a user, and generating a document access request according to the document access information and a token, wherein the token is sent to a client by a server according to login information of the client, the token comprises encrypted user identity information, and the user identity information corresponds to the login information;
sending the document access request to the server;
and receiving an encrypted document from the server, wherein the server acquires the user identity information according to a token in the document access request, verifies whether the user identity information has the access right of the document corresponding to the document access request, adds an encrypted identifier corresponding to the user identity information in the document corresponding to the document access request if the user identity information has the access right of the document corresponding to the document access request, and generates and sends the encrypted document to the client.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010451486.6A CN111625854B (en) | 2020-05-25 | 2020-05-25 | Document encryption method, access method, server and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010451486.6A CN111625854B (en) | 2020-05-25 | 2020-05-25 | Document encryption method, access method, server and system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN111625854A CN111625854A (en) | 2020-09-04 |
CN111625854B true CN111625854B (en) | 2022-10-14 |
Family
ID=72259090
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202010451486.6A Active CN111625854B (en) | 2020-05-25 | 2020-05-25 | Document encryption method, access method, server and system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN111625854B (en) |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112115448B (en) * | 2020-09-16 | 2022-11-18 | 安徽长泰科技有限公司 | Management system for intelligently encrypting and preventing document from being lost |
CN112165475B (en) * | 2020-09-22 | 2023-05-02 | 成都知道创宇信息技术有限公司 | Anticreeper method, anticreeper device, web server, and readable storage medium |
CN111931244B (en) * | 2020-10-13 | 2021-07-13 | 北京世纪好未来教育科技有限公司 | Method and device for preventing document from divulging, electronic equipment and storage medium |
CN112437078A (en) * | 2020-11-20 | 2021-03-02 | 腾讯科技(深圳)有限公司 | File storage method, device, equipment and computer readable storage medium |
CN112437079B (en) * | 2020-11-20 | 2023-04-07 | 中国人寿保险股份有限公司 | Intranet access method and device |
CN112231762A (en) * | 2020-12-15 | 2021-01-15 | 北京联想协同科技有限公司 | File access method, device and storage medium |
CN112612770A (en) * | 2020-12-28 | 2021-04-06 | 深圳市科创思科技有限公司 | Distributed file uploading method and system |
CN113536365B (en) * | 2021-06-07 | 2022-10-28 | 北京字跳网络技术有限公司 | File access method, device, equipment and medium |
CN114257441B (en) * | 2021-12-17 | 2023-12-15 | 北京字跳网络技术有限公司 | Data processing method and device based on cloud document component |
CN114257449A (en) * | 2021-12-20 | 2022-03-29 | 上海颜硕信息科技有限公司 | Data label tracing technology for Web layer |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1210315A (en) * | 1997-08-29 | 1999-03-10 | 富士通株式会社 | Device for generating, detecting, recording, and reproducing watermarked moving image having copy preventing capability and storage medium for storing program or moving image |
US6970259B1 (en) * | 2000-11-28 | 2005-11-29 | Xerox Corporation | Systems and methods for forgery detection and deterrence of printed documents |
US7269734B1 (en) * | 1997-02-20 | 2007-09-11 | Digimarc Corporation | Invisible digital watermarks |
CN101043319A (en) * | 2006-03-22 | 2007-09-26 | 鸿富锦精密工业(深圳)有限公司 | Digital content protective system and method |
CN102867155A (en) * | 2012-08-22 | 2013-01-09 | 句容市盛世软件有限公司 | Multiple-encryption and graded-management method for electronic files |
CN105359514A (en) * | 2013-07-01 | 2016-02-24 | 三星电子株式会社 | Method and device for authorizing video contents during video call |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR100971103B1 (en) * | 2003-05-28 | 2010-07-20 | 가부시키가이샤 오끼 데이타 | Watermark information embedding device, image processing device, watermark information embedding method, and image processing method |
CN102685086A (en) * | 2011-04-14 | 2012-09-19 | 天脉聚源(北京)传媒科技有限公司 | File access method and system |
CN103166783A (en) * | 2011-12-14 | 2013-06-19 | 华为技术有限公司 | Resource control method and resource control device |
EP3333812B1 (en) * | 2013-12-03 | 2020-02-19 | Crane & Co., Inc. | A security sheet or document having one or more enhanced watermarks |
CN104866735B (en) * | 2015-05-22 | 2017-11-17 | 电子科技大学 | A kind of insertion of numeric type relational database watermark and extraction verification method |
CN108345774A (en) * | 2018-01-26 | 2018-07-31 | 四川中环法智互联网科技有限公司 | A kind of transfer approach and transfer management system of secure content |
CN110531911B (en) * | 2019-07-22 | 2022-05-27 | 平安科技(深圳)有限公司 | Screen capture information control method and device, computer equipment and storage medium |
CN110691087B (en) * | 2019-09-29 | 2022-03-01 | 北京搜狐新媒体信息技术有限公司 | Access control method, device, server and storage medium |
CN110941845A (en) * | 2019-12-13 | 2020-03-31 | 北京锐安科技有限公司 | File acquisition method and device, computer equipment and storage medium |
-
2020
- 2020-05-25 CN CN202010451486.6A patent/CN111625854B/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7269734B1 (en) * | 1997-02-20 | 2007-09-11 | Digimarc Corporation | Invisible digital watermarks |
CN1210315A (en) * | 1997-08-29 | 1999-03-10 | 富士通株式会社 | Device for generating, detecting, recording, and reproducing watermarked moving image having copy preventing capability and storage medium for storing program or moving image |
US6970259B1 (en) * | 2000-11-28 | 2005-11-29 | Xerox Corporation | Systems and methods for forgery detection and deterrence of printed documents |
CN101043319A (en) * | 2006-03-22 | 2007-09-26 | 鸿富锦精密工业(深圳)有限公司 | Digital content protective system and method |
CN102867155A (en) * | 2012-08-22 | 2013-01-09 | 句容市盛世软件有限公司 | Multiple-encryption and graded-management method for electronic files |
CN105359514A (en) * | 2013-07-01 | 2016-02-24 | 三星电子株式会社 | Method and device for authorizing video contents during video call |
Non-Patent Citations (1)
Title |
---|
一种基于可变步长量化调制的地理数据库水印方法;汪传建等;《计算机研究与发展》;20111015(第10期);全文 * |
Also Published As
Publication number | Publication date |
---|---|
CN111625854A (en) | 2020-09-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN111625854B (en) | Document encryption method, access method, server and system | |
US10484385B2 (en) | Accessing an application through application clients and web browsers | |
US20100100967A1 (en) | Secure collaborative environment | |
US8239954B2 (en) | Access control based on program properties | |
CN111355726B (en) | Identity authorization login method and device, electronic equipment and storage medium | |
US20060200424A1 (en) | Method and system for integrating multiple identities, identity mechanisms and identity providers in a single user paradigm | |
CN108289098B (en) | Authority management method and device of distributed file system, server and medium | |
US9875372B2 (en) | Redacting restricted content in files | |
KR20090103670A (en) | Method and appratus for handiling security of a device on network | |
US11791990B2 (en) | Apparatus and method for managing personal information | |
JP2017033339A (en) | Service provision system, information processing device, program and service use information creation method | |
US20140150055A1 (en) | Data reference system and application authentication method | |
CN110417820A (en) | Processing method, device and the readable storage medium storing program for executing of single-node login system | |
US11244040B2 (en) | Enforcement of password uniqueness | |
US10650153B2 (en) | Electronic document access validation | |
CN109040024A (en) | A kind of resource access right control method and system | |
CN112804258A (en) | Authentication and authorization method, authorization server, API gateway, system and storage medium | |
JP2017097542A (en) | Authentication control program, authentication control device, and authentication control method | |
CN111818088A (en) | Authorization mode management method and device, computer equipment and readable storage medium | |
CN111541546A (en) | Multi-platform login method, device, equipment and readable medium | |
CN101547202A (en) | Method for processing security level of device on the net | |
CN107645474B (en) | Method and device for logging in open platform | |
US20180039771A1 (en) | Method of and server for authorizing execution of an application on an electronic device | |
US20020166066A1 (en) | Method of restricting viewing web page and server | |
CN114297598B (en) | User permission processing method and device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |