Security Guide > Domain Security > Secure Sources and Targets
  

Secure Sources and Targets

Informatica uses connection objects to connect to relational databases as source or target. You can create a connection object to a relational database that is secured with an SSL certificate.
You create PowerCenter connection objects in the Workflow Manager. You create Data Service , Data Quality, or Profiling connections in the Developer tool or in the Administrator tool.
You can create a connection to a secure source or target on the following databases:

Data Integration Service Sources and Targets

When you create a connection object for the Data Integration Service to process mappings, data profiles, scorecards, or SQL data services, you can define a connection to a database secured with the SSL protocol.
The Data Integration Service connects to the source or target database through JDBC drivers. When you configure the connection to a secure repository database, you must include the secure connection parameters in the JDBC connection string.
    1. Set up a database secured with the SSL protocol to use as a source or target.
    2. In the Administrator tool, create a connection.
    3. In the New Connection dialog box, select the connection type. and click OK.
    You can create a connection to a secure DB2, Microsoft SQL Server, or Oracle database.
    4. In the New Connection - Step 1 of 3 dialog box, enter the properties for the connection and click Next.
    5. In the New Connection - Step 2 of 3 page, enter the connection string to the database.
    To connect to a secure database, enter the secure database parameters in the Advanced JDBC Security Options field. Informatica treats the value of the Advanced JDBC Security Options field as sensitive data and stores the parameter string encrypted.
    The following list describes the secure database parameters:
    EncryptionMethod
    Required. Indicates whether data is encrypted when transmitted over the network. This parameter must be set to SSL.
    ValidateServerCertificate
    Optional. Indicates whether Informatica validates the certificate that the database server sends.
    If this parameter is set to True, Informatica validates the certificate that the database server sends. If you specify the HostNameInCertificate parameter, Informatica also validates the host name in the certificate.
    If this parameter is set to False, Informatica does not validate the certificate that the database server sends. Informatica ignores any truststore information that you specify.
    Default is True.
    HostNameInCertificate
    Optional. Host name of the machine that hosts the secure database. If you specify a host name, Informatica validates the host name included in the connection string against the host name in the SSL certificate.
    TrustStore
    Required. Path and file name of the truststore file that contains the SSL certificate for the database.
    TrustStorePassword
    Required. Password for the truststore file for the secure database.
    Note: Informatica appends the secure JDBC parameters to the connection string. If you include the secure JDBC parameters directly to the connection string, do not enter any parameters in the Advanced JDBC Security Options field.
    6. Test the connection to verify that the connection to the secure database is valid.
    7. Complete the process to create the relational connection.

PowerCenter Sources and Targets

When you create a connection object for a PowerCenter session, you can define a connection to a database secured with the SSL protocol.
You can connect to relational PowerCenter sources and targets through native connectivity or ODBC drivers.
If you connect to a secure relational source or target through native connectivity, verify that the database client contains the connection information for the secure database. For example, if you connect to a PowerCenter target on a secure Oracle database, configure the Oracle database client file tnsnames.ora with the connection information for the secure database.
If you connect to a secure relational source or target through ODBC drivers, verify that the database client contains the connection information for the secure database and the ODBC data source correctly defines the connection to the secure database.