Client Authentication for Web Data Sources
When Web data sources require client authentication, a keystore must be specified to identify the TDV Server to the provider. The TDV Server configuration keystore key alias has a default value that names a sample keystore, so that you can use client authentication immediately upon installation.
If the TDV configuration settings for keystore alias are set to null, the method described below to comply with client authentication requirements is used for Web data sources. The TDV configuration to use a specific keystore key alias overrides keystore specification defined on individual data sources.
To specify a keystore to comply with client authentication requirements
1. Open the Web data source in Studio.
2. Click the Advanced tab in the New Physical Data Source dialog to enable import of a certificate key.
3. Click Import Certificate Key Store from File to import the certificate.
Studio displays a dialog to specify the certificate.
You can choose a jks or pkcs12 certificate key store for authentication between TDV and any Web data source that requires a trusted certificate.
4. Optionally, select a keystore from the list and click Clear Certificate Key Store to remove it.
5. Optionally, click Export Certificate Key Store to File to export the current certificate keystore to a jks or pkcs12 file.
6. Optionally, on the Advanced tab, set the Channel Pass-through field to a name or names that correspond to values passed in the HTTP request header for login authentication or for other purposes.
The Channel Pass-through identifies the name of the HTTP request header property that is to be passed through to the WSDL, XML, or HTTP data source. You can specify multiple values, separated by commas.
If the data source expects a property with a name different from what was originally sent in the HTTP request header, you can change the property name if you want. The name expected by the data source is put on the left side of the “=” operand, and the original property name is put on the right.
7. Optionally, on the Advanced tab, set the Environment Pass-through field to one or more environment variables to pass through to the WSDL, XML, or HTTP data source for login authentication or other purposes.
Procedures can set an environment variable name and value by calling the SetEnvironment procedure. See the Info tab for /lib/util/SetEnvironment in the Studio resource tree for more information.
Property names in the Environment Pass-through field can be renamed before they are passed to the data source, just as they can with channel pass-through.
8. Optionally, for REST data sources, specify the Execution Timeout (msec) period.
Execution Timeout is the number of milliseconds an execution query on the data source is allowed to run before it is canceled. A value of zero milliseconds (default) disables the execution timeout. This can be used, for example, for resource-intensive cache updates set to run at non-peak processing hours.