Configuring core application authentication with ContactManager

When you integrate a Guidewire core application with ContactManager, you register a plugin implementation with the core application’s plugin registry. For example, to integrate ContactManager 10.0 with a core application of the same release, you register gw.plugin.contact.ab1000.ABContactSystemPlugin with the core application’s ContactSystemPlugin.gwp registry.

Each core application defines a user name and password that it uses to authenticate with ContactManager when the application uses its plugin to call ABContactAPI methods. The definition is in the class wsi.remote.gw.webservice.ab.ABConfigurationProvider. For security purposes, Guidewire recommends that you define your own user names and passwords.

• ClaimCenter defines the two authentication parameters, username and password, as ClientAppCC and gw.
• PolicyCenter defines the two authentication parameters, username and password, as ClientAppPC and gw.
• BillingCenter defines the two authentication parameters, username and password, as su and gw.

The base ContactManager application’s sample code contains users with names and passwords that match the default settings in the core applications. The sample code has users with names ClientAppCC, ClientAppPC, and su, all with password gw.

Guidewire recommends that you change the username and password that each application uses to authenticate with ContactManager when making calls to ABContactAPI. The process, which is similar for all applications, follows:

1. Set up a user and password in ContactManager to match the user name and password you define in the core application.
2. Define the user name and password in the core application’s ABConfigurationProvider class.