Security has been taken into account starting with the design stage: server-side configuration lets admins specify strong authentication and security rules in order to ensure SQL database security.
Your SQL database will never be exposed directly to the Internet, because AceQL HTTP uses a three-tier architecture. All SQL client calls are analyzed and filtered by a configurable Servlet, the AceQL HTTP Manager. Only this Servlet can access the SQL database directly. Access to the database is granted only if the client call matches the rules defined in the Servlet.
Each client must be logged in with a username and password to gain access to an AceQL Session. The username and password are verified by the AceQL HTTP Manager, using your injected Java code to authenticate the username-password pair. Once the client is logged in, an authentication session ID is built using strong cryptography. The authentication session ID is then reused at each client call to verify that the request is legitimate. A default authentication session ID builder algorithm is provided, but you may use JSON Web Tokens or define and code your own implementation.
You can configure your security rules in Java to reinforce the protection of your databases. These rules:
All HTTP communications between the client side and the server can be encrypted with SSL/TLS.
AceQL HTTP supports obfuscation of the Java code distributed on the client side.
