Note: | Note that if Mediator is used to access a native API protected by NTLM (which is typically hosted in IIS), then the native API in IIS should be configured to use NTLM as the authentication scheme. If the authentication scheme is configured as “Windows”, then “NTLM” should be in its list. |
Authenticate Using | String. Specifies the user credentials for authenticating client requests to the native API.
| ||||
Value | Description | ||||
Existing Credentials | Default. Mediator uses the user credentials passed in the request header for an NTLM handshake with the server. | ||||
Custom Credentials | Mediator uses the values you specify in the User, Password and Domain fields for an NTLM handshake with the server. | ||||
Field | Description | ||||
Username | String. Mandatory. Account name of a consumer who is available in the Integration Server on which Mediator is running. | ||||
Password | String. Mandatory.A valid password of the consumer. | ||||
Domain | String. Optional. Domain used by the server to authenticate the consumer. | ||||
Transparent | Mediator supports Kerberos handshake in Transparent mode. The following additional settings are required for Kerberos: Configure the client with clientCredentialType set to Windows. Set the value of watt.pg.disableNtlmAuthHandler property to true in the extended settings for the Integration Server Set the property handleClientErrorCode to true in pg-core.xml as follows: <bean id="httpResponseCodeCallback" class="com.softwareag.pg.axis2.transpo rts.ISHTTPResponseCodeCallback"> <property name="handleClientErrorCode" value="true"/> </bean> For more information about configuring the extended settings, see webMethods Integration Server Administrator’s Guide. |