Role-based access control (RBAC)
基于角色的访问控制 (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)。
Using FPM actually helps cut down on the number of these files, whether one USES RBAC or not.
无论使用RBAC与否，使用fpm实际上有助于减少这些文件的数量。
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模型中角色本身的更改是相当困难的。
Managing number of roles effectively is a formidable task in RBAC.
如何有效的管理大量角色是RBAC模型中面对的一个问题。
Role authorization constraint is one of focal points of RBAC research.
角色授权约束是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。
To facilitate our description next, we will first introduce some basic RBAC concepts.
为了便于说明，我们先介绍一些RBAC基本概念。
Detailed discussion is given regarding the implementation of models of RBAC database and API.
详细介绍并讨论基于角色控制的数据库模型和API模型的实现方法。
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建议标准。
The central notion of RBAC is that users do not have discretionary access to enterprise objects.
RBAC的中心思想是，用户没有对企业对象的自主访问权。
User management, department management, mail management, integrated the RBAC rights management system.
用户管理，部门管理，邮件管理等，集成了RBAC权限管理系统。
RBAC model is the most popular access control strategy because of its flexibleness, convenience and security.
RBAC模型具有灵活性、方便性和安全性的特点，因此成为访问控制策略的首选。
Domain RBAC introduces four new commands and USES some existing commands to handle domain operations on a system.
DomainRBAC引入了四个新命令并使用一些现有的命令来处理系统上的域操作。
Injecting RBAC mechanism into task nodes to restrict the role attribute can secure the access control of the workflow.
在任务节点中引入RBAC机制对角色属性进行约束以实现对工作流的安全存取控制。
The mechanism integrates the method of RBAC and OMG's RAD facility. It implements static authority and dynamic authority.
该机制综合应用了RBAC和OMG的RAD工具的思想，实现了静态授权和动态授权。
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。
The domain's support provides this key feature to augment the functionality provided by the Role Based Access Control (RBAC).
对域的支持提供这个关键特性，以此补充RoleBasedAccessControl (RBAC)提供的功能。
Role -based access control (RBAC) is a kind of access control mechanism which is convenient, secure and of high -performance.
基于角色访问控制(RBAC)是一种方便、安全、高效的访问控制机制。
As a sort of security mechanism, Role Based Access Control (RBAC) technique has been one of the hotspots in current research.
基于角色的访问控制(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的许多安全和审计问题。
With the introduction of RBAC, a feasibility of extending administrator roles and responsibilities to non-root users is provided.
随着RBAC的引入，也带来了将管理权限和责任扩展到非 root用户的可行性。
In this article, we'll review sudo and then outline how you can migrate to RBAC to improve your organization's administration model.
在本文中，我们将首先检查sudo，然后概述如何迁移到RBAC来改进组织的管理模型。
应用推荐