Listing 5: X509 Certificate details.
清单5：x509证书的详细信息。
Standard X509 certificate processing occurs.
标准的X509证书处理流程。
The processing flow for the X509 subscription token
X509订阅令牌符号的的处理流程
Implement the provider-side X509 certificate handler.
实现提供者一方的X509证书处理程序。
Implement the requestor-side X509 certificate handler.
实现请求者方的X509证书处理程序。
Under Type, select X509 issuer name and issuer serial.
在Type下面，选择X509issuernameandissuerserial。
The supported types are Username, Username+password or X509 certificate.
支持的类型为用户名、用户名+密码或X509证书。
The example does not identify that the token is a BASE64-encoded X509 certificate.
这个实例没有识别出令牌符号是以BASE64编码的X509证书。
There are several X509 certificate property accessors on the X509Certificate class.
在 X509Certificate 类中有一些X509证书属性访问器。
Accept applications signed using X509 certificates, as well as those that have BOINC signatures.
认可用X509证书来签名的程序，及有BOINC签名的程序。
It returns an X509 pointer to the certificate or NULL if no certificate was presented (see Listing 1).
它返回一个指向该证书的X509指针，如果证书不存在，就返回NULL(参见清单1)。
Listing 9: Verify that the certificate data represents an X509 token that we issued and that it is still valid.
清单9：检查我们发布的代表X509令牌符号的证书数据是否仍然有效。
Part of this contract is the selection a predefined usage model and the agreement on the certificate standard, like X509.v3.
合同的一部分是选择一个预先定义的使用模型并在诸如x509 . v3的证书标准上达成一致。
The requestor inserts a BASE64-encoded X509 certificate into the header of his message and sends the message to the Gateway Service endpoint.
请求者将以BASE64编码的X509证书加入到他的消息的消息头中，并将消息发送给网关服务端点。
Answer: Version 5.0 provides WS-Security headers with username tokens, x509 certs, identity assertions, dig sigs, and encryption as a Tech Preview.
答：版本5.0为ws - security头提供了用户名令牌、x509证书、身份断言、数字签名和加密作为技术预览。
The provider could use digital signatures and secure service tokens (such as X509 certificates) that they have issued to validate the requestor's entitlements.
服务提供者可以使用数字签名和安全服务令牌符号（例如X509证书），用它们来验证请求者的权利。
There have been demonstrations of binary tokens X509 and Kerberos tickets being passed, but the infrastructure to make use of those at either end is largely hand coded.
我们已经看到过传送二进制令牌X509和Kerberos票据的演示，但在任一端使用那些东西的基础架构都主要是用手工编码的。
WebSphere Application Server V5 provides support for username token, X509, identity assertion, signatures and encryption as "technical previews", meaning that they are not supported.
WebSphereApplicationServerV5提供了对用户名令牌、X509、身份断言、签名和加密的支持作为“技术预览”，这表示它们还没有得到正式支持。
WebSphere Application Server V5 provides support for username token, X509, identity assertion, signatures and encryption as "technical previews", meaning that they are not supported.
WebSphereApplicationServerV5提供了对用户名令牌、X509、身份断言、签名和加密的支持作为“技术预览”，这表示它们还没有得到正式支持。
应用推荐