WO2019062049A1 - Financial app permission configuration method, device and equipment, and storage medium - Google Patents
Financial app permission configuration method, device and equipment, and storage medium Download PDFInfo
- Publication number
- WO2019062049A1 WO2019062049A1 PCT/CN2018/080918 CN2018080918W WO2019062049A1 WO 2019062049 A1 WO2019062049 A1 WO 2019062049A1 CN 2018080918 W CN2018080918 W CN 2018080918W WO 2019062049 A1 WO2019062049 A1 WO 2019062049A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- role
- permission
- list
- level
- Prior art date
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/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/45—Structures or tools for the administration of authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
Definitions
- the corresponding access rights are executed according to the role list.
- the permission execution module 503 executes the corresponding access authority according to the role list after the user logs in at the client.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Storage Device Security (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The present application relates to the technical field of financial APP permission configuration, and provided thereby are a financial APP permission configuration method, device and equipment, and a storage medium, the financial APP permission configuration method comprising: popping up a permission configuration menu when a permission configuration instruction is received, the permission configuration menu comprising a role name configuration box, a permission range configuration box and a user data list, the user data list being formed according to user information stored in a database; associating a role name, a permission range and selected user information in the user data list, and generating a role list; and executing corresponding access permission according to the role list after a user logs into a client. The present application reduces the difficulty of access permission configuration and facilitates the updating of access permission along with updates in personnel changes by means of configuring a role to be connected to a user account and the access permission.
Description
本申请以2017年9月30日提交的申请号为201710918518.7，名称为“金融APP的权限设置方法、装置、设备及存储介质”的中国发明专利申请为基础，并要求其优先权。This application is based on the Chinese invention patent application filed on September 30, 2017, with the application number of 201710918518.7, entitled "Policy Setting Method, Device, Equipment and Storage Medium for Financial APP", and requires priority.
本申请涉及金融APP权限设置技术领域，尤其涉及一种金融APP的权限设置方法、装置、设备及存储介质。The present application relates to the technical field of financial APP permission setting, and in particular, to a method, device, device and storage medium for setting a right of a financial APP.
目前，现有技术中的权限设置方法都是根据用户的职位不同而设立角色，由于用户的职位过多，设计逻辑复杂，从而导致角色难以统一设计，增加了权限设计的难度，并且不利于人员的权限配置。另外企业的人员都存在一定的流动性，辞职、升职、新员工、不同部门员工的调动等人事调动，存在权限配置的更新跟不上人员流动的问题。At present, the prior art permission setting methods all set roles according to different positions of users. Due to too many user positions, the design logic is complicated, which makes the roles difficult to design uniformly, increases the difficulty of permission design, and is not conducive to personnel. Permission configuration. In addition, the personnel of the company have certain liquidity, resignation, promotion, new employees, transfer of employees in different departments, etc., and there is a problem that the renewal of authority configuration cannot keep up with the flow of personnel.
发明内容Summary of the invention
本申请的目的在于提供一种新型的基于角色的权限设计的方法、装置、设备及存储介质，方便为人员配置角色，便于完成人员的权限设置。The purpose of the present application is to provide a new method, device, device and storage medium for character-based authority design, which is convenient for configuring roles for personnel and facilitating permission setting of personnel.
本申请是这样实现的，本申请第一方面提供一种金融APP的设置方法，所述金融APP的设置方法包括：The application is implemented in this way. The first aspect of the present application provides a method for setting a financial APP, where the setting method of the financial APP includes:
当接收到权限设置指令时，弹出权限设置菜单，所述权限设置菜单包括角色名称设置框、权限范围设置框以及用户数据明细表，所述用户数据明细表根据数据库中存储的用户信息形成；When receiving the permission setting instruction, the permission setting menu is popped up, and the permission setting menu includes a role name setting box, a permission range setting box, and a user data list, and the user data list is formed according to the user information stored in the database;
将角色名称、权限范围以及所选定的用户数据明细表中的用户信息进行关联并生成角色明细表；Associating the role name, the scope of the permission, and the user information in the selected user data schedule to generate a role schedule;
当用户在客户端登录后，根据所述角色明细表执行对应的访问权限。After the user logs in to the client, the corresponding access rights are executed according to the role list.
本申请第二方面提供一种金融APP权限设置装置，所述金融APP的权限设置装置包括：The second aspect of the present application provides a financial APP permission setting device, where the rights setting device of the financial APP includes:
权限设置模块，当接收到权限设置指令时用于弹出权限设置菜单，所述权限设置菜单包括角色名称设置框、权限范围设置框以及用户数据明细表，所述用户数据明细表根据数据库中存储的用户信息形成；The permission setting module is configured to pop up a permission setting menu when receiving the permission setting instruction, where the permission setting menu includes a role name setting box, a permission range setting box, and a user data list, wherein the user data list is stored according to the database User information formation;
角色权限配置模块，用于将角色名称、权限范围以及所选定的用户数据明细表中的用户信息进行关联并生成角色明细表；a role permission configuration module for associating a role name, a permission range, and user information in the selected user data list to generate a role list;
权限执行模块，当用户在客户端登录后用于根据所述角色明细表执行对应的访问权限。The permission execution module is configured to perform corresponding access rights according to the role list when the user logs in to the client.
本申请第三方面提供一种终端设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，所述处理器执行所述计算机可读指令时实现如下步骤：A third aspect of the present application provides a terminal device including a memory, a processor, and computer readable instructions stored in the memory and executable on the processor, the processor executing the computer readable instructions Implement the following steps:
当接收到权限设置指令时，弹出权限设置菜单，所述权限设置菜单包括角色名称设置框、权限范围设置框以及用户数据明细表，所述用户数据明细表根据数据库中存储的用户信息形成；When receiving the permission setting instruction, the permission setting menu is popped up, and the permission setting menu includes a role name setting box, a permission range setting box, and a user data list, and the user data list is formed according to the user information stored in the database;
将角色名称、权限范围以及所选定的用户数据明细表中的用户信息进行关联并生成角色明细表；Associating the role name, the scope of the permission, and the user information in the selected user data schedule to generate a role schedule;
当用户在客户端登录后，根据所述角色明细表执行对应的访问权限。After the user logs in to the client, the corresponding access rights are executed according to the role list.
本申请第四方面提供一个或多个存储有计算机可读指令的非易失性可读存储介质，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行如下步骤：A fourth aspect of the present application provides one or more non-transitory readable storage mediums storing computer readable instructions, the computer readable instructions being executed by one or more processors such that the one or more processes Perform the following steps:
当接收到权限设置指令时，弹出权限设置菜单，所述权限设置菜单包括角色名称设置框、权限范围设置框以及用户数据明细表，所述用户数据明细表根 据数据库中存储的用户信息形成；When receiving the permission setting instruction, the permission setting menu is popped up, and the permission setting menu includes a role name setting box, a permission range setting box, and a user data list, and the user data list is formed according to the user information stored in the database;
将角色名称、权限范围以及所选定的用户数据明细表中的用户信息进行关联并生成角色明细表；Associating the role name, the scope of the permission, and the user information in the selected user data schedule to generate a role schedule;
当用户在客户端登录后，根据所述角色明细表执行对应的访问权限。After the user logs in to the client, the corresponding access rights are executed according to the role list.
本申请的一个或多个实施例的细节在下面的附图及描述中提出。本申请的其他特征和优点将从说明书、附图以及权利要求书变得明显。Details of one or more embodiments of the present application are set forth in the accompanying drawings and description below. Other features and advantages of the present invention will be apparent from the description, drawings and claims.
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only the present application. For some embodiments, other drawings may be obtained from those of ordinary skill in the art without departing from the drawings.
图1是本申请一种实施例提供的一种金融APP的权限设置方法的流程图；FIG. 1 is a flowchart of a method for setting a privilege of a financial APP according to an embodiment of the present application;
图2是本申请另一种实施例提供的一种金融APP的权限设置方法的流程图；2 is a flowchart of a method for setting a privilege of a financial APP according to another embodiment of the present application;
图3是本申请另一种实施例提供的一种金融APP的权限设置方法的流程图；3 is a flowchart of a method for setting a privilege of a financial APP according to another embodiment of the present application;
图4是本申请另一种实施例提供的一种金融APP的权限设置装置的结构示意图；4 is a schematic structural diagram of a rights setting apparatus of a financial APP according to another embodiment of the present application;
图5是本申请另一种实施例提供的一种金融APP的权限设置装置中的权限设置模块的一种实施方式提供的具体结构示意图；FIG. 5 is a schematic diagram of a specific structure provided by an implementation manner of a rights setting module in a rights setting device of a financial APP according to another embodiment of the present application;
图6是本申请另一种实施例提供的终端设备的结构示意图。FIG. 6 is a schematic structural diagram of a terminal device according to another embodiment of the present application.
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。In order to make the objects, technical solutions, and advantages of the present application more comprehensible, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.
为了说明本申请的技术方案，下面通过具体实施例来进行说明。In order to explain the technical solutions of the present application, the following description will be made by way of specific embodiments.
本申请实施例提供一种金融APP的权限设置方法，如图1所示，该金融APP的权限设置方法包括：The embodiment of the present application provides a method for setting a privilege of a financial APP. As shown in FIG. 1 , the method for setting a privilege of the financial APP includes:
步骤S10.当接收到权限设置指令时，弹出权限设置菜单，权限设置菜单包括角色名称设置框、权限范围设置框以及用户数据明细表，用户数据明细表根据数据库中存储的用户信息形成。Step S10. When the permission setting instruction is received, the permission setting menu is popped up, and the permission setting menu includes a role name setting box, a permission range setting box, and a user data list, and the user data list is formed according to the user information stored in the database.
在步骤S10中，权限设置指令是指用户在金融APP上实施的一种操作事件，当该操作事件为点击位于金融APP上的权限设置按钮时，视为接收到权限设置指令，弹出权限设置菜单，权限设置菜单可以采用列表的方式或者对话框的方式，权限设置菜单包括角色名称设置框、权限范围设置框以及用户数据明细表，角色名称设置框用于设置角色名称，该角色名称可以为用户自己制定的名称，权限范围设置框用于填写该角色所对应的权限范围，例如数据的访问权限，操作权限等，用户数据明细表根据数据库中存储的用户信息形成，公司的数据库中存储公司内的所有用户信息，将每个用户的用户信息中的部门名称、用户姓名以及用户账号提取出来，形成用户数据明细表，该用户数据明细表在权限设置菜单中可以采用多级下拉框的形式显示，例如第一级显示部门名称，选择部门名称后即出现该部门所属的多个小部门，直至显示小部门对应的多个用户姓名及每个用户姓名对应的用户账号。In step S10, the permission setting instruction refers to an operation event implemented by the user on the financial APP. When the operation event is a permission setting button located on the financial APP, it is regarded as receiving the permission setting instruction, and the pop-up permission setting menu is popped up. The permission setting menu may be in the form of a list or a dialog box. The permission setting menu includes a role name setting box, a permission range setting box, and a user data list. The role name setting box is used to set a role name, and the role name may be a user. The name set by the user, the permission scope setting box is used to fill in the permission range corresponding to the role, such as access rights of data, operation authority, etc., the user data list is formed according to the user information stored in the database, and the company database is stored in the company. All user information is extracted from the department name, user name, and user account in each user's user information to form a user data list. The user data list can be displayed in a multi-level drop-down box in the permission setting menu. , for example, the first level shows the department name Multiple small department belongs to the department after department name choices appear until the small sector corresponding to a plurality of user names and user names corresponding to each user account is displayed.
步骤S20.将角色名称、权限范围以及所选定的用户数据明细表中的用户信息进行关联并生成角色明细表。Step S20: Associate the role name, the permission range, and the user information in the selected user data list to generate a role list.
在步骤S20中，确定角色名称和权限范围后，选择需要分配的用户信息，可以选择用户姓名或者用户账号，例如，通过点击用户信息前面的选择按钮，以选定不同的用户，对于角色名称与权限范围之间的对应关系，角色名称可以与权限范围形成一对一的映射关系，角色名称可以与权限范围形成一对多或者多对一的映射关系，对于一个角色名称可以对应一个用户账号，也可以对应多个用户账号，例如，账号登录后，有的用户账号对应A角色，有的用户账号对应A、B和C三个角色，用户账号的权限范围可以是通过不同角色的叠加而扩 大的，作为一种优选的实施方式，角色名称与权限范围形成一对一的映射关系，并将所选定用户账号与角色名称形成一对多的映射关系，根据角色名、权限范围及其选择的一个或者多个用户信息生成角色明细表。In step S20, after determining the role name and the permission range, selecting the user information to be assigned, the user name or the user account may be selected, for example, by clicking a selection button in front of the user information to select a different user, for the role name and The correspondence between the scopes of the rights, the role name can form a one-to-one mapping relationship with the scope of the rights, the role name can form a one-to-many or many-to-one mapping relationship with the scope of the rights, for a role name can correspond to a user account, It can also correspond to multiple user accounts. For example, after the account is logged in, some user accounts correspond to the A role, and some user accounts correspond to the three roles A, B, and C. The scope of the user account can be expanded by superimposing different roles. As a preferred implementation manner, the role name and the permission scope form a one-to-one mapping relationship, and the selected user account and the role name form a one-to-many mapping relationship, according to the role name, the scope of the permission, and the selection thereof. One or more user information generates a role schedule.
步骤S30.当用户在客户端登录后，根据角色明细表执行对应的访问权限。Step S30. After the user logs in to the client, the corresponding access authority is executed according to the role list.
在步骤S30中，当用户使用用户账号在客户端登录后，根据角色明细表获取该用户账号对应的权限范围，并执行该访问权限范围。In step S30, after the user logs in with the user account, the user obtains the permission range corresponding to the user account according to the role list, and executes the access permission range.
本申请实施例提供一种金融APP的权限设置方法，当接收到权限设置指令时，弹出权限设置菜单，根据权限设置菜单中设置的内容，将角色名称、权限范围以及所选定的用户数据明细表中的用户信息相关联并生成角色明细表；当用户使用用户账号在客户端登录后，根据角色明细表执行对应的访问权限。本申请实施例可以使用户在客户端直接设置用户的角色及其权限范围，并通过选择用户数据明细表中的人员很方便的将设置的角色及权限范围与用户联系在一起，提高了分配权限的效率，当人员更新时，只需要快速的选择其对应的角色即可，有利于根据人事更新完成相关人员的权限分配。The embodiment of the present application provides a method for setting a permission of a financial APP. When receiving a permission setting instruction, a pop-up permission setting menu is popped, and the role name, the permission range, and the selected user data details are set according to the content set in the permission setting menu. The user information in the table is associated and a role list is generated; when the user logs in to the client using the user account, the corresponding access rights are executed according to the role list. The embodiment of the present application can enable the user to directly set the role of the user and the scope of the permission on the client, and the user in the user data list can conveniently associate the set role and the scope of the permission with the user, thereby improving the allocation authority. The efficiency, when the personnel update, only need to quickly select the corresponding role, which is beneficial to complete the authority allocation of the relevant personnel according to the personnel update.
本申请实施例提供另一种金融APP的权限设置方法，如图2所示，该金融APP的权限设置方法包括：The embodiment of the present application provides another method for setting a privilege of a financial APP. As shown in FIG. 2, the method for setting a privilege of the financial APP includes:
步骤S11.当接收到权限设置指令时，弹出权限设置菜单，权限设置菜单包括角色名称设置框、权限范围设置框以及用户数据明细表，用户数据明细表根据数据库中存储的用户信息形成。Step S11. When the permission setting instruction is received, the permission setting menu is popped up, and the permission setting menu includes a role name setting box, a permission range setting box, and a user data list, and the user data list is formed according to the user information stored in the database.
步骤S11与步骤S10相同，具体请参加步骤S10的相关描述，在此不再赘述。Step S11 is the same as step S10. For details, refer to the related description of step S10, and details are not described herein again.
步骤S21.将角色名称、权限范围以及所选定的用户数据明细表中的用户信息相关联并生成角色明细表。Step S21. associating the role name, the permission range, and the user information in the selected user data list and generating a role list.
步骤S21与步骤S20相同，具体请参加步骤S20的相关描述，在此不再赘述。Step S21 is the same as step S20. For details, refer to the related description of step S20, and details are not described herein again.
步骤S31.根据角色明细表的权限范围生成与角色名称对应的级别信息，并将级别信息存储在角色明细表中。Step S31: Generate level information corresponding to the role name according to the permission range of the role list, and store the level information in the role list.
在步骤S31中，可选的，级别的大小与权限范围相对应，权限范围越大，级别越高，权限范围的大小可以根据用户账号对应的角色名称的个数确定，该用户账号对应的角色名称越多，级别越高，也可以根据权限范围的具体访问的数字资源的内容确定，访问的数据资源越多，级别越高。例如，最大权限的角色命名为9级，以此类推，8、7、6级，拥有高级别权限的用户可以创建或者删除低级别权限的用户，获取该用户对应的权限级别后将其存储在角色明细表中。In step S31, optionally, the size of the level corresponds to the scope of the permission, and the scope of the permission is larger, and the level of the permission is determined according to the number of the role name corresponding to the user account, and the role corresponding to the user account. The more the name, the higher the level, and the content of the digital resource that is accessed according to the specific scope of the permission. The more data resources are accessed, the higher the level. For example, the role with the highest privilege is named 9th level, and so on. At the 8th, 7th, and 6th levels, users with high-level privilege can create or delete users with low-level privilege, and then obtain the privilege level corresponding to the user and store it in In the role schedule.
需要说明的是，为了便于追责，规定拥有n级角色的用户只能创建和删除拥有n-1级的角色(n≥0)。这种实施方式的优点是便于公司中人员的垂直管理，并且可以实现权限随着人事调动而及时更新。可选的，通过高级别用户创建低级别用户只在一定时间内有效。例如，规定在72小时之内有效，超过72小时创建的用户将失效。这样做的优点是人为添加或者删除的用户的做法只是做一个过渡，为了便于***的统一管理，权限的变更最终还是通过角色的分配来实现。It should be noted that in order to facilitate accountability, users with n-level roles can only create and delete roles with n-1 level (n≥0). The advantage of this embodiment is that it facilitates the vertical management of personnel in the company, and the authority can be updated in time with personnel transfer. Optionally, creating a low-level user through a high-level user is only valid for a certain period of time. For example, the rule is valid for 72 hours, and users created over 72 hours will be invalid. The advantage of this is that the user's practice of adding or deleting is just a transition. In order to facilitate the unified management of the system, the change of authority is finally realized through the assignment of roles.
步骤S41.当用户登录用户账号时，根据角色明细表获取用户账号对应的用户级别信息。Step S41: When the user logs in to the user account, the user level information corresponding to the user account is obtained according to the role list.
步骤S51.当用户账号访问数据资源时，将数据资源的级别与用户级别信息进行对比。Step S51: When the user account accesses the data resource, the level of the data resource is compared with the user level information.
步骤S61.当用户级别高于或等于数据资源的级别时，允许访问。Step S61. When the user level is higher than or equal to the level of the data resource, access is allowed.
步骤S71.当用户级别低于数据资源的级别时，拒绝访问并发出相关的提示信息。Step S71. When the user level is lower than the level of the data resource, the access is denied and the related prompt information is sent.
在步骤S41至步骤S71中，当用户登录用户账号时，根据角色明细表中用户账号对应的级别信息获取该用户账号对应的级别，同时可以将数据资源的访问级别与用户的级别相对应，例如公共数据资源可以设定所有级别都可以访问， 部分保密数据资源可以设定高级别的用户访问，在用户账号访问某一数据资源时，直接根据级别进行判别是否可以访问该用户资源，可以快速的实现用户账号对数据资源的访问。In step S41 to step S71, when the user logs in the user account, the level corresponding to the user account is obtained according to the level information corresponding to the user account in the role list, and the access level of the data resource is corresponding to the level of the user, for example, Public data resources can be set to be accessible at all levels. Some confidential data resources can be set to access users at a high level. When a user account accesses a certain data resource, it can directly determine whether the user resource can be accessed according to the level. Implement user account access to data resources.
本申请另一种实施例提供一种金融APP的权限设置方法，如图4所示，权限设置方法还包括：Another embodiment of the present application provides a method for setting a privilege of a financial APP. As shown in FIG. 4, the privilege setting method further includes:
步骤S12.设置游客角色及其对应的权限范围，权限范围包括***息。Step S12. Set the visitor role and its corresponding permission range, and the permission scope includes public information.
在步骤S12中，可选的，在设置角色名称时，可以设置游客角色，其对应的权限范围为可以对外部人员公开的信息，其对应的用户账号为用户数据明细表以外的账号。In step S12, optionally, when setting the role name, the visitor role may be set, and the corresponding permission range is information that can be disclosed to external personnel, and the corresponding user account is an account other than the user data list.
步骤S22.当用户以游客身份访问***时，生成匿名用户账号，并将匿名用户账号与游客角色相关联。Step S22. When the user accesses the system as a visitor, an anonymous user account is generated, and the anonymous user account is associated with the visitor role.
在步骤S22中，可选的，当用户以游客身份访问***时，通过进行注册，生成匿名用户账号，该匿名用户账号不属于用户数据明细表，生成匿名用户账号后，即将其与游客角色及其权限范围相关联，并添加到角色明细表中，并执行游客角色对应的访问权限。In step S22, optionally, when the user accesses the system as a visitor, the anonymous user account is generated by registering, and the anonymous user account does not belong to the user data list, and after generating the anonymous user account, the guest and the guest role are Its scope of authority is associated and added to the role schedule and the access rights corresponding to the visitor role are executed.
步骤S32.当匿名用户账号访问受限数据资源时，向匿名用户账号输出身份验证提示，根据所提交的身份验证信息，调用用户数据明细表验证用户身份，当验证通过时更新匿名用户账号所对应的角色信息。Step S32. When the anonymous user account accesses the restricted data resource, output an authentication prompt to the anonymous user account, and according to the submitted identity verification information, invoke the user data list to verify the user identity, and update the anonymous user account when the verification is passed. Role information.
在步骤S32中，可选的，当用户使用匿名用户账号访问受限数据资源时，例如数据资源的级别高于匿名用户账号的级别，此时弹出用户身份验证菜单，例如用户身份证验证菜单，提示用户提交身份验证，当用户提交身份验证信息，例如身份证号码时，将该身份验证信息与用户数据明细表中存储的信息进行对比，例如，可以预先在用户数据明细表中存储客户信息，当该身份验证信息符合客户信息时验证通过，通过更新匿名用户账号所对应的角色信息为客户，进而执行该角色所对应的权限。In step S32, optionally, when the user accesses the restricted data resource by using the anonymous user account, for example, the level of the data resource is higher than the level of the anonymous user account, and the user identity verification menu, such as the user ID verification menu, is popped up. The user is prompted to submit the authentication. When the user submits the authentication information, such as the ID number, the authentication information is compared with the information stored in the user data list. For example, the customer information may be stored in the user data list in advance. When the authentication information meets the customer information, the verification is passed, and the role information corresponding to the anonymous user account is updated as the client, and then the permission corresponding to the role is executed.
本申请实施例提供一种游客访问模式，满足不同的用户的需求，当用户需要访问受限的数据资源时，对用户提供的信息进行验证，通过验证时转换用户的角色配置，进而执行该角色所对应的权限，更改权限较快，给用户带来了方便。The embodiment of the present application provides a visitor access mode, which satisfies the needs of different users. When a user needs to access a limited data resource, the user provides information to be verified, and the role configuration of the user is converted by the verification, thereby executing the role. The corresponding permissions, change permissions are faster, and bring convenience to the user.
本申请另一种实施例提供一种金融APP的权限设置装置50，如图4所示，金融APP的权限设置装置50包括：Another embodiment of the present application provides a rights setting device 50 for a financial APP. As shown in FIG. 4, the rights setting device 50 of the financial APP includes:
权限设置模块501，当接收到权限设置指令时，弹出权限设置菜单，所述权限设置菜单包括角色名称设置框、权限范围设置框以及用户数据明细表，用户数据明细表根据数据库中存储的用户信息形成；The permission setting module 501, when receiving the permission setting instruction, pops up the permission setting menu, where the permission setting menu includes a role name setting box, a permission range setting box, and a user data list, and the user data list is based on the user information stored in the database. form;
角色权限配置模块502，将角色名称、权限范围以及所选定的用户数据明细表中的用户信息相关联并生成角色明细表；The role rights configuration module 502 associates the role name, the rights range, and the user information in the selected user data list and generates a role list;
权限执行模块503，当用户在客户端登录后，根据所述角色明细表执行对应的访问权限。The permission execution module 503 executes the corresponding access authority according to the role list after the user logs in at the client.
进一步的，作为一种实施方式，角色权限配置模块502还用于将角色名称与权限范围形成一对一的映射关系，并将所选定用户账号与角色名称形成一对多的映射关系。Further, as an implementation manner, the role rights configuration module 502 is further configured to form a one-to-one mapping relationship between the role name and the rights range, and form a one-to-many mapping relationship between the selected user account and the role name.
进一步的，作为一种实施方式，如图5所示，权限设置模块501还包括：Further, as an implementation manner, as shown in FIG. 5, the rights setting module 501 further includes:
级别设置单元510，用于根据角色明细表的权限范围生成与角色名称对应的级别信息；The level setting unit 510 is configured to generate level information corresponding to the role name according to the permission range of the role list;
级别获取单元511，当用户登录用户账号时用于根据角色明细表获取用户账号对应的用户级别信息。The level obtaining unit 511 is configured to acquire user level information corresponding to the user account according to the role list when the user logs in the user account.
级别判断单元512，当所述用户账号访问数据资源时用于将数据资源的级别与用户级别信息进行对比，当用户级别高于或等于数据资源的级别时，允许访问；当用户级别低于数据资源的级别时，拒绝访问并发出相关的提示信息。The level determining unit 512 is configured to compare the level of the data resource with the user level information when the user account accesses the data resource, and allow access when the user level is higher than or equal to the level of the data resource; when the user level is lower than the data When the level of the resource is reached, the access is denied and the relevant prompt message is issued.
上述终端设备中模块的具体工作过程，可以参考前述方法实施例中的对应 过程，在此不再赘述。For the specific working process of the module in the foregoing terminal device, refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.
本申请另一种实施例提供一个或多个存储有计算机可读指令的非易失性可读存储介质。该一个或多个存储有计算机可读指令的非易失性可读存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行上述实施例中的金融APP权限设置的方法，为避免重复，这里不再赘述。或者，该计算机可读指令被处理器执行时实现上述实施例中金融APP的权限设置装置中各模块/单元的功能，为避免重复，这里不再赘述。Another embodiment of the present application provides one or more non-volatile readable storage media storing computer readable instructions. The one or more non-transitory readable storage mediums storing computer readable instructions, when executed by one or more processors, causing one or more processors to execute the financial APP in the above embodiments The method of setting permissions, in order to avoid duplication, will not be described here. Alternatively, the functions of the modules/units in the authority setting device of the financial APP in the above embodiment are implemented when the computer readable instructions are executed by the processor. To avoid repetition, details are not described herein again.
可以理解地，一个或多个存储有计算机可读指令的非易失性可读存储介质可以包括：能够携带所述计算机可读指令的任何实体或装置、记录介质、U盘、移动硬盘、磁碟、光盘、计算机存储器、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、电载波信号和电信信号等。It will be understood that one or more non-volatile readable storage media storing computer readable instructions may comprise: any entity or device capable of carrying the computer readable instructions, a recording medium, a USB flash drive, a mobile hard drive, a magnetic Discs, optical discs, computer memories, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier signals, and telecommunications signals.
图6是本实施例中终端设备的示意图。如图6所示，终端设备6包括处理器60、存储器61以及存储在存储器61中并可在处理器60上运行的计算机可读指令62。处理器60执行计算机可读指令62时实现上述实施例中金融产品显示方法的各个步骤，例如图1所示的步骤S10、S20和S30。或者，处理器60执行计算机可读指令62时实现上述实施例中金融APP的权限设置装置各模块/单元的功能，如图4所示金融APP的权限设置模块501，角色权限配置模块502和权限执行模块503。Figure 6 is a schematic diagram of a terminal device in this embodiment. As shown in FIG. 6, terminal device 6 includes a processor 60, a memory 61, and computer readable instructions 62 stored in memory 61 and operative on processor 60. The processor 60 executes the computer readable instructions 62 to implement the various steps of the financial product display method of the above-described embodiments, such as steps S10, S20, and S30 shown in FIG. Alternatively, when the processor 60 executes the computer readable instructions 62, the functions of the modules/units of the rights setting device of the financial APP in the above embodiment are implemented, as shown in FIG. 4, the rights setting module 501 of the financial APP, the role rights configuration module 502, and the rights. Execution module 503.
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，仅以上述各功能单元、模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能单元、模块完成，即将所述装置的内部结构划分成不同的功能单元或模块，以完成以上描述的全部或者部分功能。It will be clearly understood by those skilled in the art that, for convenience and brevity of description, only the division of each functional unit and module described above is exemplified. In practical applications, the above functions may be assigned to different functional units according to needs. The module is completed by dividing the internal structure of the device into different functional units or modules to perform all or part of the functions described above.
以上所述实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其 依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围，均应包含在本申请的保护范围之内。The above-mentioned embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still implement the foregoing embodiments. The technical solutions described in the examples are modified or equivalently replaced with some of the technical features; and the modifications or substitutions do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in Within the scope of protection of this application.
Claims (20)
- 一种金融APP的权限设置方法，其特征在于，所述权限设置方法包括：A method for setting a permission of a financial APP, characterized in that the permission setting method comprises:当接收到权限设置指令时，弹出权限设置菜单，所述权限设置菜单包括角色名称设置框、权限范围设置框以及用户数据明细表，所述用户数据明细表根据数据库中存储的用户信息形成；When receiving the permission setting instruction, the permission setting menu is popped up, and the permission setting menu includes a role name setting box, a permission range setting box, and a user data list, and the user data list is formed according to the user information stored in the database;将角色名称、权限范围以及所选定的用户数据明细表中的用户信息进行关联并生成角色明细表；Associating the role name, the scope of the permission, and the user information in the selected user data schedule to generate a role schedule;当用户在客户端登录后，根据所述角色明细表执行对应的访问权限。After the user logs in to the client, the corresponding access rights are executed according to the role list.
- 如权利要求1所述的权限设置方法，其特征在于，所述用户数据明细表根据数据库中存储的用户信息形成，包括：The privilege setting method according to claim 1, wherein the user data list is formed according to user information stored in a database, and includes:根据用户信息中的部门名称、用户姓名以及用户账号形成用户数据明细表。A user data list is formed based on the department name, user name, and user account in the user information.
- 如权利要求1所述的权限设置方法，其特征在于，将角色名称、权限范围以及所选定的用户数据明细表中的用户信息进行关联，包括：The permission setting method according to claim 1, wherein the role name, the permission range, and the user information in the selected user data list are associated, including:将角色名称与权限范围形成一对一的映射关系，并将所选定用户账号与角色名称形成一对多的映射关系。The role name and the permission range form a one-to-one mapping relationship, and the selected user account and the role name form a one-to-many mapping relationship.
- 如权利要求3所述的权限设置方法，其特征在于，将角色名称、权限范围以及所选定的用户数据明细表中的用户信息相关联并生成角色明细表，之后还包括：The authority setting method according to claim 3, wherein the role name, the permission range, and the user information in the selected user data list are associated and a role list is generated, and then includes:根据角色明细表的权限范围生成与角色名称对应的级别信息，并将所述级别信息存储在所述角色明细表中；Generating level information corresponding to the role name according to the permission range of the role list, and storing the level information in the role list;当用户在客户端登录后，根据所述角色明细表执行对应的访问权限，包括：After the user logs in to the client, the corresponding access rights are executed according to the role list, including:当用户登录用户账号时，根据所述角色明细表获取用户账号对应的用户级别信息；When the user logs in to the user account, the user level information corresponding to the user account is obtained according to the role list.当所述用户账号访问数据资源时，将数据资源的级别与用户级别信息进行对比，当用户级别高于或等于数据资源的级别时，允许访问；否则拒绝访问并发出相关的提示信息。When the user account accesses the data resource, the level of the data resource is compared with the user level information, and when the user level is higher than or equal to the level of the data resource, access is allowed; otherwise, the access is denied and the related prompt information is sent.
- 如权利要求3所述的权限设置方法，其特征在于，根据角色明细表的权限范围生成与角色名称对应的级别信息，并将所述级别信息存储在所述角色明细表中，之后还包括：The privilege setting method according to claim 3, wherein the level information corresponding to the role name is generated according to the privilege range of the role list, and the level information is stored in the role list, and further includes:根据拥有n级角色的用户指令创建和删除拥有n-1级的角色。Create and delete roles with n-1 levels based on user instructions with n-level roles.
- 如权利要求3所述的权限设置方法，其特征在于，所述权限设置方法还包括：The privilege setting method according to claim 3, wherein the privilege setting method further comprises:设置游客角色及其对应的权限范围，所述权限范围包括***息；Setting a visitor role and its corresponding permission range, the permission scope including public information;当用户以游客身份访问***时，生成匿名用户账号，并将所述匿名用户账号与游客角色相关联；When the user accesses the system as a visitor, an anonymous user account is generated, and the anonymous user account is associated with the visitor role;当所述匿名用户账号访问受限数据资源时，向所述匿名用户账号输出身份验证提示，根据所提交的身份验证信息，调用用户数据明细表验证用户身份，当验证通过时更新所述匿名用户账号所对应的角色信息。When the anonymous user account accesses the restricted data resource, output an authentication prompt to the anonymous user account, and according to the submitted authentication information, invoke a user data list to verify the user identity, and update the anonymous user when the verification is passed. The role information corresponding to the account.
- 一种金融APP的权限设置装置，其特征在于，所述权限设置装置包括：A privilege setting device for a financial APP, characterized in that the privilege setting device comprises:权限设置模块，当接收到权限设置指令时用于弹出权限设置菜单，所述权限设置菜单包括角色名称设置框、权限范围设置框以及用户数据明细表，所述用户数据明细表根据数据库中存储的用户信息形成；The permission setting module is configured to pop up a permission setting menu when receiving the permission setting instruction, where the permission setting menu includes a role name setting box, a permission range setting box, and a user data list, wherein the user data list is stored according to the database User information formation;角色权限配置模块，用于将角色名称、权限范围以及所选定的用户数据明细表中的用户信息进行关联并生成角色明细表；a role permission configuration module for associating a role name, a permission range, and user information in the selected user data list to generate a role list;权限执行模块，当用户在客户端登录后用于根据所述角色明细表执行对应的访问权限。The permission execution module is configured to perform corresponding access rights according to the role list when the user logs in to the client.
- 如权利要求7所述的金融APP的权限设置装置，其特征在于，所述权限设置装置还包括：The authority setting device of the financial APP according to claim 7, wherein the authority setting device further comprises:级别设置单元，用于根据角色明细表的权限范围生成与角色名称对应的级别信息；a level setting unit, configured to generate level information corresponding to the role name according to the permission range of the role list;级别获取单元，当用户登录用户账号时用于根据所述角色明细表获取用户账号对应的用户级别信息；a level obtaining unit, configured to acquire user level information corresponding to the user account according to the role list when the user logs in the user account;级别判断单元，当所述用户账号访问数据资源时用于将数据资源的级别与用户级别信息进行对比，当用户级别高于或等于数据资源的级别时，允许访问；当用户级别低于数据资源的级别时，拒绝访问并发出相关的提示信息。The level determining unit is configured to compare the level of the data resource with the user level information when the user account accesses the data resource, and allow access when the user level is higher than or equal to the level of the data resource; when the user level is lower than the data resource At the level of the access, the access is denied and the relevant prompt message is issued.
- 一种终端设备，包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机可读指令，其特征在于，所述处理器执行所述计算机可读指令时实现如下步骤：A terminal device comprising a memory, a processor, and computer readable instructions stored in the memory and operable on the processor, wherein the processor executes the computer readable instructions as follows step:当接收到权限设置指令时，弹出权限设置菜单，所述权限设置菜单包括角色名称设置框、权限范围设置框以及用户数据明细表，所述用户数据明细表根据数据库中存储的用户信息形成；When receiving the permission setting instruction, the permission setting menu is popped up, and the permission setting menu includes a role name setting box, a permission range setting box, and a user data list, and the user data list is formed according to the user information stored in the database;将角色名称、权限范围以及所选定的用户数据明细表中的用户信息进行关联并生成角色明细表；Associating the role name, the scope of the permission, and the user information in the selected user data schedule to generate a role schedule;当用户在客户端登录后，根据所述角色明细表执行对应的访问权限。After the user logs in to the client, the corresponding access rights are executed according to the role list.
- 如权利要求9所述的终端设备，其特征在于，所述用户数据明细表根据数据库中存储的用户信息形成，包括：The terminal device according to claim 9, wherein the user data list is formed according to user information stored in a database, and includes:根据用户信息中的部门名称、用户姓名以及用户账号形成用户数据明细表。A user data list is formed based on the department name, user name, and user account in the user information.
- 如权利要求9所述的终端设备，其特征在于，将角色名称、权限范围以及所选定的用户数据明细表中的用户信息进行关联，包括：The terminal device according to claim 9, wherein the role name, the permission range, and the user information in the selected user data list are associated, including:将角色名称与权限范围形成一对一的映射关系，并将所选定用户账号与角色名称形成一对多的映射关系。The role name and the permission range form a one-to-one mapping relationship, and the selected user account and the role name form a one-to-many mapping relationship.
- 如权利要求11所述的终端设备，其特征在于，将角色名称、权限范围以及所选定的用户数据明细表中的用户信息相关联并生成角色明细表，之后还包括：The terminal device according to claim 11, wherein the role name, the permission range, and the user information in the selected user data list are associated and a role list is generated, and then includes:根据角色明细表的权限范围生成与角色名称对应的级别信息，并将所述级别信息存储在所述角色明细表中；Generating level information corresponding to the role name according to the permission range of the role list, and storing the level information in the role list;当用户在客户端登录后，根据所述角色明细表执行对应的访问权限，包括：After the user logs in to the client, the corresponding access rights are executed according to the role list, including:当用户登录用户账号时，根据所述角色明细表获取用户账号对应的用户级 别信息；When the user logs in to the user account, the user level information corresponding to the user account is obtained according to the role list;当所述用户账号访问数据资源时，将数据资源的级别与用户级别信息进行对比，当用户级别高于或等于数据资源的级别时，允许访问；否则拒绝访问并发出相关的提示信息。When the user account accesses the data resource, the level of the data resource is compared with the user level information, and when the user level is higher than or equal to the level of the data resource, access is allowed; otherwise, the access is denied and the related prompt information is sent.
- 如权利要求9所述的终端设备，其特征在于，根据角色明细表的权限范围生成与角色名称对应的级别信息，并将所述级别信息存储在所述角色明细表中，之后还包括：The terminal device according to claim 9, wherein the level information corresponding to the role name is generated according to the permission range of the role list, and the level information is stored in the role list, and further includes:根据拥有n级角色的用户指令创建和删除拥有n-1级的角色。Create and delete roles with n-1 levels based on user instructions with n-level roles.
- 如权利要求9所述的终端设备，其特征在于，所述处理器执行所述计算机可读指令时还实现如下步骤：The terminal device according to claim 9, wherein said processor further implements the following steps when said computer readable instructions are executed:设置游客角色及其对应的权限范围，所述权限范围包括***息；Setting a visitor role and its corresponding permission range, the permission scope including public information;当用户以游客身份访问***时，生成匿名用户账号，并将所述匿名用户账号与游客角色相关联；When the user accesses the system as a visitor, an anonymous user account is generated, and the anonymous user account is associated with the visitor role;当所述匿名用户账号访问受限数据资源时，向所述匿名用户账号输出身份验证提示，根据所提交的身份验证信息，调用用户数据明细表验证用户身份，当验证通过时更新所述匿名用户账号所对应的角色信息。When the anonymous user account accesses the restricted data resource, output an authentication prompt to the anonymous user account, and according to the submitted authentication information, invoke a user data list to verify the user identity, and update the anonymous user when the verification is passed. The role information corresponding to the account.
- 一个或多个存储有计算机可读指令的非易失性可读存储介质，其特征在于，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器执行如下步骤：One or more non-transitory readable storage mediums storing computer readable instructions, wherein when the computer readable instructions are executed by one or more processors, cause the one or more processors to execute The following steps:当接收到权限设置指令时，弹出权限设置菜单，所述权限设置菜单包括角色名称设置框、权限范围设置框以及用户数据明细表，所述用户数据明细表根据数据库中存储的用户信息形成；When receiving the permission setting instruction, the permission setting menu is popped up, and the permission setting menu includes a role name setting box, a permission range setting box, and a user data list, and the user data list is formed according to the user information stored in the database;将角色名称、权限范围以及所选定的用户数据明细表中的用户信息进行关联并生成角色明细表；Associating the role name, the scope of the permission, and the user information in the selected user data schedule to generate a role schedule;当用户在客户端登录后，根据所述角色明细表执行对应的访问权限。After the user logs in to the client, the corresponding access rights are executed according to the role list.
- 如权利要求15所述的非易失性可读存储介质，其特征在于，所述用户 数据明细表根据数据库中存储的用户信息形成，包括：The non-volatile readable storage medium of claim 15, wherein the user data list is formed according to user information stored in a database, comprising:根据用户信息中的部门名称、用户姓名以及用户账号形成用户数据明细表。A user data list is formed based on the department name, user name, and user account in the user information.
- 如权利要求15所述的非易失性可读存储介质，其特征在于，将角色名称、权限范围以及所选定的用户数据明细表中的用户信息进行关联，包括：The non-volatile readable storage medium of claim 15 wherein the role name, the scope of the rights, and the user information in the selected user data list are associated, including:将角色名称与权限范围形成一对一的映射关系，并将所选定用户账号与角色名称形成一对多的映射关系。The role name and the permission range form a one-to-one mapping relationship, and the selected user account and the role name form a one-to-many mapping relationship.
- 如权利要求17所述的非易失性可读存储介质，其特征在于，将角色名称、权限范围以及所选定的用户数据明细表中的用户信息相关联并生成角色明细表，之后还包括：A non-volatile readable storage medium according to claim 17, wherein the role name, the scope of authority, and the user information in the selected user data list are associated and a role list is generated, and then includes :根据角色明细表的权限范围生成与角色名称对应的级别信息，并将所述级别信息存储在所述角色明细表中；Generating level information corresponding to the role name according to the permission range of the role list, and storing the level information in the role list;当用户在客户端登录后，根据所述角色明细表执行对应的访问权限，包括：After the user logs in to the client, the corresponding access rights are executed according to the role list, including:当用户登录用户账号时，根据所述角色明细表获取用户账号对应的用户级别信息；When the user logs in to the user account, the user level information corresponding to the user account is obtained according to the role list.当所述用户账号访问数据资源时，将数据资源的级别与用户级别信息进行对比，当用户级别高于或等于数据资源的级别时，允许访问；否则拒绝访问并发出相关的提示信息。When the user account accesses the data resource, the level of the data resource is compared with the user level information, and when the user level is higher than or equal to the level of the data resource, access is allowed; otherwise, the access is denied and the related prompt information is sent.
- 如权利要求15所述的非易失性可读存储介质，其特征在于，根据角色明细表的权限范围生成与角色名称对应的级别信息，并将所述级别信息存储在所述角色明细表中，之后还包括：The non-volatile readable storage medium according to claim 15, wherein level information corresponding to the role name is generated according to a permission range of the role list, and the level information is stored in the role list And then include:根据拥有n级角色的用户指令创建和删除拥有n-1级的角色。Create and delete roles with n-1 levels based on user instructions with n-level roles.
- 如权利要求15所述的非易失性可读存储介质，其特征在于，所述计算机可读指令被一个或多个处理器执行时，使得所述一个或多个处理器还执行如下步骤：The non-volatile readable storage medium of claim 15 wherein said computer readable instructions are executed by one or more processors such that said one or more processors further perform the steps of:设置游客角色及其对应的权限范围，所述权限范围包括***息；Setting a visitor role and its corresponding permission range, the permission scope including public information;当用户以游客身份访问***时，生成匿名用户账号，并将所述匿名用户账 号与游客角色相关联；When the user accesses the system as a visitor, an anonymous user account is generated and the anonymous user account is associated with the visitor role;当所述匿名用户账号访问受限数据资源时，向所述匿名用户账号输出身份验证提示，根据所提交的身份验证信息，调用用户数据明细表验证用户身份，当验证通过时更新所述匿名用户账号所对应的角色信息。When the anonymous user account accesses the restricted data resource, output an authentication prompt to the anonymous user account, and according to the submitted authentication information, invoke a user data list to verify the user identity, and update the anonymous user when the verification is passed. The role information corresponding to the account.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710918518.7A CN107844698B (en) | 2017-09-30 | 2017-09-30 | Method, device and equipment for setting authority of financial APP and storage medium |
| CN201710918518.7 | 2017-09-30 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2019062049A1 true WO2019062049A1 (en) | 2019-04-04 |
Family
ID=61662196
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2018/080918 WO2019062049A1 (en) | 2017-09-30 | 2018-03-28 | Financial app permission configuration method, device and equipment, and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107844698B (en) |
| WO (1) | WO2019062049A1 (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107844698B (en) * | 2017-09-30 | 2020-05-29 | 平安科技（深圳）有限公司 | Method, device and equipment for setting authority of financial APP and storage medium |
| CN108629484A (en) * | 2018-03-30 | 2018-10-09 | 平安科技（深圳）有限公司 | It attends a banquet qualification management method, apparatus and storage medium |
| CN109598117A (en) * | 2018-10-24 | 2019-04-09 | 平安科技（深圳）有限公司 | Right management method, device, electronic equipment and storage medium |
| CN109783581A (en) * | 2018-11-30 | 2019-05-21 | 平安科技（深圳）有限公司 | Right management method, device, electronic equipment and storage medium |
| CN111046354A (en) * | 2019-11-05 | 2020-04-21 | 京东数字科技控股有限公司 | Access and client access management method, system and medium |
| CN111062028B (en) * | 2019-12-13 | 2023-11-24 | 腾讯科技（深圳）有限公司 | Authority management method and device, storage medium and electronic equipment |
| CN111353145A (en) * | 2020-02-28 | 2020-06-30 | 广东特惟嘉科技发展有限公司 | User authority management method, device and storage medium |
| CN111581650B (en) * | 2020-04-09 | 2024-03-05 | 上海淇毓信息科技有限公司 | Business system authority management method, system and electronic equipment |
| CN113505362B (en) * | 2021-07-16 | 2023-09-22 | 长鑫存储技术有限公司 | System authority management and control method, data center, management and control device and storage medium |
| CN115017531B (en) * | 2022-08-09 | 2022-11-01 | 威海海洋职业学院 | Financial data sharing method and system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102567675A (en) * | 2012-02-15 | 2012-07-11 | 合一网络技术(北京)有限公司 | User authority management method and system in business system |
| CN103500297A (en) * | 2013-10-11 | 2014-01-08 | 济钢集团有限公司 | Fine grit authority management method in information system |
| CN104680082A (en) * | 2015-03-17 | 2015-06-03 | 浪潮集团有限公司 | Data authority accessing control model |
| CN107844698A (en) * | 2017-09-30 | 2018-03-27 | 平安科技（深圳）有限公司 | Financial APP authority setting method, device, equipment and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102467642B (en) * | 2010-11-17 | 2015-02-25 | 北大方正集团有限公司 | Permission control method and device for application software |
| CN104090770A (en) * | 2014-07-22 | 2014-10-08 | 中国地质大学（北京） | Method based on function of user right configuration system in software development |
-
2017
- 2017-09-30 CN CN201710918518.7A patent/CN107844698B/en active Active
-
2018
- 2018-03-28 WO PCT/CN2018/080918 patent/WO2019062049A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102567675A (en) * | 2012-02-15 | 2012-07-11 | 合一网络技术(北京)有限公司 | User authority management method and system in business system |
| CN103500297A (en) * | 2013-10-11 | 2014-01-08 | 济钢集团有限公司 | Fine grit authority management method in information system |
| CN104680082A (en) * | 2015-03-17 | 2015-06-03 | 浪潮集团有限公司 | Data authority accessing control model |
| CN107844698A (en) * | 2017-09-30 | 2018-03-27 | 平安科技（深圳）有限公司 | Financial APP authority setting method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107844698B (en) | 2020-05-29 |
| CN107844698A (en) | 2018-03-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2019062049A1 (en) | Financial app permission configuration method, device and equipment, and storage medium | |
| US9667661B2 (en) | Privileged account manager, dynamic policy engine | |
| US20190332780A1 (en) | Code package processing | |
| US10944560B2 (en) | Privacy-preserving identity asset exchange | |
| US11201746B2 (en) | Blockchain access control system | |
| TW201738825A (en) | Method and device for outputting risk information and constructing risk information | |
| US11138323B2 (en) | Blockchain-based content management system, method, apparatus, and electronic device | |
| US20150033327A1 (en) | Systems and methodologies for managing document access permissions | |
| US10958687B2 (en) | Generating false data for suspicious users | |
| US11126746B2 (en) | Dynamic security controls for data sharing between systems | |
| US11341192B2 (en) | Cross platform collaborative document management system | |
| You et al. | [Retracted] Research and Design of Docker Technology Based Authority Management System | |
| CN109901816A (en) | Co-development method, terminal, medium and the system of protection copyright based on container | |
| US20240007458A1 (en) | Computer user credentialing and verification system | |
| Patel et al. | An approach to introduce basics of Salesforce. com: A cloud service provider | |
| US20150067124A1 (en) | Application service management device and application service management method | |
| CN111414591B (en) | Workflow management method and device | |
| US20120216240A1 (en) | Providing data security through declarative modeling of queries | |
| US11062001B2 (en) | Matrix transformation-based authentication | |
| CN108322421B (en) | Computer system safety management method and device | |
| US20180365237A1 (en) | Method and system for using micro objects | |
| US11907394B1 (en) | Isolation and authorization for segregated command and query database resource access | |
| WO2023159458A1 (en) | Device runtime update pre-authentication | |
| US20230153450A1 (en) | Privacy data management in distributed computing systems | |
| US11392898B2 (en) | Secure cloud collaboration platform |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18862338 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 23/09/2020) |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 18862338 Country of ref document: EP Kind code of ref document: A1 |