Refresh Authentication
Page 3 of 7

A Refresh Authentication Model for Single-Corporate-Entity Systems

Within a single-corporate entity, you can configure your system so that targets must present user IDs and passwords that are valid in the source database.

When user authentication is turned on, for a standard JDBC connection users must present a user ID and a password as part of the connection request, as shown in the following example:

Connection conn = DriverManager.getConnection(
"jdbc:cloudscape:myDB", "mary", "little7xylamb");

Refresh requests make similar behind-the-scenes JDBC connection attempts. When user authentication is turned on at the source, refresh requests must provide valid user IDs and passwords. Since these connection attempts happen behind the scenes, how do you configure your system so that the refresh request provides the user ID and password?

Providing the User ID

For single corporate entities, you typically provide user IDs in one of the following ways:

  • Set the user property within the PROPERTIES clause of the REFRESH command.

    The target can set a property user in the PROPERTIES clause of the REFRESH command. For example:

    REFRESH PROPERTIES user = "mary"

    For more information, see The REFRESH Command.

  • Let the source use the target database user ID

    If the user provides a user ID to connect to the target database (which would be required if user authentication is turned on at the target), you can configure the system so that Cloudscape simply passes along this user ID to the refresh request.

    This is the default behavior if:

Providing the Password

For single corporate entities, you typically provide passwords in the following way:

  • Within the PROPERTIES clause of the REFRESH command.

    The target can set a property password in the PROPERTIES clause of the REFRESH command along with the user ID. For example:

    REFRESH PROPERTIES user = "mary", password = "little7xylamb"

    For more information, see The REFRESH Command.

NOTE: Unlike the user ID, there is no way to configure your system so that Cloudscape passes along the password provided in the target's JDBC connection to the refresh request.