CN108076015B

CN108076015B - Authority information processing method and device

Info

Publication number: CN108076015B
Application number: CN201611005511.8A
Authority: CN
Inventors: 阮华; 何瑞; 曾凡; 万志颖; 李家昌; 史晓茸
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2016-11-15
Filing date: 2016-11-15
Publication date: 2020-07-07
Anticipated expiration: 2036-11-15
Also published as: CN108076015A

Abstract

The invention discloses a method and a device for processing authority information. Wherein, the method comprises the following steps: receiving a query request of a first account, wherein the query request is used for requesting to query authority information of a second account; responding to the query request, querying authority information of the second account, wherein the authority information is used for representing authority which the second account is allowed to have; and sending a result page recorded with the permission information to the first account, wherein the permission information recorded in the result page is allowed to be edited. The invention solves the technical problem of complicated operation for editing the user permission.

Description

Authority information processing method and device

Technical Field

The present invention relates to the field of information processing, and in particular, to a method and an apparatus for processing permission information.

Background

Permissions refer to the extent and degree to which an actor must make a decision on an event in order to ensure effective performance of a role, and in the management of a multi-user computer system, a permission may refer to a particular user having particular system resource usage rights. The administrator generally refers to an actual person or account responsible for maintenance or management update of a certain system or software, and a network administrator in the network assigns different permissions to users for the use of a certain resource.

In the prior art, the authority of a specific system or account is generally displayed by a list, a search result obtained by searching for the related authority of a certain user by an administrator is also displayed by the list, and the administrator can select one or more authorities from the list to delete.

In the above scheme, when editing the user right, an administrator can enter the query interface through query to delete the user right in the query result display page, but if the administrator wants to increase the user right, the administrator needs to exit the query result display page and enter an addition page with a certain right, and selects an account to be added in the addition page to add the account right.

Aiming at the problem of complicated operation for editing the user permission, an effective solution is not provided at present.

Disclosure of Invention

The embodiment of the invention provides a method and a device for processing authority information, which are used for at least solving the technical problem of complicated operation of editing user authority.

According to an aspect of the embodiments of the present invention, there is provided a method for processing rights information, including: receiving a query request of a first account, wherein the query request is used for requesting to query authority information of a second account; responding to the query request, querying authority information of the second account, wherein the authority information is used for representing authority which the second account is allowed to have; and sending a result page recorded with the permission information to the first account, wherein the permission information recorded in the result page is allowed to be edited.

According to another aspect of the embodiments of the present invention, there is provided a method for processing permission information, which is applied to a terminal, where a first account is logged in the terminal, and the method includes: the first account sends a query request to a server, wherein the query request is used for requesting to acquire authority information of a second account; receiving a result page recorded with the permission information of the second account, wherein the server responds to the query request to acquire the permission information, the permission information is used for representing permission possessed by the second account, and the permission information recorded in the result page is allowed to be edited; and displaying the result page.

According to an aspect of the embodiments of the present invention, there is provided a processing apparatus of authority information, including: the system comprises a receiving unit, a sending unit and a processing unit, wherein the receiving unit is used for receiving a query request of a first account, and the query request is used for requesting to query authority information of a second account; the query unit is used for responding to the query request and querying the authority information of the second account, wherein the authority information is used for expressing the authority which the second account is allowed to have; and the sending unit is used for sending a result page recorded with the permission information to the first account, wherein the permission information recorded in the result page is allowed to be edited.

According to another aspect of the embodiments of the present invention, there is provided a device for processing permission information, which is applied to a terminal, where a first account is logged in the terminal, and the device includes: the system comprises a first sending unit, a second sending unit and a server, wherein the first sending unit is used for sending a query request to the server, and the query request is used for requesting to acquire the authority information of a second account; a first receiving unit, configured to receive a result page recorded with permission information of the second account, where the server obtains the permission information in response to the query request, the permission information is used to indicate a permission that the second account is allowed to have, and the permission information recorded in the result page is allowed to be edited; and the display unit is used for displaying the result page.

In the embodiment of the invention, after a query request of a first account is received, permission information of a second account requesting query is acquired in response to the query request, the permission information is used for representing permission possessed by the second account, a result page recorded with the permission information of the second account is returned to the first account, and the result page is displayed on a terminal screen logged in by the first account. In the embodiment, according to the query request of the first account, the authority information which the second account is allowed to have is obtained by querying, not only the information which the second account already has, but also the authority which the second account is allowed to have is recorded in the result page and can be edited, so that when the user authority is edited, an interface of the query result does not need to be quitted, the page of the query result can be directly edited, the operation is simple, the problem that the operation for editing the user authority in the prior art is complex is solved, and the effect of quickly editing the authority of the user is realized.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

fig. 1 is a schematic diagram of a hardware environment of a processing method of rights information according to an embodiment of the present invention;

FIG. 2 is a first flowchart of an alternative method for processing rights information according to an embodiment of the present invention;

FIG. 3 is a flowchart II of an alternative method for processing rights information according to an embodiment of the present invention;

FIG. 4 is a flowchart III of an alternative method for processing rights information according to an embodiment of the present invention;

FIG. 5 is a flow chart diagram of an alternative method for processing rights information according to an embodiment of the present invention;

FIG. 6 is a flow chart diagram of an alternative method for processing rights information according to an embodiment of the present invention;

FIG. 7 is an interface diagram of a query page of an alternative method of processing rights information according to an embodiment of the invention;

fig. 8 is an edit right interface diagram of an alternative method of processing right information according to an embodiment of the present invention;

FIG. 9 is a first schematic diagram of an alternative apparatus for processing rights information according to an embodiment of the present invention;

