Listing 3 includes only one provider, the LDAP authentication provider.
清单3只包含了一个提供者，即LDAP身份验证提供者。
In this document we are focussing on a full authentication provider.
在本文档中，我们主要关注完整的身份验证提供者。
Listing 4 shows the configuration for the LDAP authentication provider.
清单4展示了LDAP身份验证提供者的配置。
The LDAP authentication provider transfers control to the populator bean.
LDAP身份验证提供者将控制权传递给populatorbean。
The populator returns the role information to the LDAP authentication provider.
populator 将用户角色信息返回给LDAP身份验证提供者。
The authenticator sends the user information back to the LDAP authentication provider.
authenticator将用户信息发送回LDAP身份验证提供者。
The user cache service returns the details of the user to the authentication provider.
usercacheservice将用户的详细信息返回给身份验证提供者。
There are four possible ways to pass logon data in a request to the authentication provider.
把请求中的登录数据传递给身份验证提供者有四种方法。
The LDAP authentication provider handles all communication with your back-end LDAP directory.
LDAP身份验证提供者处理所有与后端ldap目录的通信。
There are three types of exceptions which an IBM Cognos 8 Authentication Provider can return.
IBMCognos8身份验证提供者可以返回三种异常。
The AuthProviderSpecificID is an id that is constructed internally by the authentication provider.
AuthProviderSpecificID是身份验证提供者在内部构造的id。
The authentication provider checks whether the cache service returned details of the user or null.
身份验证提供者检查缓存服务返回的是用户的详细信息还是null。
This provider will consume some token and deduct logon data consumable by an Authentication provider from it.
这种提供者接受某个令牌并从中推导出身份验证提供者可使用的登录数据。
If a match is found, the authentication provider returns the details of the user to the authentication manager.
如果找到一个匹配，身份验证提供者将用户的详细信息返回给身份验证管理器。
The assumption is that this token is not consumable by any other IBM Cognos 8 authentication provider directly.
假设任何其他IBMCognos8身份验证提供者都无法直接使用这种令牌。
The JDBCSample was chosen for this document only because it's the only example of a full authentication provider.
本文档选用JDBCSample作为示例只是因为它是完整身份验证提供者的惟一示例。
This feature allows an authentication provider to request additional information from either the user or the system.
这个特性让身份验证提供者能够向用户或系统请求更多信息。
Since our application manages Speaker entities, we should build a custom authentication provider that uses Speaker data.
由于我们的应用程序管理Speaker实体，我们应当建立一个使用 Speaker数据的自定义认证提供程序。
An internal authentication provider is used to implement this functionality which is neither visible nor configurable.
使用一个内部身份验证提供者实现此功能，它是不可见的，也不可配置。
The CAMID is constructed by the authentication provider for each object read in from an external authentication provider.
对于从外部身份验证提供者读取的每个对象，由身份验证提供者构造CAMID。
For each namespace, a visa is issued by the authentication provider after successful authentication has been established.
对于每个名称空间，在成功完成身份验证之后，身份验证提供者都会颁发一个visa。
When receiving a TC an authentication provider will not verify their origin or consistency explicitly but implicitly only.
当收到TC 时，身份验证提供者并不显式地检验其来源或一致性，只隐式地检验。
The Roo-generated Spring Security shown above uses an in-memory authentication provider configured under the <user-service> tag.
如上 Roo生成的 SpringSecurity 在
The LDAP authentication provider returns details of the user (along with information about user's business roles) back to APF.
LDAP身份验证提供者将用户的详细信息(以及用户业务角色信息)返回给APF。
For example, an authentication processing filter requires an authentication manager to select an appropriate authentication provider.
比如，一个身份验证处理过滤器需要一个身份验证管理器选择一个合适的身份验证提供者。
The authentication provider extracts the username from the authentication token and passes it to a service called user cache service.
身份验证提供者支持从身份验证标记中提取用户名，并将它发送给名为usercacheservice的服务。
This also applies to the internal authentication provider, so all the objects of the IBM Cognos namespace have a CAMID assigned to them.
这也适用于内部身份验证提供者，所以IBMCognos名称空间的所有对象都有分配给它们的CAMID。
If the cache returned null, the authentication provider passes the username (extracted in Step 6) to another service called user details service.
如果缓存返回null，身份验证提供者将用户名(在步骤6中提取)发送给另一个名为user details service的服务。
An authentication provider has to support at least one method of authentication, possibly multiple and it can support single sign-on support as well.
身份验证提供者必须支持至少一种身份验证方法，很可能支持多种方法，还可以支持单点登录。
Using cookies should be handled in a TSP really which then passes on to a full authentication provider which uses REMOTE_USER based SSO as demonstrated here.
实际上应该在TSP中处理cookie，然后传递给使用基于 REMOTE_USER 的SSO 的完整身份验证提供者。
应用推荐