GSS-API is a standard that DB2 supports.
GSS - API是DB 2所支持的一个标准。
GSS-API enables application control over security.
GSS - API允许应用程序控制安全。
DB2 UDB Authentication using newer supported GSS-API mechanism.
使用较新的受支持的GSS - API机制的DB 2UDB身份验证。
Because of this limitation, GSS-API has not been potentially used.
由于有这个限制，往往不使用GSS - API。
Scenario 1: Use of down-level and upgraded clients with GSS-API plug-in.
场景1：未升级和升级的客户机对GSS - API插件的使用。
On the DB2 UDB client: a LIPKEY-enabled client-side GSS-API security plug-in.
在DB2UDB客户机中：一个支持 LIPKEY 的客户端GSS-API安全插件。
Almost all UNIX operating systems, including AIX, support and provide GSS-API.
大多数UNIX操作系统(包括AIX)都支持和提供GSS - API。
Kerberos is the most popular underlying security mechanism available with GSS-API.
Kerberos是通过GSS - API使用的最流行的底层安全机制。
For GSS-API or Kerberos, this is the password that is used to get the user credential.
对于GSS - API或Kerberos，这是用于获得用户凭证的密码。
There are other forms of credentials, depending on the specific GSS-API implementation.
还有其他形式的凭证，这取决于特定的GSS-API实现。
This article takes you further with information about the new GSS-API security mechanisms.
本文将进一步介绍有关新的GSS-API安全机制的信息。
In fact, the IBM-supplied sample Kerberos security plug-in for DB2 UDB is based on GSS-API.
事实上，ibm为db2UDB提供的示例Kerberos安全插件是基于GSS - API的。
Note: You need gssapiDB2.h only if you are implementing the GSS-API-based security plug-in.
注意：只有在实现基于 GSS-API 的安全性插件时才需要gssapiDB2.h。
Using these GSS-API interfaces, you can implement secure Keberized applications and systems.
通过使用这些GSS - API接口，可以实现使用Kerberos机制的安全应用程序和系统。
Write customized GSS-API security plug-ins that will support SPKM/LIPKEY security mechanisms.
编写支持SPKM/LIPKEY安全机制的定制的GSS-API 安全插件。
The GSS-API default behavior will be to initiate the context for Kerberos security mechanism.
GSS-API 的默认行为是为Kerberos安全机制启动上下文。
The server ID and password are sent in a GSS token, and are produced and consumed using the JGSS API.
服务器ID和密码在GSS令牌中发送，并使用JGSSAPI产生和使用。
This typically will be documented in detail by the GSS-API offering that supports LIPKEY mechanism.
通常，这将由支持LIPKEY 机制的 GSS-API 产品进行详细记载。
The server ID and password are sent in a GSS token, which is produced and consumed using the JGSS API.
在gss令牌中发送服务器ID和密码，而GSS令牌由JGSSAPI产生和使用。
SPKM is a GSS-API mechanism which is based on a public key rather than a symmetric key infrastructure.
SPKM是一种GSS - API机制，其基于公钥而非对称密钥基础设施。
A programmer using GSS-API can write an application that is ignorant of the details of protecting network data.
使用GSS - API的程序员编写的应用程序可以不知道关于保护网络数据的细节。
The GSS-API is fully described in RFC 2743, which, unfortunately, is among the most difficult RFCs to understand.
GSS-API 在RFC 2743 中进行了完整的描述，不幸的是，它是最难理解的 RFC 之一。
Table 8 shows the steps involved in a client-server flow when DB2 is involved in the GSS-API authentication process.
表8展示了在GSS-API 身份验证过程中涉及DB2时客户机 - 服务器之间流程中的步骤。
Kerberos-based authentication modules are implemented directly using a Kerberos API or by using the GSS-API interface.
基于Kerberos的身份验证模块可以用KerberosAPI直接实现，也可以使用GSS - API接口实现。
If a client has more than one GSS-API plug-in copied, the server determines which one to use, based on the ordered list.
如果客户机上复制了不只一个GSS - API插件，那么服务器将根据这个有序列表来确定使用哪个插件。
Table 7 provides a simplified illustration of the basic client-server flows involved in the GSS-API authentication process.
表7简单地解释了在GSS-API身份验证过程中客户机 - 服务器之间的基本流程。
So for applications that need to have a GSS-API mechanism which is based on a public-key infrastructure, SPKM is the answer.
因此，当应用程序需要一种基于公共密钥基础设施的GSS-API机制时，SPKM 就能满足它的要求。
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框架保护客户端和服务器之间的交互。
On successful establishment of a GSS-API context, it is concluded that the user identification has been successfully verified.
成功地建立GSS - api上下文之后，就可以认为已经成功地检验了用户身份。
Table 5 shows the steps you would take to enable GSS-API authentication plug-ins using the above listed configuration parameters.
表5展示了使用前面列出的配置参数启用GSS - API身份验证插件的步骤。
应用推荐