FIG. 10 is a second diagram of an alternative apparatus for processing rights information according to an embodiment of the present invention; and

fig. 11 is a block diagram of a structure of a first account according to an embodiment of the present invention.

Detailed Description

In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

First, partial terms or terms appearing in the description of the embodiments of the present invention are applied to the following explanations:

permissions refer to the extent and degree to which an actor must make a decision on an event in order to ensure effective performance of a role, and in the management of a multi-user computer system, a permission may refer to a particular user having particular system resource usage rights.

An administrator generally refers to an actual person or account that is responsible for the maintenance or management of certain systems or software updates, and a network administrator in a network assigns different permissions to users for the use of certain resources.

According to an embodiment of the present invention, an embodiment of a method for processing rights information is provided. Alternatively, in the present embodiment, the processing method of the authority information may be applied to a hardware environment formed by the server 102 and the terminal 104 as shown in fig. 1. As shown in fig. 1, a server 102 is connected to a terminal 104 via a network including, but not limited to: the terminal 104 is not limited to a PC, a mobile phone, a tablet computer, etc. in a wide area network, a metropolitan area network, or a local area network. The method for processing the authority information according to the embodiment of the present invention may be executed by the server 102, the terminal 104, or both the server 102 and the terminal 104. The method for processing the authority information by the terminal 104 according to the embodiment of the present invention may be executed by a client installed thereon.

Alternatively, the number of the servers in this embodiment may be one or more. In this embodiment, a web server and a processing server may be deployed on the server, and optionally, the web server (i.e., a web server) may be a program deployed on a computer, and may also be a server that can independently run a web service, and the processing server may be a program deployed on a computer, and may also be a server that independently runs a processing service.

Further optionally, the web server and the processing server are different services deployed on the same computer, or may be processes residing on the same machine.

Alternatively, the web server may provide a document, such as a web page, to a web client, such as a browser; the web server may also place website files or data files. The web server may be an Apache server, a Nginx server, or an IIS server.

In an alternative embodiment, the web server, after receiving a request sent by a web client, processes the request through a processing service and feeds back a file to the web client.

According to an embodiment of a processing method for optional permission information provided by the present invention, the embodiment may be applied to a server, fig. 2 is a first flowchart of the processing method for optional permission information according to the embodiment of the present invention, and as shown in fig. 2, the method may include the following steps:

step S202: receiving a query request of a first account, wherein the query request is used for requesting to query authority information of a second account;

step S204: responding to the query request, and querying authority information of the second account, wherein the authority information is used for representing authority which the second account is allowed to have;

step S206: and returning the result page recorded with the permission information to the first account, wherein the permission information recorded in the result page is allowed to be edited.

Through the embodiment, after the query request of the first account is received, the permission information of the second account requesting the query is obtained in response to the query request, the permission information is used for representing permission possessed by the second account, the result page recorded with the permission information of the second account is returned to the first account, and the result page is displayed on a terminal screen logged by the first account. In the embodiment, according to the query request of the first account, the authority information which the second account is allowed to have is obtained by querying, not only the information which the second account already has, but also the authority which the second account is allowed to have is recorded in the result page and can be edited, so that when the user authority is edited, an interface of the query result does not need to be quitted, the page of the query result can be directly edited, the operation is simple, the problem that the operation for editing the user authority in the prior art is complex is solved, and the effect of quickly editing the authority of the user is realized.

In the technical solution of step S202, the web server may provide a query page for inputting a query request by the first account, and the web server receives the query request by the first account through the query page.

The query page provided by the web server may record a query input box, and the query input box may be used to input query keywords, such as an account number to be queried and authority information (e.g., an authority name).

In an optional embodiment, the query webpage is further provided with a query determination key (or button) corresponding to the query input box, the query determination key is executed with a predetermined operation to generate a query determination instruction, and after receiving the query determination instruction, the terminal generates a query request corresponding to the input query keyword in response to the query determination instruction. Wherein, the predetermined operation may be a click operation.

For example, after entering a query page, a user inputs an account to be queried in a query input box, clicks a query determination key, receives the account to be queried, determines to receive a query determination instruction after receiving an operation event that the query determination key is clicked (or pressed), generates a query request corresponding to the account to be queried in response to the query determination instruction, and sends the query request to a server.

In another alternative embodiment, the user may generate the query determination command by operating a predetermined key (or a combination of keys), for example, pressing an enter key (i.e., enter key) to generate the query determination command.

The input mode of the query determination instruction is not specifically limited, and the input modes according with the inventive concept of the present application all belong to the protection scope of the present application.

In another optional embodiment, the query page may be a page with a query function, the query page may further record permissions of multiple services, and the query page may further record authorized account summary information with permissions, such as: the account numbers A, B and C have editing rights, and the authorized account number summary information may be recorded by the name of the account number, or may be recorded by the head portrait or nickname of the account number, which is not limited in this application.

The first account in the above embodiment may be an administrator account, and an administrator may log in the account on the terminal, enter a query page (such as a rights management page) after logging in using the administrator account, input an account name of the second account (or other related information of the second account) through the query page, click a query determination key, generate a query request, and send the query request to the server.

Alternatively, the user may log in through the html5 page or client.

Further optionally, the second account may be an account that does not have any authority, an account that already has all authorities of the corresponding service, or an account that already has partial authorities of the corresponding service, which is not limited in this application.

In the technical solution of step S204, after receiving the query request through a page (e.g., a query page), the web server sends the query request to a processing server (the processing server may be a process resident on a machine where the web server is located), and the processing server responds to the query request to query the database for the permission information of the second account requested to be queried. Alternatively, the query operation may be implemented by using the account name of the second account as a keyword, and performing a search in the database using the keyword.

