SOAP Credentials

The built-in soapCredential Protocol is used to authenticate users against servers providing web services. This Credential Protocol is also used to count the number of remote servers for licensing. The Endpoint must match the FQDN of the server providing the web services. If no authentication is required, the username and password are ignored, but they must always be set. You can use dummy in this case to indicate that authentication is not required.

To prevent authentication headers from being sent to the web service, you can use the {redwood}:nocredential syntax in the Run As User field. In your Job Definition source, you can also use req.setAuthentication(SOAPRequest.REDWOOD_NOCREDENTIAL, null).

SOAP definitions use HTTP Credentials for proxies.

Example Proxy Credential

The following proxy configuration is used for all SOAP servers serving on port 80.

Field	Value
Protocol	login
Real User	jdoe
Password	***
Endpoint	proxy.masalan.com
Virtual User	proxy:*:80

The following proxy configuration is used for all SOAP servers serving on port 443. This proxy server does not require a username, only a password.

Field	Value
Protocol	login
Real User	forceNone
Password	***
Endpoint	sproxy.masalan.com
Virtual User	proxy:*:443