The encryption of passwords can be disabled with server-side or client-side parameters, or at connection time using ODBC Connect Info settings or non-standard JDBC connection properties.

By default, solidDB^® always encrypts passwords using the DES algorithm. If you have enabled the use of OpenSSL libcrypto, General.UseCryptoLib=yes, OpenSSL libcrypto is used for encryption of passwords of externally authenticated users. Databases and log files are not encrypted by default.

If you want to create a database without any encryption, disable the encryption of passwords using the parameter settings or connection properties described below.

Disabling the encryption of passwords disables also the encryption of database and log files, if used.

To disable encryption of passwords, set the server-side parameters General.UseEncryption and General.UseCryptoLib to no.

The default setting for General.UseEncryption is yes.

The default setting for General.UseCryptoLib is no.

To disable the encryption for a specific ODBC client connection, set the client-side parameter Client.UseEncryption and Client.UseCryptoLib to no.

The default setting is Yes.

Alternatively, disable encryption using the connect string option USE_ENCRYPTION=NO or USE_CRYPTO=NO.

In ODBC environments, disable encryption by including the option USE_ENCRYPTION=NO or USE_CRYPTO=NO in the ODBC connect info string.

The option must be given before the server connect string, for example:

The defaults are USE_ENCRYPTION=YES and USE_CRYPTO=NO.

In JDBC environments, disable encryption by setting the non-standard JDBC connection property solid_use_encryption to NO or solid_use_strong_encryption to NO.