Optionally, the permission information is used to indicate a permission that the second account is allowed to have, where the permission that the second account is allowed to have may be a preset permission that the second account can have, and the permission may be all or part of a permission of a corresponding service. In this embodiment, there is no limitation on whether the second account already has the permission that allows it.

Optionally, the permission information may include a name of a permission that the second account is allowed to have, for example, the permission information may be: "permission that the second account is allowed to have is: authority A, Authority B and Authority C'.

Further optionally, the authority information may further include: the status information of whether each permission that the second account has is already possessed by the second account number may optionally use different values to identify different statuses, such as 1 for an possessed status and 0 for an unavailable status. For example, the authority information may be: "permission that the second account is allowed to have is: authority a (1), authority B (1), and authority C (0) ", that is, the second account already has authority a and authority B, and does not yet have authority C.

In the technical solution of step S206, after the processing server obtains the authority information (i.e., the query result corresponding to the query request), the result page generated by the web server based on the authority information is returned to the first account, and after the first account receives the returned result page, the terminal logged in by the first account displays the received result page on the corresponding screen.

The permission information recorded in the result page is allowed to be edited, where the editing refers to an operation that can change the permission that the second account already has, for example, increase the permission that the second account already has, or decrease the permission that the second account already has.

According to the embodiment of the application, the authority information of the second account includes: the account management system comprises first information and second information, wherein the first information is used for representing one or more first authorities which the second account already has, and the second information is used for representing one or more second authorities which the second account is allowed to have and which the second account does not yet have.

Optionally, the permission that the second account is allowed to have may be all or part of the permission in the service to which the second account belongs, for example, if the second account is an administrator account, the permission that the second account is allowed to have may be all permissions of the service, where the all permissions include a query permission and an editing permission, the query permission may be a permission to query the permissions of other accounts, and the editing permission may be a permission to change the permissions of other accounts. If the second account is a common account, the permission allowed by the second account may be a partial permission of the service, and if the second account is not allowed to have the query permission and the editing permission.

In this embodiment, the permission that the second account is allowed to have includes: the permission that the second account is allowed to have and the second account already has, and the permission that the second account is allowed to have and the second account not already has.

Optionally, the first information and the second information may use names of permissions to represent corresponding permissions, for example, the first information of the second account is: permission A, permission B and permission C, wherein the second information of the second account is as follows: permission S, permission F, and permission D. Alternatively, this information may be presented in the form of a list, as shown in table 1:

TABLE 1

First information	Second information
		Authority 1	Authority 2
Authority 3	Authority 7
		Authority 4	Authority 8
Authority 5	——
		Authority 6	——

As can be seen from table 1, the second account already has the following rights: privilege 1, privilege 3, privilege 4, privilege 5, and privilege 6; the second account has no authority: privilege 2, privilege 7, and privilege 8.

In another optional embodiment, the permission information of the second account may also indicate a permission that the second account is not allowed to have, and the permission that the second account is not allowed to have may exist in a different expression form from the permission that the second account is allowed to have, for example, the permission that the second account is allowed to have and the permission that the second account is not allowed to have may be expressed by different fonts, colors, and grays.

Optionally, the permission that allows the second account to have the first permission that the second account already has and the first permission that the second account does not yet have may also be expressed using different expression forms, for example, using different fonts, colors, grays or other identifiers to distinguish the first permission from the second permission.

Further, the first information and the second information may also use other expressions to represent corresponding rights, which is not limited in this application.

In the technical solution of step S204, querying the permission information of the second account may be implemented by the example shown in fig. 3, and as shown in fig. 3, the embodiment may include the following steps:

step S302: and checking whether the first account has the inquiry authority.

The processing server may query whether the first account has a query right from a right table of the database, where the query right is a right to query right information of other accounts, and specifically in the embodiment of the present application, the query right may be a right to query right information of a second account.

If the first account number is detected to have the query authority, executing step S306; if it is detected that the second account does not have the query authority, step S304 is executed.

Step S304: and returning error information.

And the webpage server returns error information to the first account, wherein the error information is used for prompting that the first account does not have the inquiry authority. The terminal logged in by the first account may display the error information on a screen of the terminal after receiving the error information, and optionally, the error information is displayed in the form of a floating frame on the screen of the terminal.

Step S306: and inquiring the authority information of the second account.

Optionally, the first authority and the second authority of the first account are queried from a database to obtain authority information.

After the webpage server sends a result page recorded with the authority information of the second account to the first account, the terminal logged by the first account displays the information on a screen, and the first information and the second information in the result page can be displayed in different areas.

Alternatively, the plurality of rights indicated by the rights information are allowed to simultaneously perform editing operations including a deletion operation and an addition operation.

The deleting operation is used for deleting part or all of the first permissions possessed by the second account, and the adding operation is used for adding part or all of the second permissions which are allowed to be possessed by the second account and not possessed by the second account.

In this embodiment, the same time may refer to that multiple operations may be performed together in one editing operation, or that multiple operations are performed in the same page, so that the permissions of the second account are edited in batch in one result page.

The result page may perform the delete operation by receiving a delete instruction or may perform the add operation by receiving an add instruction.

Specifically, an input box of a delete or add instruction is recorded on the result page, a user of the first account can input the add instruction or delete instruction through the input box, a determined edit key is also recorded on the result page, after the determined edit key is detected to be pressed, the web server sends the delete instruction and/or the add instruction to the processing server, and the processing server executes corresponding add and/or delete operations.

