English
  • PowerCenter 10.2 HotFix 2
  • All Products

Table of Contents

Search

  1. About the Security Guide
  2. Introduction to Informatica Security
  3. User Authentication
  4. LDAP Security Domains
  5. Kerberos Authentication
  6. Domain Security
  7. SAML Authentication for Informatica Web Applications
  8. Security Management in Informatica Administrator
  9. Users and Groups
  10. Privileges and Roles
  11. Permissions
  12. Audit Reports
  13. Command Line Privileges and Permissions
  14. Custom Roles
  15. Default List of Cipher Suites

Security Guide

Security Guide

Back Next

Requirements for Secure Communication within the Domain

Requirements for Secure Communication within the Domain

Before you enable secure communication within the domain, ensure that the following requirements are met:
You created a certificate signing request (CSR) and private key.
You can use keytool or OpenSSL to create the CSR and private key.
If you use RSA encryption, you must use more than 512 bits.
You have a signed SSL certificate.
The certificate can be self-signed or CA signed. Informatica recommends a CA signed certificate.
You imported the certificate into keystores.
You must have a keystore in PEM format named
infa_keystore.pem
 and a keystore in JKS format named
infa_keystore.jks
.
The password for the keystore in JKS format must be the same as the private key pass phrase used to generate the SSL certificate.
You imported the certificate into truststores.
You must have a truststore in PEM format named
infa_keystore.pem
 and a keystore in JKS format named
infa_keystore.jks
.
The keystores and truststores are in the correct directory.
If you enable secure communication during installation, the keystore and truststore must be in a directory that is accessible to the installer.
If you enable secure communication after installation, the keystore and truststore must be in a directory that is accessible to the command line programs.
Important:
 If you push processing to a compute cluster and the Data Integration Service runs on a grid, import the certificates one time and then copy them to each Data Integration Service on the grid. Each time you import a certificate, the contents of the certificate are identical, but the hex values are different. As a result, concurrent mappings that run on the grid fail with initialization errors.
For more information about how to create a custom keystore and truststore, see the Informatica How-To Library article How to Create Keystore and Truststore Files for Secure Communication in the Informatica Domain: https://kb.informatica.com/h2l/HowTo%20Library/1/0700-CreateKeystoresAndTruststores-H2L.pdf
After you secure the domain, configure the Informatica client applications to work with a secure domain.