Developer Transformation Guide

Back Next

Web Service Security

You enable security for web services in a web services connection. You can configure the following types of security:

Web Service Security: The Data Integration Service can include a web service security header when it sends a SOAP request to the web service provider. The web service security header contains authentication information so the web service provider can authenticate the Data Integration Service.
The Web Service Consumer transformation supplies the user name token. The Data Integration Service creates a separate security SOAP header in the SOAP request and passes the request to the web service provider.
You can use the following types of web service security in a web services connection:
PasswordText. The Data Integration Service does not change the password in the WS-Security SOAP header.
PasswordDigest. The Data Integration Service combines the password with a nonce and a time stamp. The Data Integration Service applies a SHA hash on the password, encodes it in base64 encoding, and uses the encoded password in the SOAP header.

Transport layer security: Security implemented on top of the transport layer (TCP layer) of TCP/IP using Secure Sockets Layer (SSL). Web services use Hypertext Transfer Protocol over SSL (HTTPS) as a web address for secure message transport. Web Service Consumer transformations can use TLS 1.2, TLS 1.1, or TLS 1.0. You can use the following authentication with transport layer security: HTTP authentication, proxy server authentication, and SSL certificates.
SSL authentication: You can use SSL authentication when you connect through the HTTPS protocol.; You can use the following types of SSL authentication:
One-way SSL authentication
Two-way SSL authentication

HTTP authentication: You can use HTTP authentication when you connect through the HTTP protocol.; You can use the following HTTP authentication methods:
Basic authentication
Digest authentication
NT LAN Manager (NTLM) authentication