The built-in JDBC driver that comes with the JDBC client might not be compatible with the Kerberos options for the Vertica server. DbVisualizer/DBeaver must be configured correctly with the Vertica JDBC driver that matches the server version.If that is not the case, for example, if that host is in the COMPANYCORP Kerberos realm, you need a domain_realm mapping like the following: The JDBC client uses this file at startup to determine which authentication protocol to use.īefore you configure the JDBC clients, make sure the following is true:For example, the domain realm is assumed to be in the VERTICA Kerberos realm. The authentication method and its associated implementation details are specified in a JAAS configuration file. JAAS is a pluggable API that permits Java applications to remain independent from underlying authentication methodologies. JDBC clients use the Java Authentication and Authorization Service (JAAS) for Kerberos authentication. The information in this blog post applies to both the Vertica Enterprise and SQL on Hadoop editions. The examples used in this post are based on DbVisualizer and DBeaver, but you can use these steps for any JDBC-based client tool. This blog post provides step-by-step guidance for setting up JDBC clients like DbVisualizer and DBeaver to work with your Kerberos-enabled Vertica cluster. It is easy to use these tools on a non-Kerberos enabled Vertica cluster, but connecting to a Kerberos-enabled Vertica cluster is not straightforward because there is no native support for Kerberos on tools like DbVisualizer and DBeaver. Many customers use JDBC-based tools like DbVisualizer and DBeaver to connect to Vertica for SQL development purposes.
0 Comments
Leave a Reply. |