如果使用受信任的应用程序部署，则不会出现任何信任级别提示。
No prompting for trust levels will occur if you use Trusted Application Deployment.
若要配置受信任的应用程序部署，可以将证书安装到计算机或企业级别。
To configure trusted application deployment, the certificate can be installed to the machine or enterprise level.
在某些情况下，通常由受信任的应用程序域宿主提供的证据实际上由加载程序提供。
In some situations, evidence that would normally be provided by a trusted application domain host is actually provided by the loader.
受信任的应用程序域宿主可以重写由加载程序提供的证据，并可提供它们自己的证据。
Trusted application domain hosts can override evidence provided from the loader and can provide their own evidence.
另外，程序集或受信任的应用程序域宿主还可以提供自定义证据作为程序集组成部分的资源。
In addition, an assembly or a trusted application domain host can provide custom evidence as a resource that is part of the assembly.
或者，数据库可能从受信任的应用程序处接收XML文档，而且您已知这些XML数据始终有效。
Or, maybe the database receives XML documents from a trusted application, maybe even one that you control, and you know that the XML data is always valid.
如果数字签名有效，则受信任的应用程序域宿主将签名信息作为证据传递给运行时的策略机制。
If the digital signature is valid, the trusted application domain host passes the signature information as evidence to the runtime's policy mechanism.
受信任的应用程序可以自由地去，但你可以按照自己的互联网接入功能，也认为是非常简单易用。
Trusted applications are free to go, but you can block their Internet access too with functions that are very simple to use.
如果受信任的应用程序域宿主没有提供证据的权限，则程序集或应用程序域会收到已授予宿主的权限。
If the trusted application domain host does not have permission to provide evidence, the assembly or application domain receives the permissions that have been granted to the host.
运行时的策略机制使用来自受信任的应用程序域宿主和程序集的证据来确定一段代码在代码组中的成员资格。
The runtime's policy mechanism USES the evidence from both the trusted application domain host and the assembly to determine a piece of code's membership in a code group.
其他的辨识项(例如组件的数位签章)是程序码本身就有的，可来自载入器或受信任的应用程序定义域主机。
Other evidence, such as an assembly's digital signature, is inherent in the code itself and can come from the loader or a trusted application domain host.
有些辨识项(例如程序码来源的位置)通常来自受信任的应用程序定义域主机，因为只有主应用程序知道这项资讯。
Some evidence, such as where the code originates, usually comes from the trusted application domain host because only the host knows this information.
应用程序使用受信任的应用程序部署，并且没有将用于为应用程序签名的数字证书列为本地计算机上的受信任发行者。
The application USES trusted application Deployment and the digital certificate used to sign the application is not listed as a trusted publisher on the local machine.
您可以假设所有直接访问的用户都是受信任的(即使对内部应用程序来说，这也是一个天真的假设，但是在本场景中这样假设已经足够了)。
You can assume all the direct users are trusted (a naive assumption even for an internal application, but sufficient for this scenario).
在这种新模型下，根据每位用户受信任的程度，对他或者她授权使用应用程序的某一范围的功能。
Under this new model, each user is authorized to use an application's range of functionality according to the degree to which he or she is trusted.
和端到端信任类似，此模型假定请求应用程序是已知的受信任软件。
This model assumes, like the end to end trust, that a requesting application is known and trusted software.
端到端安全模型意味着所有提供者将授予所有受信任的请求应用程序访问权限。
The end to end security model would mean that all providers give access to all trusted requesting applications.
此模型支持用户单点登录到受信任应用程序，由后者以用户的身份进行服务请求。
This model supports single sign on by users to trusted applications which are able to make service requests on their behalf.
如果您的环境不稳定，经常出现组件故障，也可能要重新考虑是否将通道作为受信任应用程序运行。
If your environment is unstable with regular component failure you may also wish to reconsider running the channels as trusted applications.
通过选择此选项，队列管理器中的所有通道都将作为受信任应用程序运行。
By choosing this option all channels within the queue manager will run as trusted.
而且，由于可以以很少的连接资源切换用户，而不需要身份验证，受信任上下文是商业应用程序的理想选择。
Furthermore, the ability to switch users with minimum connection resources and without authentication, makes trusted context an ideal choice for business applications.
本节描述环境的配置和在含受信任上下文的环境下运行DB2CLI应用程序的一些考虑事项。
This section describes the environment configurations and considerations for running DB2 CLI applications under this environment with trusted context.
处理请求者和应用程序服务主机之间的信任关系的消息代理可能是另一个受信任的中介。
Another trusted intermediary might be a message broker that handles trust relationships between requesters and an application service host.
XKMS 将管理客户机应用程序的PKI 的复杂性抽象到了一个受信任的第三方，从而使 PKI 易于管理。
XKMS allows easy management of the PKI by abstracting the complexity of managing the PKI from client applications to a trusted third party.
在应用程序已经建立与DB 2服务器的连接之后，应用程序可以在后端切换与受信任上下文相关联的用户。
After the application has established a trusted connection with the DB2 server, the application may switch users associated with the trusted context object in the backend.
在建立受信任连接之后，应用程序将用户切换到受信任上下文中定义的允许的用户。
After the trusted connection has been established, the application can then switch the user to an allowed user defined in the trusted context.
将MQ应用程序作为受信任对象运行的好处在于，这样可通过缩短的代码路径长度提供性能优势。
The attraction of running an MQ application as trusted is that it gives a performance benefit through reduced code pathlength.
“受信任的代码”在控制区域中运行，用户应用程序代码在服务区域中运行，从而将应用程序执行与事务管理完全隔离。
"Trusted code" runs in the control region, user application code runs in the servant region, which completely isolates application execution and transaction management.
这个受信任的第三方在提供一个到客户机应用程序的PK i接口的同时驻留了XKMS服务。
The trusted third party hosts the XKMS service while providing a PKI interface to the client applications.
通过考虑组件在应用程序结构内的主要使用情况，可以更为恰当地确定数据有效性检查的位置——例如，仅在受管理的信任边界进行检查。
Considering the primary USES of components within application structures leads to more appropriate placement of data validity checking — for example, only at managed trust boundaries.
应用推荐