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
|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
|Add a system property to the
|Credentials included in a non-secure connection are not secure. Use with caution.|
You configure the Java client for client authentication in the same way. See the Javadocs for more information.
The .NET client can be configured for client authentication, using a system environment variable. See the .NET client documentation for details.
|Securing Host Communications|
|Protecting Sensitive Data|
|QACOM for the .NET Environment (PDF format)|