Application Note for QuNect ODBC for Quick Base
How Secure is QuNect ODBC for Quick Base?
QuNect ODBC for Quick Base is actually more secure than Quick Base itself. This results from the fact that all communications between QuNect ODBC for Quick Base and Quick Base are done with SSL TLS over HTTPS (port 443). There is no option to use HTTP to communicate with Quick Base when using QuNect ODBC for Quick Base. All information communicated between QuNect ODBC for Quick Base and Quick Base itself is encrypted with the industry-standard, Secure Socket Layers (SSL) protocol to ensure your information is neither intercepted nor corrupted during transmission over the Internet.This includes but is not limited usernames, passwords, database information and database metainformation such as application, table and columns names. The level and type of encryption within the SSL protocol is determined by the configuration of your operating system.
A QuNect ODBC for QuickBase license holder must use either their Quickbase password or a usertoken along with their Quickbase user name to configure their DSN or connection string. DSNs are managed by the ODBC Administrator application (C:\Windows\System32\odbcad.exe) that is part of the Windows operating system or in the case of Linux and MacOS a separate application (e.g. iODBC, unixODBC). The Windows ODBC Administrator application stores configuration information in the Registry including passwords and usertokens. For Linux and MacOS the ODBC Administrator applications store information in a file called odbc.ini. Connection strings can be used instead of DSNs. It is up to an ODBC client application (e.g. Tableau, SQL Server, MS Excel, MS Access, Informatica, MATLAB, etc) to store the connection string. QuNect ODBC for QuickBase does not store connection strings, usernames, passwords or usertokens except temporarily in memory while QuNect ODBC for QuickBase is being used by the ODBC client application.