Third-party applications or intermediate code

When using authentication, it is the responsibility of the application to handle any challenges that originate from the authentication server.

To handle the challenges, the application programmer must be able to register a callback function with the driver. Because there are no attributes defined in the ODBC standard that are used to accomplish this, the attributes used are HCL OneDB™ extensions.

Many applications are written with ADO layer of Microsoft™ to abstract the ODBC calls from the developer. Most Visual Basic applications are written with ADO objects. These applications and third-party applications in general are not aware of the HCL OneDB extensions and are not able to handle an authentication challenge.

The ODBC Data Source Administrator on Windows™ also falls under the class of third-party applications. Not all features are available when configuring a UNIX™ data source. For example, the Apply and Test Connection button and the User Server Database Locale toggle does not work if a challenge is received because those features require the ability to connect to the server.