Using Secure Communications Encryption with AES
AES Security Mechanism
The Actian Ingres security mechanism AES provides secure connections between the client and the DBMS Server by using the AES encryption algorithm. The AES mechanism uses both AES and RSA keys and provides a higher level of security than the INGRES mechanism.
There are two distinct types of network connections where AES can be enabled:
1. Applications running in client installations connecting to server installations over Ingres Net and GCA Remote Access (GCR). Applications include ODBC, ESQLC, OpenROAD, terminal monitor, and so on—all non-JDBC and non-.NET applications. This type of encryption can also be enabled for a Data Access Server (DAS) if not running in the same installation as the DBMS.
Note: Applications using shared database connections (using GCA_SAVE / GCA_RESTORE), for example OpenROAD, ABF and/or calling other applications, Report Writer or alike, must use the client side communication server rather than the default direct connection to the remote communication server. This is achieved by adding connection attribute connection_type to the vnode definition and set to comsvr.
Failing to do so, applications may fail with:
E_LC0001 GCA protocol service (GCA_RESTORE) failure.
Internal service status E_GC0017 -- Restore failure: error opening
restore file.
E_LQ0001 Failed to connect to DBMS session.
2. JDBC and .NET applications connecting to a Data Access Server (DAS).
Last modified date: 07/21/2025