To enforce a stronger Internet password policy, you can develop a custom authentication Domino Security API (DSAPI) filter, or use an LDAP directory for authentication.
要实施更强的互联网口令策略，可以开发定制的身份验证DominoSecurity API (DSAPI)过滤器，或者可以依据LDAP目录进行身份验证。
The main advantage of using the GSS-API is that by writing to this generic API, your implementation can interoperate with various security systems.
使用GSS - API的主要优点是，通过使用这种通用API编写代码，您的实现可以与不同的安全性系统互操作。
You authenticate to the API using security credentials.
使用安全凭证验证到这个API。
Thus, a secure application developed using GSS-API can work over different security mechanisms without changes to the application.
因此，用GSS - API开发的安全应用程序可以在不同的安全机制上运行，不用改变应用程序。
This article takes you further with information about the new GSS-API security mechanisms.
本文将进一步介绍有关新的GSS-API安全机制的信息。
With GSS-API, these systems can be designed to make use of different underlying security mechanisms for different factors of the multifactor authentication.
通过使用GSS - API，系统可以对多因素身份验证的不同因素使用不同的底层安全机制。
Typically, in GSS-API a secure connection between two communicating applications is represented by a data structure called a security context.
在GSS - API中，两个相互通信的应用程序之间的安全连接通常由一个称为安全上下文的数据结构表示。
GSS-API enables application control over security.
GSS - API允许应用程序控制安全。
It then describes how you can achieve authentication based on public key technology, using the new GSS-API security mechanisms with the customizable DB2 UDB security plug-ins.
然后还将描述：如何通过使用新的具有可定制的DB 2UDB安全插件的GSS - API安全机制来实现基于公钥技术的身份验证。
Essentially, security administrators can code to the GSS-API and implement virtually any supported security mechanism that supports this interface.
本质上是，安全管理员可以对于GSS -API进行编码，并真正实现支持该接口的、受支持的安全机制。
Finally, it recommends the use of GSS-API (available with most UNIX operating systems like AIX) to help achieve readiness to incorporate newer security mechanisms.
最后，建议使用GSS - API(在包括AIX在内的大多数UNIX操作系统上都有的api)帮助纳入新的安全机制。
About cross-domain limitation, the cross Document Messaging API is interesting to allow cross-origin communication but the developer as to be very careful using it and ensure security at all time.
至于跨域的限制，跨文档进行消息传输的API非常有趣的允许跨源(cross -origin)通信，但是开发者需要非常小心的使用它，在任何时候确保安全性。
Apache Shiro provides something unique in the world of security frameworks: a consistent Session API usable in any application and any architectural tier.
在安全框架领域，ApacheShiro提供了一些独特的东西：可在任何应用或架构层一致地使用SessionAPI。
In other words, IBM's Kerberos support is provided as a GSS-API security plug-in, which you can use for both server and client authentication.
换言之，IBM的Kerberos支持是作为一个GSS - API安全插件来提供的，您可将该插件用于服务器身份验证和用户身份验证。
Amazon EC2 calls these instances security groups and has API calls and commands to manipulate them.
AmazonEC2调用这些安全组并使用API调用和命令来操作它们。
Kerberos is the most popular underlying security mechanism available with GSS-API.
Kerberos是通过GSS - API使用的最流行的底层安全机制。
The key point here is that Shiro's API is largely intuitive because it reflects the natural tendency for developers to think in 'per-user' security control.
这里的关键点是Shiro的API非常直观，因为它反映了开发者以‘每个用户’思考安全控制的自然趋势。
But imagine the potential if Apple could build a biometrics API that could allow other applications on the PC and Mac to use the iPhone as second factor, biometric security device.
不过想想下面这种可能性-苹果建立一个生物识别的API，允许PC或者Mac上的其他程序调用，以使用iPhone作为第二要素-生物识别安全设备。
Using the WebSphere Process Server Web service API involves a number of steps, such as copying key artifacts, generating the proxy clients, and ensuring security.
使用WebSphereProcessServerWeb服务API涉及许多步骤，比如复制关键工件、生成代理客户机和确保安全性。
As of today, the only security mechanism supported by most of the GSS-API offerings is the popular symmetric key-based mechanism called Kerberos [IETF RFC-1964].
到目前为止，大部分GSS - API产品所支持的惟一的安全机制就是名为kerberos [ietfRFC - 1964]的流行的基于对称密钥的机制。
On the DB2 UDB client: a LIPKEY-enabled client-side GSS-API security plug-in.
在DB2UDB客户机中：一个支持 LIPKEY 的客户端GSS-API安全插件。
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安全插件。
Note: You need gssapiDB2.h only if you are implementing the GSS-API-based security plug-in.
注意：只有在实现基于 GSS-API 的安全性插件时才需要gssapiDB2.h。
Not all the improvements in Tomcat 7 are down to the Servlet 3.0 API. Tomcat also sees a number of important security improvements.
Tomcat7中的改进也不是全都针对Servlet 3.0API的，其中还有不少重要的安全性改进。
After you have installed the Lotus Sametime Unified Telephony API, you need to complete some configuration steps to configure security for the application.
安装好LotusSametimeUnifiedTelephonyAPI后，您需要完成一些配置步骤来为应用程序配置安全性。
In fact, the IBM-supplied sample Kerberos security plug-in for DB2 UDB is based on GSS-API.
事实上，ibm为db2UDB提供的示例Kerberos安全插件是基于GSS - API的。
The GSS-API default behavior will be to initiate the context for Kerberos security mechanism.
GSS-API 的默认行为是为Kerberos安全机制启动上下文。
As you can see in the above figures, the authentication is achieved by exchange of GSS-API tokens, which is very typical with the GSS-API security model. The key points to notice here are.
由上面两图可知：身份验证是通过交换GSS - API令牌来实现，这对于GSS - API安全模型非常典型。
Write customized GSS-API security plug-ins that will support SPKM/LIPKEY security mechanisms.
编写支持SPKM/LIPKEY安全机制的定制的GSS-API 安全插件。
Simple authentication and Security layer (SASL) is an API that provides an abstraction layer for authentication protocols.
简单身份验证和安全层(SASL)是一种为身份验证协议提供抽象层的API。
应用推荐