其他属性指定提供者url以及安全主体和凭证。
The other properties specify the provider URL and the security principal and credentials.
安全主体表示用户和与该用户相关联的角色。
A security principal represents a user and the roles associated with that user.
虽然可从消息验证和删除WS - UNT，但安全主体(用户身份)会发生。
The WS-UNT is validated and removed from message, but a security subject (user's identity) takes place.
最后的三个.jar文件提供了其他支持类，比如与Geronimo对话的安全主体。
The final three.jar files provide other supporting classes, such as security principals, for talking with Geronimo.
对于给定应用程序域，宿主可更改默认的基于角色的安全性策略并设置默认安全主体。
For a given application domain, the host can change the default role-based security policy and set a default security principal.
雇主的要是我而是会聘请有此范围和好奇心比那些狭隘地追求安全主体和高年级的毕业生。
If I were an employer I would rather employ graduates who have this range and curiosity than those who narrowly pursued safe subjects and high grades.
安全的内涵和外延、安全威胁的来源、安全主体以及维护安全的手段都需要从理论上加以修正。
The meaning and extension of security, the source of security threat, and the object of security as well as the means of defending security all require substantial theoretical modifications.
还可以为KerberosV 5帐户映射建立本地帐户，这对告知操作系统如何对特定的安全主体进行授权非常必要。
You can also set up local account to Kerberos V5 account mappings, which is necessary to inform the operating system how to authorize a specific security principal.
授权支持：可以处理各种授权方式，不管你是使用Windows验证、线程安全主体、ASP.NET基于角色的安全模式或者你自己自定义的。
Authorization Support: Handled a variety of ways whether you use Windows authentication, thread principals, ASP.NET role-based security or your own.
主体之间的安全中间层可以进一步分解为执行点、决策点、契约和属性。
The security intermediation between principals can be further deconstructed into enforcement points, decision points, contracts, and attributes.
请在安全的地方记录名称和所选择的密码，因为这些主体对您的NAS环境来说是非常重要的。
Record the name and chosen password in a secure place, as these principals are essential for your NAS environment.
此外，SOA安全团队应该生成高级图形表示形式，以说明团队成员将如何保护主体之间的交互。
In addition, the SOA security team should generate a high-level graphic representation of how team members will secure interactions among principals.
GSSAPI缺少一个获取凭证的登录接口；它仅在底层的安全机制中查询调用主体的凭证。
GSSAPI lacks a login interface for acquiring credentials; it merely queries the underlying security mechanism for credentials for the calling principal.
随着对主体间的交互的进一步细分，将出现特定的SOA安全服务来专门负责保护这些交互。
As the interactions between principals are further detailed, specific SOA security services will emerge with specific responsibilities for securing those interactions.
在安全领域中，必须保护的项目称为主体。
In the security domain, items that must be secured are called principals.
SAML与其它安全性方法的最大区别在于它以有关多个主体的断言的形式来表述安全性。
SAML is different from other security approaches mostly because of its expression of security in the form of assertions about subjects.
该信息包含主体的身份、公共的安全凭证和私有的安全凭证。
This information includes the principal's identities, public security credentials, and private security credentials.
主体UUID：一个主体的UUID,PAC中描述了该主体的安全属性。
Principal UUID: the UUID of the principal whose security attributes are described in PAC.
由一个Subject代表的主体可以有多个身份和多个安全凭证，所有这些都封装在一个 Subject 中。
The principal represented by a Subject may have multiple identities and multiple security credentials, all encapsulated in the one Subject.
如果启用了wrap -principals选项，CommunityEdition将对主体进行“包装”，以跟踪各个主体来自于哪个登录模块和安全领域。
If the wrap-principals option is enabled, Community Edition will "wrap" principals to track which login module and security realm each principal came from.
然后将安全角色映射到CommunityEdition特定部署计划中的主体。
You then map the security roles to principals in the Community Edition specific deployment plan.
在Gluecode标准版中可以定义多个安全域，然后通过提供一套访问控制主体，对用户进行身份验证和授权。
Multiple security realms can be defined in Gluecode Standard Edition to authenticate and authorize users by providing a set of principals for access control.
在geronimo - web . xmlweb应用程序部署计划中，我们将web .xml中定义的EJB引用映射到特定的EJB，并将安全角色映射到主体。
In the geronimo-web.xml web application deployment plan, we map the EJB references defined in web.xml to specific EJBs, and map the security roles to principals.
定义调用者等于让WebSphere使用Username凭据创建安全凭据和主体。
By defining the caller, you are enabling WebSphere to create the security credential and principal, using the Username token credentials.
安全角色映射到security元素内的role - mappings元素下的主体。
The security roles are mapped to principals under the role-mappings element inside the security element.
取决于您的环境所提供的Web服务安全性(WS - Security)支持，您既可以仅仅对SOAP主体进行签名，也可以对Body内部的单个元素进行签名。
Depending on the WS-Security support your environment provides, you might be able to sign just the SOAP body, or you might be able to sign individual elements within the body.
然后将这些安全角色映射到服务器特定的部署计划(在应用程序部署时使用的部署计划)中的主体(在CommunityEdition的情况下是geronimo - web . xml)。
These security roles are mapped to principals in a server-specific deployment plan (geronimo-web.xml in the case of Community Edition) used at application deployment time.
一旦在 web.xml中定义了安全角色和约束，那么将在应用程序部署计划geronimo-web.xml 中，把安全角色映射为主体。
Once the security roles and constraints are defined in web.xml, the security roles are mapped in the application deployment plan, geronimo-web.xml, to the principals.
在部署计划中配置安全凭据，以构成Run - as角色安全性的主体。
You configure the security credentials that constitute the subject for run-as role security in the deployment plan.
default - subject下的realm元素指定安全领域，id元素指定凭据库中所配置的主体的id。
The realm element under default-subject specifies the security-realm, and the id element specifies the id of the subject as configured in the credential store.
应用推荐