In an optional embodiment, a selection box is arranged on the displayed result page corresponding to each authority (including the first authority and the second authority), and the selection box can be selected, and the selection box arranged on the result page is a check box, that is, the selection box is a control which can be simultaneously selected, and a user can input a corresponding instruction by selecting the selection box.

If the authority corresponding to the selection box is the first authority, the selected operation of the selection box corresponds to a deleting instruction; and if the authority corresponding to the selection box is the second authority, the operation selected by the selection box corresponds to the adding instruction.

For example, on the displayed result page, one or more deletion instructions and/or one or more addition instructions can be input in batch, and the edit-determining button is clicked, the web server sends the instructions to the processing server, and the processing server executes corresponding addition or deletion operations.

In an optional embodiment, after sending the result page recorded with the permission information to the first account, the method further includes the following steps shown in fig. 4:

step S402: and inputting an editing instruction on a result page displayed by the terminal logged in by the first account.

Alternatively, the results page may be displayed in a browser of the terminal. The editing instructions may report deletion instructions and/or addition instructions.

Step S404: and the webpage server receives an editing instruction sent by the first account.

The editing instruction is used for deleting part or all of the first permissions possessed by the second account, and/or adding part or all of second permissions which are allowed to be possessed by the second account and not possessed by the second account;

step S406: and the system background checks whether the first account has the editing authority.

The editing authority is the authority of editing indicated by the editing instruction, and the operation is used for detecting whether the first account has the authority of deleting and/or adding the second account.

If the first account is verified not to have the editing authority, executing step S408; if the first account is verified to have the editing right, step S410 is executed.

Step S408: and returning error information, wherein the error information is used for indicating that the first account does not have the editing authority.

Step S410: and executing the operation indicated by the editing instruction.

Optionally, the adding and/or deleting operation indicated by the editing instruction is performed to change the permission of the second account, for example, all or part of the first permissions possessed by the second account are deleted, and all or part of the second permissions not possessed by the second account are added as the permissions possessed by the second account.

Step S412: and saving the execution result.

Optionally, the rights of the changed second account are saved in a database.

The application also provides a method for processing the authority information, which is applied to a terminal, wherein a first account is logged on the terminal, and the method can include the following steps as shown in fig. 5:

step S502: sending a query request to a server, wherein the query request is used for requesting to acquire the authority information of the second account;

step S504: receiving a result page recorded with the permission information of the second account, wherein the server responds to the query request to acquire the permission information, the permission information is used for representing permission possessed by the second account, and the permission information recorded in the result page is allowed to be edited;

step S506: and displaying a result page. Optionally, the result page is presented in a browser of the terminal.

Through the embodiment, after the query request of the first account is received, the permission information of the second account requesting the query is obtained in response to the query request, the permission information is used for representing permission possessed by the second account, the result page recorded with the permission information of the second account is returned to the first account, and the result page is displayed on a terminal screen logged by the first account. In the embodiment, according to the query request of the first account, the authority information which the second account is allowed to have is obtained by querying, not only the information which the second account already has, but also the authority which the second account is allowed to have recorded in the result page can be edited, so that when the user authority is edited, an interface of the query result does not need to be quitted, the page of the query result can be directly edited, the operation is simple, and the problem that the operation of editing the user authority in the prior art is complicated is solved.

In an optional embodiment, the permission information of the second account includes: the account management system comprises first information and second information, wherein the first information is used for representing one or more first authorities which the second account already has, and the second information is used for representing one or more second authorities which the second account is allowed to have and which the second account does not yet have.

After the terminal logged in with the first account receives the authority information, a result page is displayed on a screen of the terminal, a selection frame is arranged in the result page corresponding to information (such as authority names) of each authority, the selection frame can be selected, an editing instruction can be input by performing selection operation on the selection frame, wherein if the selection frame of the first authority is selected, a deleting instruction is input, and if the selection frame of the second authority is selected, an adding instruction is input.

Alternatively, the selection box is a check box, that is, an edit instruction can be input to a plurality of rights (including the first right and the second right) at a time.

After presenting the results page, the method further comprises: receiving an input editing instruction through a selection box, wherein the editing instruction is used for deleting part or all of first permissions possessed by the second account, and/or adding part or all of second permissions which are allowed to be possessed by the second account and not possessed by the second account; and sending an editing instruction to the server so as to change one or more first permissions possessed by the second account into one or more third permissions.

Optionally, after the editing instruction is sent to the server, if the server executes the operation indicated by the editing instruction, returning an editing result, and the terminal receives the editing result and displays the editing result on a screen of the terminal; and if the server verifies that the first account does not have the editing authority, the operation indicated by the editing instruction is not executed, and error information is returned, wherein the error information is used for prompting that the first account does not have the editing authority.

In an optional embodiment, before the first account sends the query request to the server, the method may further include: receiving an input second account through a query input box of a query page; receiving a query determination instruction input through a query page; and responding to the query determination instruction, and generating a query request corresponding to the second account.

The query determination instruction may be input through a key or a combination of keys, and if it is detected that the enter key is pressed, the query determination instruction that is input is determined to be detected.

An alternative embodiment of the present application is described in detail below with reference to fig. 6-8.

As shown in fig. 6, this embodiment may include the steps of:

step S601: the administrator enters the account name of the second account on the query page.

The administrator enters the account name of the second account in the search box (e.g., a username, which may be a person who now has no privileges or a user who already has some or all privileges).

Optionally, after logging in the administrator account (i.e., the first account in the above embodiment), the administrator enters a query page, where the query page may be a rights management page shown in fig. 7, as shown in fig. 7, the rights management page may show a foreground right and a background right, where the foreground right may include: as shown in fig. 7, which accounts (optionally, information of the accounts represented by the avatar) have foreground permissions can also be shown in the page.

