Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging and Reporting
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. DTLDESCRIBE Metadata
  12. PowerExchange Globalization
  13. Using the PowerExchange ODBC Drivers
  14. PowerExchange Datatypes and Conversion Matrix
  15. Appendix A: DTL__CAPXTIMESTAMP Time Stamps
  16. Appendix B: PowerExchange Glossary

SSL_ALLOW_SELFSIGNED Statement

SSL_ALLOW_SELFSIGNED Statement

The SSL_ALLOW_SELFSIGNED statement specifies the type of certificate to use for SSL security.
You can use either self-signed certificates or certificates signed by a commercial certificate authority that the system trusts. Any certificate, regardless of whether it is self-signed or signed by a trusted CA, must have its CA in the CALIST file or CA hash in the CAPATH directory. This statement is also used when establishing a secure TLS connection to an LDAP server for credentials checking to handle situations where the certificates from the LDAP server are self-signed.
Linux, UNIX, and Windows
SSL, SSL_REQ_CLNT_CERT, and SSL_REQ_SRVR_CERT
No
SSL_ALLOW_SELFSIGNED={
N
|Y}
  • N
    .
    Uses certificates from a commercial certificate authority (CA) that the system trusts.
  • Y.
    Uses self-signed certificates. Self-signed certificates are not verifiable by following the chain to a trusted certificate authority. Self-signed certificates are for internal use only, such as for connections within your organization's network or for internal testing.
    If you specify SSL_ALLOW_SELFSIGNED=Y with OPENLDAP credentials checking and also specify the LDAP_TLS statement with the START_TLS=Y parameter, self-signed certificates from the LDAP server are tolerated and credentials checking proceeds.
Default is N.
You might want to include the SSL_CIPHER_LIST statement in the DBMOVER file on the client machine for the following reasons:
  • Configure the SSL_ALLOW_SELFSIGNED, SSL_CIPHER_LIST, or SSL_CONTEXT_METHOD statement only if a failure connecting to the LDAP server occurs.
  • On Windows, setting the trace filter TRACE=(SEC,9,99) causes low-level tracing in the Open LDAP client libraries, which can provide information about whether the connection to the LDAP server failed because of correctable errors such as self-signed certificates, no ciphers shared between the client and server, or context method mismatches between the client and server.
  • Informatica recommends using the strongest TLS protocol supported on both the client and server systems. OpenLDAP libraries 2.5.18 support TLS protocol TLSV1_3. If the LDAP server does not support TLS protocol TLSV1_3, configure the SSL_CONTEXT_METHOD statement in the Windows dbmover.cfg to specify the strongest TLS protocol supported by the LDAP server, for example, SSL_CONTEXT_METHOD=TLSv1_2.

0 COMMENTS

We’d like to hear from you!