Activating Classic Authentication

Classic authentication prompts users to enter their user name and password and sends the information to the DI Server. Depending on its configuration, the server then verifies the provided information against authentication data stored in the administration database (ADB) or in an LDAP directory.

For information on how to configure a DI Server to use LDAP authentication, see Configuring LDAP Authentication and for details about the ADB and its function, see The Function of the Administration Database.

To activate classic authentication in Metability

1. Open the dataspace.xml file for editing.
2. Add this parameter to the SERVER entry that pertains to the server connection for which you want to enable classic authentication:

authType="classic"

For example:

<SERVER Name="User connection" host="rosrv.asg.com" port="8888" authType="classic"/>

3. Optional. Specify a user account and password to be used instead of prompting users for their credentials (that is, all users will be logged in using the same account):

user="name" pwd="password"

where name and password are the account’s name and password (if required).

For example:

<SERVER Name="User connection" host="rosrv.asg.com" port="8888" authType="classic" user="MTB-USER" pwd="123"/>

4. Save your changes.

To activate classic authentication with TLS-encrypted communication in Metability

1. Open the dataspace.xml file for editing.
2. Add this parameter to the SERVER entry that pertains to the server connection for which you want to enable classic authentication:

authType="classic"

For example:

<SERVER Name="User connection" host="rosrv.asg.com" port="8888" authType="classic"/>

3. Add this parameter to the SERVER entry that pertains to the server connection for which you want to enable TLS-encrypted communication:

tlsCaCertFileJava="* <xml_attr_val>*"

These are the available values for this parameter:

*<xml_attr_val> := <file> | JVM | WIN *

The values and the descriptions are:

<file>	The absolute path and name of a Java KeyStore file (*.jks) that contains the trusted root CA certificates.
JVM	The symbolic name for the JVM's trusted certificates store.
WIN	The symbolic name for the Windows certificate store Current Users/Trusted Root Certification Authorities/Certificates.

This is supported only for Windows environments.

For example:

<SERVER Name="User connection" host="rosrv.asg.com" port="8888" authType="classic" tlsCaCertFileJava="WIN"/>

4. Optional. Specify a user account and password to be used instead of prompting users for their credentials (that is, all users will be logged in using the same account):

user="name" pwd="password"

where name and password are the account’s name and password (if required).

For example:

<SERVER Name="User connection" host="rosrv.asg.com" port="8888" authType="classic" tlsCaCertFileJava="WIN" user="MTB-USER" pwd="123"/>

5. Save your changes.