Connection Authentication Support

Connection authentication performs the following actions.

1. Calls a user-authentication routine, which issues the challenge in the form of a generated key

2. Sends the generated key to the prospective "client"

3. Calls a user-response at the client, which must reply with the correct response

4. Calls a user hook again when the response data is returned to the server-side, which can either allow or disallow the connection, based on the response

Authentication is enabled by default, using the JADE-supplied default library and authentication hooks. If you want to avoid enforcement of the authentication protocol, you must manually disable authentication in the JADE initialization file at the server.

When connection authentication is enabled:

• JADE looks in the [JadeSecurity] section of the JADE initialization file for the name of a user-defined authentication library (DLL).

  For details, see "JADE Security Section [JadeSecurity]", in the JADE Initialization File Reference.

• The JADE RPC module dynamically loads the authentication DLL by a LoadLibrary call during initialization and attempts to obtain the address of predefined functions by name, using GetProcAddress.

• On a remote access-capable node, if the dynamic load fails, an exception is logged in the JADE event log and remote access provider support is disabled, preventing any clients from connecting.

JADE invokes the Authentication Challenge hook, Authentication Response hook, and Authentication Verification hook described in the following subsections only if the authentication feature is enabled. Your site-supplied library must export all three hook functions to enable correct operation of authentication support.