For LIPKEY-based authentication, you will typically need.
为了进行基于LIPKEY的身份验证，通常需要。
On the DB2 UDB client: a LIPKEY-enabled client-side GSS-API security plug-in.
在DB2UDB客户机中：一个支持 LIPKEY 的客户端GSS-API安全插件。
High-level view of DB2 UDB authentication using the LIPKEY security mechanism.
使用LIPKEY安全机制的DB 2UDB身份验证的高级视图。
Write customized GSS-API security plug-ins that will support SPKM/LIPKEY security mechanisms.
编写支持SPKM/LIPKEY安全机制的定制的GSS-API 安全插件。
This typically will be documented in detail by the GSS-API offering that supports LIPKEY mechanism.
通常，这将由支持LIPKEY 机制的 GSS-API 产品进行详细记载。
The most important security mechanisms available under NFSv4 include Kerberos version 5 and LIPKEY.
NFSv4中提供的最重要的安全机制包括Kerberos版本5和LIPKEY。
The overview of the SPKM and LIPKEY mechanisms given below will provide an insight to what it offers to applications.
下文对SPKM和LIPKEY机制的概述，有助于了解其为应用程序带来的好处。
On the DB2 UDB server: an X.509 certificate, a PKI environment, and a LIPKEY-enabled server-side GSS-API security plug-in.
在DB2UDB服务器中：一张 X.509证书，一个PKI环境，以及一个支持 LIPKEY 的服务器端GSS-API安全插件。
In this protocol, the client-server interactions are secured using GSS-API framework offered by Kerberos, LIPKEY, and SPKM-3.
在这个协议中，使用Kerberos、LIPKEY和SPKM - 3提供的GSS - API框架保护客户端和服务器之间的交互。
The LIPKEY mechanism can be used when the initiator (client) does not have a certificate and instead USES a user ID and password for authentication.
当发起者(客户机)没有证书而是使用用户ID和口令进行验证身份时，就可以使用LIPKEY机制。
The prime reason for this increased support is that the NFS V4 [IETF RFC-3530] has mandated the use of SPKM and LIPKEY security mechanisms for its security module.
这种支持增长的主要原因是，NFSV4 [IETFRFC-3530]强制规定其安全模块使用SPKM和LIPKEY 安全机制。
As mentioned in IETF RFC 2847, LIPKEY is a low infrastructure based GSS-API security mechanism which maps to a typical TLS (Transport Layer security) deployment scenario.
正如在IETFRFC 2847中所提到的，LIPKEY是一种基于GSS - API安全机制的低基础设施，该安全机制对应于典型的TLS (TransportLayerSecurity)部署场景。
Thus the above requirement will force vendors to extend their GSS-API framework to support SPKM and LIPKEY in addition to Kerberos, which will continue be the default GSS-API mechanism.
因此，上述要求会迫使供应商扩展GSS - API框架，以支持Kerberos之外还支持SPKM和LIPKEY，而Kerberos将继续作为默认的GSS - API机制。
For the LIPKEY mechanism in particular, during the execution of db2secGenerateInitialCred , the client will be prompted for a user id and password, which will be used for client side authentication.
尤其对于LIKEY机制而言，在执行db2secgenerateinitialcred的过程中，客户将被要求输入用户ID和口令，以用于客户端身份验证。
For the LIPKEY mechanism in particular, during the execution of db2secGenerateInitialCred , the client will be prompted for a user id and password, which will be used for client side authentication.
尤其对于LIKEY机制而言，在执行db2secgenerateinitialcred的过程中，客户将被要求输入用户ID和口令，以用于客户端身份验证。
应用推荐