Step S602: click the search button.

Optionally, the user clicks a search key (or confirms through an enter shortcut) in the query page shown in fig. 7, generates a query request, and sends the query request to a system background (such as the processing server described above) through the web server to process the query request.

Step S603: it is checked whether the originator of the query request has the query right.

If yes, go to step S604; if not, go to step S611: and returning error information, wherein if the initiator (namely the first account) is detected to have no inquiry authority, the error information prompts that the initiator has no inquiry authority.

Step S604: and inquiring to obtain the authority information of the second account.

Optionally, after receiving the request for querying the permission, the system background verifies the authority of the administrator of the submitter, verifies the validity of the user, queries the current permission of the user and the permission list which the user can apply for and does not have, and returns the current permission and the permission list to the browser foreground.

Step S605: and displaying the authority information of the second account on the terminal where the administrator is located.

The permission information includes first information and second information, where the first information indicates the permission that the second account has, such as the existing permission in the result page shown by the terminal shown in fig. 8; the second information indicates permissions that the second account is allowed to have and that the second account does not yet have, as shown by the added permissions in the results page shown in fig. 8.

Optionally, an input box for querying information and a query confirmation key may also be set on the result page, and the user may also directly query the authority through the page.

As shown in fig. 8, the first information and the second information may be displayed in different areas, and optionally, the first information and the second information may be displayed in a result page according to a layout manner different from that shown in fig. 8, which is not limited in this application.

Step S606: editing the permissions of the second account.

Alternatively, by displaying a result page (which may also be referred to as a permission page), the user can quickly add and/or delete permissions, and after inputting an editing instruction, click to confirm the completion of the batch modification operation, as shown in fig. 8, a check box may be set in the page, and the user can edit the permissions of the second account through the check box.

Step S607: and checking whether the user sending the editing instruction has the editing authority.

If yes, go to step S608; if not, go to step S611.

Step S608: and saving the edited right.

Step S609: and returning a storage result.

Step S610: and displaying the storage result on the browser foreground.

Step S611: and returning error information.

If it is detected that the initiator (i.e., the first account) of the query request does not have the query right, the error message prompts that the initiator does not have the query right.

In another example, if it is detected that the sender of the editing instruction (i.e., the first account) has no editing right, the error message indicates that the initiator has no editing right.

Step S612: and displaying error information.

Through the embodiment, each authority of each account can be effectively and quickly managed, and an administrator can quickly confirm the authority owned by a certain user and quickly add and delete the authority to a certain person by searching the user authority.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.

Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk), and includes instructions for enabling a first account device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.

According to the embodiment of the invention, the processing device for implementing the processing method of the authority information is also provided. Fig. 9 is a schematic diagram of an alternative apparatus for processing rights information according to an embodiment of the present invention, and as shown in fig. 9, the apparatus may include:

a receiving unit 91, configured to receive an inquiry request of a first account, where the inquiry request is used to request to inquire authority information of a second account;

the querying unit 93 is configured to query, in response to the query request, authority information of the second account, where the authority information is used to indicate an authority that the second account is allowed to have;

a sending unit 95, configured to send a result page recorded with the permission information to the first account, where the permission information recorded in the result page is allowed to be edited.

Wherein, the authority information of the second account includes: the account management system comprises first information and second information, wherein the first information is used for representing one or more first authorities which the second account already has, and the second information is used for representing one or more second authorities which the second account is allowed to have and which the second account does not yet have.

Alternatively, the authority information is information representing a plurality of authorities that are allowed to simultaneously perform editing operations including a deletion operation and an addition operation.

In an alternative embodiment, the first information is recorded in a first area of the results page and the second information is recorded in a second area of the results page.

According to the above embodiment of the present application, the query unit is specifically configured to: and under the condition that the first account is verified to have the inquiry authority, inquiring the authority information of the second account, wherein the inquiry authority is the authority for inquiring the authority information of the second account.

Optionally, the receiving unit is further configured to receive an editing instruction sent by the first account after the result page recorded with the permission information is sent to the first account, where the editing instruction is used to delete part or all of the first permissions possessed by the second account, and/or add part or all of the second permissions which are allowed to be possessed by the second account and which are not possessed by the second account.

The device also includes: and the execution unit is used for responding to the editing instruction and performing addition operation and/or deletion operation on the authority of the second account under the condition that the first account is verified to have the editing authority, wherein the editing authority is the authority of the editing authority indicated by the editing instruction.

According to the embodiment of the invention, the processing device for implementing the processing method of the authority information is also provided. Fig. 10 is a schematic diagram of an optional apparatus for processing permission information according to an embodiment of the present invention, and as shown in fig. 10, the apparatus is applied to a terminal, on which a first account is registered, and the apparatus may include:

a first sending unit 1001, configured to send a query request to a server, where the query request is used to request to acquire permission information of a second account;

a first receiving unit 1003, configured to receive a result page recorded with permission information of the second account, where the server acquires the permission information in response to the query request, the permission information is used to indicate permission that the second account is allowed to have, and the permission information recorded in the result page is allowed to be edited;

a display unit 1005, configured to display the result page.

Alternatively, the authority information is information representing a plurality of authorities that are allowed to simultaneously perform editing operations including an addition operation and a deletion operation.

In an optional embodiment, the apparatus may further comprise: the second receiving unit is used for receiving an input editing instruction after the result page is displayed, wherein the editing instruction is used for deleting part or all of the first permissions possessed by the second account and/or adding part or all of the second permissions which are allowed to be possessed by the second account and not possessed by the second account; and the second sending unit is used for sending an editing instruction to the server so as to change one or more first authorities of the second account into one or more third authorities.

