Role-based access control (RBAC)
基于角色的访问控制 (RBAC)
Using RBAC involves two parts of work.
使用RBAC包含两个部分的工作。
In RBAC, an important conception 'role' is introduced.
RBAC中引入了角色这一重要概念。
The modification of roles in hierarchy RBAC is very difficult.
层次化的RBAC模型中角色本身的更改是相当困难的。
Domain RBAC allows creating 1024 domain object's on the system.
DomainRBAC在系统上最多可创建1024个域对象。
Domain RBAC is enabled by default on enhanced RBAC mode system.
DomainRBAC在加强的 RBAC模式下是默认启用的。
Another approach to controlling access is role-based access control (RBAC).
另一种控制访问的方法是基于角色的访问控制(RBAC)。
Now that the users exist, set up RBAC to log them into the appropriate roles.
现在用户已经存在，请设置rbac以将这些用户登录到相应的角色中。
In the privilege management system an important concept is introduced - RBAC.
在权限管理系统中，引入了一个重要的概念——RBAC。
This paper proposes an improved access control model for portal systems: P-RBAC.
提出了一种面向门户系统的访问控制模型P -RBAC。
The integration of RBAC security model and generally UML design model is introduced.
阐述了系统RBAC的安全模型与系统通常U ML设计模型的集成。
To facilitate our description next, we will first introduce some basic RBAC concepts.
为了便于说明，我们先介绍一些RBAC基本概念。
You generally think of RBAC as specifying the access that users in certain roles may receive.
一般情况下，可以将RBAC视为指定某些角色下的用户接收的访问。
Using FPM actually helps cut down on the number of these files, whether one USES RBAC or not.
无论使用RBAC与否，使用fpm实际上有助于减少这些文件的数量。
The central notion of RBAC is that users do not have discretionary access to enterprise objects.
RBAC的中心思想是，用户没有对企业对象的自主访问权。
Constraints are considered to be the principal motivation for Role-Based Access Control (RBAC).
限制可以视为是基于角色的访问控制(RBAC)的主要动机。
To accelerate the research and application of RBAC, NIST in USA has proposed a standard for it.
为了促进RBAC的研究和应用，美国国家技术与标准局提出了RBAC建议标准。
User management, department management, mail management, integrated the RBAC rights management system.
用户管理，部门管理，邮件管理等，集成了RBAC权限管理系统。
A sort of RBAC model for electric power MIS was designed on the basis of studying access control models.
本文在研究r BAC访问控制模型的基础上，设计了一种应用于电力MIS系统的RBAC模型。
But tradition RBAC can not easy change operate set of role, and would conflict with exterior application.
传统RBAC在改变角色的操作集合时，易与外部应用程序发生冲突。
With the separating of user and permission, RBAC can make a convenient and flexible permission management.
其主要思想是通过用户与权限的分离，使权限管理方便灵活。
Domain RBAC introduces four new commands and USES some existing commands to handle domain operations on a system.
DomainRBAC引入了四个新命令并使用一些现有的命令来处理系统上的域操作。
It has simple configuration and secure communication with integrating RBAC to enable non-root users to collect FFDC data.
它具有简单的配置和安全的通信，并通过集成rbac允许非根用户收集FFDC数据。
Domain RBAC provides fine granular control access over resources for users and requires Enhanced RBAC to be enabled.
DomainRBAC为用户提供了很好的资源访问粒度控制，它要求启用Enhanced RBAC。
Injecting RBAC mechanism into task nodes to restrict the role attribute can secure the access control of the workflow.
在任务节点中引入RBAC机制对角色属性进行约束以实现对工作流的安全存取控制。
The domain's support provides this key feature to augment the functionality provided by the Role Based Access Control (RBAC).
对域的支持提供这个关键特性，以此补充RoleBasedAccessControl (RBAC)提供的功能。
AIX provides a facility to delegate administrative roles to non-root users through role-based access control (RBAC) mechanism.
AIX提供了一种功能，可通过基于角色的访问控制(RBAC)机制将管理角色委托给非root用户。
In AIX 6.1, IBM introduced Role Based Access Control (RBAC), which addresses many of the security and auditing concerns of sudo.
在AIX 6.1中，IBM引入了基于角色的访问控制(RBAC)，这解决了sudo的许多安全和审计问题。
On the basis of RBAC model, this paper put forward a new model PRBAC, which was a twolevel model based on the post and role.
在RBAC模型的基础上，提出一种基于岗位和角色的两级访问控制模型——PRBAC。
With the introduction of RBAC, a feasibility of extending administrator roles and responsibilities to non-root users is provided.
随着RBAC的引入，也带来了将管理权限和责任扩展到非 root用户的可行性。
应用推荐