Configuring for Client Authentication


By default, connections with the host are not secure in the Designer and credentials are not sent to the host (since username and passwords are passed as plain text). Host connections configured for client authentication will not work in this case.

If you need
Do this...
A connection that authenticates the client Secure the connection.

By default, when using a secure connection, credentials (username and password) are always sent to the host via the HTTP authorization header (using the basic authentication method). See Secure Host Communications to learn how to configure a secure connection.

To use client authentication with a non-secure connection
(not recommended)
Add a system property to the config.ini file. This file is located in the configuration subfolder where the Bridge Designer is installed.

  1. Using a text editor, open config.ini.
  2. Add the line: com.attachmate.cicsbridge.includecredentials=true. Save the file.
Credentials included in a non-secure connection are not secure. Use with caution.

Java and VBI Scripting clients

You configure the Java and VBI scripting clients for client authentication in the same way. See the Javadocs and VBI Scripting language documentation for more information.

.NET clients

The .NET client can be configured for client authentication, using a system environment variable. See the .NET client documentation for details.

Related Topics
Bullet Securing Host Communications
Bullet com.attachmate.cicsbridge.ws
Bullet Using Verastream Bridge Integrator Scripting Language (PDF format)
Bullet Protecting Sensitive Data
Bullet QACOM for the .NET Environment (PDF format)