And a selection frame corresponding to the authority in a one-to-one mode is recorded in the result page, and the second receiving unit is used for receiving the editing instruction through the selection frame.

In another optional embodiment, the receiving unit is further configured to receive, before the first account sends the query request to the server, the input second account through a query input box of the query page; receiving a query determination instruction input through a query page; the device still includes: and the generating unit is used for responding to the query determining instruction and generating a query request corresponding to the second account.

It should be noted here that the modules described above are the same as the examples and application scenarios implemented by the corresponding steps, but are not limited to the disclosure of the above embodiments. It should be noted that the modules described above as a part of the apparatus may operate in a hardware environment as shown in fig. 1, and may be implemented by software or hardware.

According to the embodiment of the invention, the server or the terminal for implementing the processing method of the authority information is also provided.

Fig. 11 is a block diagram of a terminal according to an embodiment of the present invention, and as shown in fig. 11, the terminal may include: one or more processors 201 (only one of which is shown), a memory 203, and a transmission device 205 (such as the transmission device in the above embodiment), as shown in fig. 11, the terminal may further include an input/output device 207.

The memory 203 may be used to store software programs and modules, such as program instructions/modules corresponding to the method and apparatus for processing authority information in the embodiment of the present invention, and the processor 201 executes various functional applications and data processing by running the software programs and modules stored in the memory 203, that is, implements the method for processing authority information. The memory 203 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 203 may further include memory located remotely from the processor 201, which may be connected to the terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device 205 is used for receiving or sending data via a network, and can also be used for data transmission between a processor and a memory. Examples of the network may include a wired network and a wireless network. In one example, the transmission device 205 includes a Network adapter (NIC) that can be connected to a router via a Network cable and other Network devices to communicate with the internet or a local area Network. In one example, the transmission device 205 is a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.

Wherein the memory 203 is specifically used for storing application programs.

The processor 201 may call the application stored in the memory 203 via the transmission means 205 to perform the following steps: receiving a query request of a first account, wherein the query request is used for requesting to query authority information of a second account; responding to the query request, and querying authority information of the second account, wherein the authority information is used for representing authority which the second account is allowed to have; and sending the result page recorded with the permission information to the first account, wherein the permission information recorded in the result page is allowed to be edited.

In yet another alternative, the first information is recorded in a first area of the results page and the second information is recorded in a second area of the results page.

The processor 201 is further configured to perform the following steps: and under the condition that the first account is verified to have the inquiry authority, inquiring the authority information of the second account, wherein the inquiry authority is the authority for inquiring the authority information of the second account.

The processor 201 is further configured to perform the following steps: after the result page recorded with the permission information is sent to the first account, receiving an editing instruction sent by the first account, wherein the editing instruction is used for deleting part or all of the first permissions possessed by the second account and/or adding part or all of the second permissions which are allowed to be possessed by the second account and not possessed by the second account; and under the condition that the first account is verified to have the editing authority, responding to an editing instruction, and performing addition operation and/or deletion operation on the authority of the second account, wherein the editing authority is the authority of the editing authority indicated by the editing instruction.

The processor 201 may call the application stored in the memory 203 via the transmission means 205 to perform the following steps: sending a query request to a server, wherein the query request is used for requesting to acquire the authority information of the second account; receiving a result page recorded with the permission information of the second account, wherein the server responds to the query request to acquire the permission information, the permission information is used for representing permission possessed by the second account, and the permission information recorded in the result page is allowed to be edited; and displaying a result page.

Wherein the authority information is information indicating a plurality of authorities which are allowed to simultaneously perform editing operations including an adding operation and a deleting operation.

The processor 201 is further configured to perform the following steps: after the result page is displayed, receiving an input editing instruction, wherein the editing instruction is used for deleting part or all of the first permissions possessed by the second account, and/or adding part or all of the second permissions which are allowed to be possessed by the second account and not possessed by the second account; and sending an editing instruction to the server so as to change one or more first permissions possessed by the second account into one or more third permissions.

The processor 201 is further configured to perform the following steps: and receiving an editing instruction through a selection frame, wherein the selection frames corresponding to the authorities in a one-to-one mode are recorded in the result page.

And recording first information in a first area of the result page and recording second information in a second area of the result page.

The processor 201 is further configured to perform the following steps: before the first account sends a query request to the server, receiving an input second account through a query input box of a query page; receiving a query determination instruction input through a query page; and responding to the query determination instruction, and generating a query request corresponding to the second account.

Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment is not described herein again.

It can be understood by those skilled in the art that the structure shown in fig. 11 is only an illustration, and the terminal may be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palm computer, and a Mobile Internet Device (MID), a PAD, etc. Fig. 11 is a diagram illustrating a structure of the electronic device. For example, the terminal may also include more or fewer components (e.g., network interfaces, display devices, etc.) than shown in FIG. 11, or have a different configuration than shown in FIG. 11.

Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by a program instructing hardware associated with the terminal device, where the program may be stored in a computer-readable storage medium, and the storage medium may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.

The embodiment of the invention also provides a storage medium. Alternatively, in this embodiment, the storage medium may be a program code for executing the processing method of the authority information.

Optionally, in this embodiment, the storage medium may be located on at least one of a plurality of network devices in a network shown in the above embodiment.

Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps:

S1，；

S2，；

S3，；

S4，。

optionally, the storage medium is further arranged to store program code for performing the steps of:

optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps: receiving a query request of a first account, wherein the query request is used for requesting to query authority information of a second account; responding to the query request, and querying authority information of the second account, wherein the authority information is used for representing authority which the second account is allowed to have; and sending the result page recorded with the permission information to the first account, wherein the permission information recorded in the result page is allowed to be edited.

Optionally, the storage medium is further arranged to store program code for performing the steps of: and under the condition that the first account is verified to have the inquiry authority, inquiring the authority information of the second account, wherein the inquiry authority is the authority for inquiring the authority information of the second account.

Optionally, the storage medium is further arranged to store program code for performing the steps of: after the result page recorded with the permission information is sent to the first account, receiving an editing instruction sent by the first account, wherein the editing instruction is used for deleting part or all of the first permissions possessed by the second account and/or adding part or all of the second permissions which are allowed to be possessed by the second account and not possessed by the second account; and under the condition that the first account is verified to have the editing authority, responding to an editing instruction, and performing addition operation and/or deletion operation on the authority of the second account, wherein the editing authority is the authority of the editing authority indicated by the editing instruction.

Optionally, the storage medium is further arranged to store program code for performing the steps of: sending a query request to a server, wherein the query request is used for requesting to acquire the authority information of the second account; receiving a result page recorded with the permission information of the second account, wherein the server responds to the query request to acquire the permission information, the permission information is used for representing permission possessed by the second account, and the permission information recorded in the result page is allowed to be edited; and displaying a result page.

Optionally, the storage medium is further arranged to store program code for performing the steps of: after the result page is displayed, receiving an input editing instruction, wherein the editing instruction is used for deleting part or all of the first permissions possessed by the second account, and/or adding part or all of the second permissions which are allowed to be possessed by the second account and not possessed by the second account; and sending an editing instruction to the server so as to change one or more first permissions possessed by the second account into one or more third permissions.

Optionally, the storage medium is further arranged to store program code for performing the steps of: and receiving an editing instruction through a selection frame, wherein the selection frames corresponding to the authorities in a one-to-one mode are recorded in the result page.

Optionally, the storage medium is further arranged to store program code for performing the steps of: before the first account sends a query request to the server, receiving an input second account through a query input box of a query page; receiving a query determination instruction input through a query page; and responding to the query determination instruction, and generating a query request corresponding to the second account.

Optionally, in this embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

The integrated unit in the above embodiments, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in the above computer-readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing one or more computer devices (which may be personal computers, servers, network devices, etc.) to execute all or part of the steps of the method according to the embodiments of the present invention.

In the above embodiments of the present invention, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the several embodiments provided in the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.

Claims

1. A method for processing authority information is characterized by comprising the following steps:

receiving a query request of a first account, wherein the query request is used for requesting to query authority information of a second account;

responding to the query request, querying authority information of the second account, wherein the authority information is used for representing authority allowed to the second account and status information of whether each authority allowed to the second account is already possessed by the second account, and the authority information of the second account comprises: the account management method comprises the following steps of first information and second information, wherein the first information is used for representing one or more first permissions which the second account already has, and the second information is used for representing one or more second permissions which the second account is allowed to have and which the second account does not yet have;

sending a result page recorded with the permission information to the first account to indicate a terminal logged in by the first account to display the received result page on a screen, wherein the permission information recorded in the result page is allowed to be edited, the first information and the second information in the result page are displayed in different areas, the first permission and the second permission are respectively provided with corresponding selection frames, and an editing instruction is input under the condition that the selection frames are selected, and the editing instruction comprises a deleting instruction and/or an adding instruction;

and receiving the editing instruction, and executing the operation indicated by the editing instruction.

2. The method according to claim 1, wherein the authority information is information indicating a plurality of authorities which are allowed to simultaneously perform editing operations including a deletion operation and an addition operation.

3. The method of claim 1, wherein the first information is recorded in a first area of the results page and the second information is recorded in a second area of the results page.

4. The method of claim 1, wherein querying the permission information of the second account comprises:

and inquiring the authority information of the second account under the condition that the first account is verified to have the inquiry authority, wherein the inquiry authority is the authority for inquiring the authority information of the second account.

5. The method according to claim 1, wherein after sending the result page recorded with the permission information to the first account, the method comprises:

receiving an editing instruction sent by the first account, wherein the editing instruction is used for deleting part or all of first permissions possessed by the second account and/or adding part or all of second permissions which are allowed to be possessed by the second account and not possessed by the second account;

and under the condition that the first account is verified to have the editing authority, responding to the editing instruction, and performing addition operation and/or deletion operation on the authority of the second account, wherein the editing authority is the authority for editing the editing authority indicated by the editing instruction.

6. A method for processing authority information is applied to a terminal, wherein a first account is logged in the terminal, and the method comprises the following steps:

the first account sends a query request to a server, wherein the query request is used for requesting to acquire authority information of a second account;

receiving a result page recorded with authority information of the second account, wherein the server acquires the authority information in response to the query request, the authority information is used for representing authority allowed to the second account and status information of whether each authority allowed to the second account is already possessed by the second account, the authority information recorded in the result page is allowed to be edited, and the authority information of the second account includes: the account management method comprises the following steps of first information and second information, wherein the first information is used for representing one or more first permissions which the second account already has, and the second information is used for representing one or more second permissions which the second account is allowed to have and which the second account does not yet have;

displaying the result page on a screen, wherein the first information and the second information in the result page are displayed in different areas, the first authority and the second authority are respectively provided with corresponding selection boxes, and an editing instruction is input under the condition that the selection boxes are selected, wherein the editing instruction comprises a deleting instruction and/or an adding instruction;

7. The method according to claim 6, wherein the authority information is information indicating a plurality of authorities which are allowed to simultaneously perform editing operations including the addition operation and the deletion operation.

