SSIS Components for FinancialForce

Build 20.0.7656

Advanced Settings

Customizing the SSL Configuration

By default, the component attempts to negotiate SSL/TLS by checking the server's certificate against the system's trusted certificate store. To specify another certificate, see the SSLServerCert property for the available formats to do so.

Connecting Through a Firewall or Proxy

HTTP Proxies

To connect through the Windows system proxy, you do not need to set any additional connection properties. To connect to other proxies, set ProxyAutoDetect to false.

In addition, to authenticate to an HTTP proxy, set ProxyAuthScheme, ProxyUser, and ProxyPassword, in addition to ProxyServer and ProxyPort.

Other Proxies

Set the following properties: Set FirewallType, FirewallServer, and FirewallPort. To tunnel the connection, set FirewallType to TUNNEL. To authenticate specify FirewallUser and FirewallPassword. To authenticate to a SOCKS proxy, additionally set FirewallType to SOCKS5.

Authenticating with SSO

The component supports SSO authentication through the OneLogin, PingFederate, and OKTA identity providers. All identity providers require the following common connection properties. You can find the values for the following properties in the FinancialForce account settings by navigating to Administration Setup > Security Controls > SAML Single Sign-On and then choosing the desired organization.

  • SSOLoginUrl: Set to your SSO endpoint, as shown in the following examples:
    • OneLogin:
      https://app.onelogin.com/saml/metadata/123455
    • PingFederate:
      https://myssoendpoint/idp/sts.wst
  • SSOTokenUrl: Set to your FinancialForce OAuth 2.0 token endpoint for SSO. For example:
    https://mysite.salesforce.com/services/oauth2/token?so=1234567

You also need to specify other properties specific to the identity provider in SSOProperties. See SSOProperties in Connection String Options for more details.

Troubleshooting the Connection

To show component activity from query execution to network traffic, use Logfile and Verbosity. The examples of common connection errors below show how to use these properties to get more context. Contact the support team for help tracing the source of an error or circumventing a performance issue.

  • Authentication errors: Typically, recording a Logfile at Verbosity 4 is necessary to get full details on an authentication error.
  • Queries time out: A server that takes too long to respond exceeds the component's client-side timeout. Often, setting the Timeout property to a higher value avoids a connection error. Another option is to disable the timeout by setting the property to 0. Setting Verbosity to 2 shows where the time is being spent.
  • The certificate presented by the server cannot be validated: This error indicates that the component cannot validate the server's certificate through the chain of trust. If you are using a self-signed certificate, there is only one certificate in the chain. To resolve this error, you must verify that the certificate can be trusted and specify to the component that you trust the certificate. You can specify that you trust a certificate by adding the certificate to the trusted system store or by setting SSLServerCert.

Copyright (c) 2020 CData Software, Inc. - All rights reserved.
Build 20.0.7656