只有继承用户适用于此授权角色。
表1显示了哪种任务支持哪种授权角色。
Table 1 shows which authorization role is supported by which kind of task.
以下授权角色类可用于为升级建模授权角色。
These authorization role classes are available to model authorization rules for escalations.
可以使用人员谓词为预定义的授权角色集定义授权规则。
You define authorization rules using staff verbs for the set of predefined authorization roles.
它要求容器实现一些接口，使部署工具能够管理授权角色。
It requires that containers implement interfaces that enable deployment tools to manage authorization roles.
管理员可以向任何人创建、传输或删除每个授权角色的工作项。
Administrators can create, transfer, or delete work items of every authorization role to anybody.
一些授权角色是必不可少的，这些角色上分配了人员。
Some of the authorization roles mandate that people are assigned to them.
它定义一个新的授权角色，名为administrator。
这些谓词中有些可能返回要分配到授权角色的潜在较大用户ID。
Some of these verbs can return potentially large sets of user IDs to be assigned to an authorization role.
内联参与任务授权角色的成员在相应的人工任务活动上具有相同的角色。
Members of an inline participating task authorization role have the same role on the corresponding human task activity.
以下示例可用于将用户注册中心已知的组成员分配到某个人工任务授权角色。
The following example can be used to assign the members of a group known by the user registry to a human task authorization role.
表2、3和4显示了哪个缺省值适用于哪个人工任务或业务流程授权角色。
Tables 2, 3 and 4 show which defaults apply for which human task or business process authorization role.
在本例中，在本地Servlet上为授权角色LocalRole启用资源约束。
In this example, we enabled a resource constraint on the local servlet for the authorization role LocalRole.
通过在编辑器画布的Staffsettings下选择您所选的授权角色，可以定义授权规则。
You can define authorization rules selecting the authorization role of your choice on the editor canvas, under Staff Settings.
如果发现某个工作项与此用户、所选业务对象和允许调用此api方法的预定义授权角色相关联，则会授予权限。
If a work item is found that is associated with this user, the selected business object, and a predefined authorization role that allows this API method to be invoked, then authorization is granted.
由于每个授权角色都可以授予阅读者权限，因此调用方由于任何分配原因(授权角色)而拥有匹配的工作项就足够了。
Since every authorization role grants reader rights, it is sufficient when the caller has a matching work item for any assignment reason (authorization role).
其中描述了授权角色及其继承规则和缺省值，如何定义授权规则以及如何解析授权规则以执行基于实例的授权。
It described the authorization roles with their inheritance rules and defaults, how you can define authorization rules, and how they are resolved in order to perform instance-based authorization.
在定义人工任务时，可以选择一个授权角色，如“潜在所有者”，并将其与任务编辑器中提供的谓词集中的一个人员谓词关联。
When you define human tasks, you select an authorization role, like "potential owner," and associate it with a staff verb from the verb set offered by the task editor.
发起人可以向以下任何人创建、传输或删除这些授权角色的工作项：潜在所有者、潜在启动者、发起者、阅读者、编辑和升级接收者。
Originators can create, transfer, or delete work items of these authorization roles to anybody: potential owner, potential starter, originator, reader, editor, and escalation receiver.
您可以在这个记录内定义角色以及为应用程序提供授权。
You can define roles in this record as well provide authorization for your application.
每个用户授权担任的角色。
我们希望对用户的角色进行区分，以授权特定用户组声明和处理特定人工任务。
We would also like to distinguish between user roles giving particular user groups authorization to claim and work on certain human tasks.
请注意，可以为安全标识选择未授权访问SCA组件的角色。
Notice that you can choose, for the security identity, a role not authorized to access the SCA component.
执行治理策略的工作应该留给指导委员会或某个得到授权，专门充当此角色的治理机构来做。
Enforcement of governance policies should be left to a steering committee or a governance body specifically empowered to play that role.
您可以设计访问控制策略，以便根据用户在特定组织中的角色对其进行授权。
You can design access control policies to grant authority to a user based on their role in a particular organization.
与J2EE基于角色的授权通常提供的授权相比，此模式提供了更细粒度的授权，可以一直细化到项目内的单个对象的级别。
This pattern provides a more granular level of authorization than is typically provided by J2EE role-based authorization, getting down to the level of an individual object within a system.
基于角色的授权通过仅将资源提供给已分配相应角色的用户来保护资源。
Role-based authorization protects resources by only making them available to users who have been assigned to the appropriate role.
基于角色的授权基于用户是某类用户的成员这一事实提供对资源的访问。
Role-based authorization provides access to resources based on the fact that the user is a member of some class of users.
只要用户不属于对维度具有显式授权的角色，它就属于默认角色的成员，可以根据默认策略访问该维度。
All users who do not belong to a role with explicit authorization on the dimension are members of the default role, and they are able to access the dimension according to the default policy.
本文后面的授权小节将对角色加以解释。
The roles is explained later in the Authorization section of this article
应用推荐