8. The method of claim 6, wherein after presenting the results page, the method further comprises:

receiving an input editing instruction, wherein the editing instruction is used for deleting part or all of first permissions possessed by the second account, and/or adding part or all of second permissions which are allowed to be possessed by the second account and not possessed by the second account;

and sending the editing instruction to the server so as to change one or more first permissions possessed by the second account into one or more third permissions.

9. The method of claim 8, wherein selection boxes corresponding to the permissions in a one-to-one correspondence are recorded in the result page, and the method further comprises: and receiving the editing instruction through a selection box.

10. The method of claim 6, wherein the first information is recorded in a first area of the results page and the second information is recorded in a second area of the results page.

11. The method of claim 6, wherein before the first account sends the query request to the server, the method further comprises:

receiving an input second account through a query input box of a query page;

receiving a query determination instruction input through the query page;

and responding to the query determination instruction, and generating the query request corresponding to the second account.

12. An apparatus for processing rights information, comprising:

the system comprises a receiving unit, a sending unit and a processing unit, wherein the receiving unit is used for receiving a query request of a first account, and the query request is used for requesting to query authority information of a second account;

an inquiring unit, configured to inquire, in response to the inquiry request, authority information of the second account, where the authority information is used to indicate authorities that the second account is allowed to have and status information of whether each authority that the second account is allowed to have is already possessed by the second account, and the authority information of the second account includes: the account management method comprises the following steps of first information and second information, wherein the first information is used for representing one or more first permissions which the second account already has, and the second information is used for representing one or more second permissions which the second account is allowed to have and which the second account does not yet have;

a sending unit, configured to send a result page recorded with the permission information to the first account, so as to instruct a terminal logged in by the first account to display the received result page on a screen, where the permission information recorded in the result page is allowed to be edited, the first information and the second information in the result page are displayed in different areas, the first permission and the second permission respectively set corresponding selection frames, and an editing instruction is input when the selection frames are selected, where the editing instruction includes a deletion instruction and/or an addition instruction;

the device is also used for receiving the editing instruction and executing the operation indicated by the editing instruction.

13. The apparatus according to claim 12, wherein the authority information is information indicating a plurality of authorities which are allowed to simultaneously perform editing operations including a deletion operation and an addition operation.

14. The apparatus of claim 12, wherein the first information is recorded in a first area of the results page and the second information is recorded in a second area of the results page.

15. The apparatus according to claim 12, wherein the query unit is specifically configured to:

16. The apparatus of claim 12,

the receiving unit is further configured to receive an editing instruction sent by the first account after the result page recorded with the permission information is sent to the first account, where the editing instruction is used to delete part or all of the first permissions possessed by the second account, and/or add part or all of the second permissions which the second account is allowed to possess and which the second account does not yet possess;

the device also includes: and the execution unit is used for responding to the editing instruction and performing addition operation and/or deletion operation on the authority of the second account under the condition that the first account is verified to have the editing authority, wherein the editing authority is the authority for editing the authority indicated by the editing instruction.

17. A processing device of authority information is applied to a terminal, a first account is logged on the terminal, and the processing device comprises:

the system comprises a first sending unit, a second sending unit and a server, wherein the first sending unit is used for sending a query request to the server, and the query request is used for requesting to acquire the authority information of a second account;

a first receiving unit, configured to receive a result page recorded with permission information of the second account, where the server obtains the permission information in response to the query request, where the permission information is used to indicate permissions that the second account is allowed to have and status information of whether each permission that the second account is allowed to have is already possessed by the second account, and the permission information recorded in the result page is allowed to be edited, where the permission information of the second account includes: the account management method comprises the following steps of first information and second information, wherein the first information is used for representing one or more first permissions which the second account already has, and the second information is used for representing one or more second permissions which the second account is allowed to have and which the second account does not yet have;

the display unit is used for displaying the result page on a screen, wherein the first information and the second information in the result page are displayed in different areas, the first authority and the second authority are respectively provided with corresponding selection boxes, and an editing instruction is input under the condition that the selection boxes are selected, wherein the editing instruction comprises a deleting instruction and/or an adding instruction;

18. The apparatus according to claim 17, wherein the authority information is information indicating a plurality of authorities which are allowed to simultaneously perform editing operations including the addition operation and the deletion operation.

19. The apparatus of claim 17, further comprising:

a second receiving unit, configured to receive an input editing instruction after the result page is displayed, where the editing instruction is used to delete part or all of the first permissions that the second account already has, and/or add part or all of the second permissions that the second account is allowed to have and the second account does not yet have;

and the second sending unit is used for sending the editing instruction to the server so as to change one or more first permissions possessed by the second account into one or more third permissions.

20. The apparatus according to claim 19, wherein a selection box corresponding to the permissions in a one-to-one correspondence is recorded in the result page, and the second receiving unit is configured to receive the editing instruction through the selection box.

21. The apparatus of claim 17, wherein the first information is recorded in a first area of the results page and the second information is recorded in a second area of the results page.

22. The apparatus of claim 17,

the receiving unit is further configured to receive an input second account through a query input box of a query page before the first account sends a query request to the server; receiving a query determination instruction input through the query page;

the device further comprises: and the generating unit is used for responding to the query determining instruction and generating the query request corresponding to the second account.

23. A computer-readable storage medium comprising a stored program, wherein the program when executed performs the method of any of claims 1 to 5.

24. A computer-readable storage medium comprising a stored program, wherein the program when executed performs the method of any of claims 6 to 11.

25. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method of any of claims 1 to 5 by means of the computer program.

26. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method of any of claims 6 to 10 by means of the computer program.