Authentication module deployment
When you use authentication modules, you must consider the following
issues:
Implicit connections with authentication modules Authentication responses to authentication modules, such as PAM and LDAP, expect a password. However, in implicit connections to the database server, there is no password.Application development for authentication modules The authentication method depends on the PAM or LDAP Authentication Support module installed.Distributed transactions and authentication modules When HCL OneDB initiates a distributed connection after the session is established, it cannot respond to authentication challenges because the timing is unpredictable. Also, the password required to connect to the local server might not be the same as the password required to connect to the remote server. Consequently, authentication for distributed connections must be completed by the remote server on the basis of trust. The remote server must trust the local server and the remote administrators must explicitly permit the user to connect from the local server to the remote server.Client APIs and authentication support modules Only specific HCL OneDB client APIs support PAM and LDAP Authentication Support modules. To use the other APIs when an authentication module is enabled on HCL OneDB , you can connect to a DBSERVERALIASES .Compatibility issues with authentication modules Only specific HCL OneDB products support authentication modules. To use the other products when an authentication module is enabled on HCL OneDB , you can connect to a DBSERVERALIASES .
Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.