![]() |
Refresh Authentication
|
|
A Refresh Authentication Model for Single-Corporate-Entity SystemsWithin 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( 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 IDFor single corporate entities, you typically provide user IDs in one of the following ways:
Providing the PasswordFor single corporate entities, you typically provide passwords in the following way:
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. |
|
![]() Cloudscape Version 3.6 For information about Cloudscape technical support, go to: www.cloudscape.com/support/.Copyright © 1998, 1999, 2000 Informix Software, Inc. All rights reserved. |