Querix extends U.S.A. distributorship with Advanced Data Tools
4GL Developer Workshop in Washington DC,USA - 19th April 2010
Document Actions
Security - Encryption and Authentication
By using any Querix Advanced Thin Client System, an application can be made secure by using encryption and user authentication.
Available authentication methods are Shadow, Crypt and PAM management.
GUI Server Security Model
One of the most significant advantages between the Querix gui application server and other gui application servers is the ability for a client to authenticate to the server. The server process runs as the user that has actually connected to the server rather than the traditional model, where the server processes were executed within the same user context as the service itself. To allow us to achieve this, the new listener introduces three types of authentication: none (classic), basic and full.
When the GUI server is operating in full authentication mode, the client must specify a username and password. The server will then use a choice of authentication methods including PAM and Windows Active Directory Authentication.
SSL encrypted communications
SSL enrypted communcation between the GUI clients and the application server for the highest standard of security.
 |
'Hydra 4GL' has the ability to encrypt the communication between the application server and the advanced thin-client, using SSL data encryption, to provide security and peace of mind. ‘Hydra4GL’ uses the Secure Sockets Layer to provide strong encryption over communication channels. After ‘Hydra4GL’ is installed, demonstration SSL certificates are installed with the Querix application server. The GUI application server can also be configured to use your own digitally signed certificates for maximum security.
|
Phoenix SSL |
|
|
This extra layer keeps the clients remote from the server and sets new standards for security in 4GL environments. |
 |
Chimera SSL - Direct Acces |
|
|
Some database vendors may support encryption between the RDBMS and the application server. This extra layer keeps the clients remote from the server and sets new standards for security in 4GL environments. |
 |
Chimera SSL - Browser Access |
|
|
If Chimera is called via a Web browser from a Web-page, the Chimera client JAR will be transfered to the client and the connection to the application server goes directly from the Client to the Application Server. The secure internet connection between Web server and Client (Browser) would not be sufficient. For this reason, the data transmission between the Client PC/station and the Application server is encrypted. |
 |