3/10/2023 0 Comments Gss initiate failed dbvisualizer![]() Not all clients are compatible with all Kerberos implementations, so this should be done in consultation with a resource knowledgeable about your organizations's Kerberos setup.Ĥa. This usually requires installation of a KDC client on the Agent box. You may need to use a Kerberos client to run a kinit command locally, on your Agent box(es). Copy your krb5.ini (or nf), nf and keytab files to \QuerySurge\agent\ģe. In \QuerySurge\agent\, create a bin\ directory.Ĭopy the winutil.exe that you downloaded (step 1b) to \QuerySurge\agent\bin\.ģd. Make sure that the proper set of JDBC jar files is deployed to \QuerySurge\agent\jdbc, per step 1a.ģc. (Make sure to run QuerySurgeAgentw.exe and not QuerySurgeAgent.exe.) On the General tab, use the Stop button (lower left) to stop the Agent.ģb. Go to the directory: \QuerySurge\agent\, and run QuerySurgeAgentw.exe as Administrator. ![]() However, there is no requirement to use these specific directories.ģa. Note: We recommend using the QuerySurge Agent directories for the file locations in this setup step, since this should be the same for all your Agents. Note : keytab files may have a single key for a single principal or may have multiple keys. Your Login Context may be different check with a Kerberos-knowledgeable resource in your organization. Note: In the example above, the leading name .initiate, which appears before the opening curly brace, is the Login Context. Note: The principal used in your nf may need to be a user principal, while the principal used in the JDBC URL (see below) may need to be a service principal, depending on your Kerberos configuration. The format of a typical Kerberos V5 principal is: principal for your nf may need both the primary and the it may only require the instance (as shown above) instance field of the principal may be a user name myuserprin or it may be a fully qualified name, depending on your configuration. Note:A principal has three parts: the primary, the instance, and the realm. KeyTab="C:/Program Files/QuerySurge/agent/mykeytab.keytab" Using the default install path on Windows, this becomes: Note the dummy path to the keytab and the dummy principal in this file template:Ĭom.Krb5LoginModule Specify your keytab path with forward slashes (even though your deployment is on Windows). You'll need a nf file, which points to the keytab file. The basic nf file layout is below. The keytab file - If you're authenticating to Kerberos via a keytab, you'll need to obtain a keytab file (usually generated by a Kerberos admin or other knowledgeable resource), and the user principal associated with the keytab.Ģc. On Windows, the file may be called krb5.ini.Ģb. ![]() nf (krb5.ini) file - From your Kerberos admin or other knowledgeable resource, obtain a nf file. You can download it from Hortonworks here or (at the time of this writing) from this github.Ģa. Note: winutils.exe is not distributed with Hadoop. You will also need hadoop winutils.exe for 1a and 1b. Note: If you have previously deployed Hive driver jars, you should delete them from the Agent driver directory before you deploy the driver jars from your Hive server. Note that you'll need to match your Hive version to the driver version that you download.ĭeploy the driver jar(s) to your Agent you can find instructions for this procedure here. You can download this driver from this github. ![]() QuerySurge's vendor, RTTS, partners with CData you can see information about the CData driver offering here.ġc. Note: For Zookeeper URLs (see Step 5), additional jar files may be required: curator-client-X.X.X.jar, curator-framework-X.X.X.jar.ġb. Get the JDBC driver jars for your Hive distro from your Hive server (asterisks indicate distribution-specific notations): If you receive this outcome, we recommend trying one of the other options listed below (1b or 1c).ġa. The typical result in this case is that your connection attempt will error out with either a NoClassDefFoundError or a ClassNotFoundException. Note: Due to changes in recent releases of the Apache Hive "standalone" driver jar (see 1a), depending on your version, the list of required jars shown may not be correct or complete for kerberized Hive connections. We strongly encourage using the specific Apache drivers from your Hadoop distro and version. The drivers on which this procedure is based are the standard Apache Hive JDBC drivers. ![]() This procedure is for QuerySurge Agents deployed on Windows. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |