[geomesa-dev] [JIRA] (GEOMESA-3162) accumulo-client.properties isn't loa

["John Gibson (JIRA)" <jira@xxxxxxxxxxxxxxxxxxxxx>]

Title: Message Title

John Gibson created an issue

GeoMesa / GEOMESA-3162

accumulo-client.properties isn't loaded correctly, breaks TLS

Issue Type:	Bug
Affects Versions:	3.1.2
Assignee:	Unassigned
Components:	Accumulo
Created:	14/Dec/21 10:51 AM
Environment:	CentOS 7, Geomesa Accumulo 3.1.2_2.11, Accumulo 2.0.1
Priority:	Major
Reporter:	John Gibson

Geomesa loads some credentials and connection info from accumulo-client.properties as implemented by GEOMESA-2800 Done . Unfortunately it only loads a handful of the client properties (Zookeeper connection info, and some authentication settings). This ignores other client settings like TLS, for example.

The culprit is in AccumuloDataStoreFactory:

val conf = ClientConfiguration.create().withInstance(instance).withZkHosts(zookeepers)
    ZookeeperTimeoutParam.lookupOpt(params).orElse(config.zkTimeout).foreach { timeout =>
      conf.`with`(ClientProperty.INSTANCE_ZK_TIMEOUT, timeout)
    }

ClientConfiguration.create() creates an empty configuration instead of automatically loading the client properties. You need either an explicit fromFile() or a loadDefault() to get the default configuration loaded.

This is why the SASL flag has to be set manually further down in the connection creation code:

AccumuloDataStoreFactory.scala

      // explicitly enable SASL for kerberos connections
      // this shouldn't be required if Accumulo client.conf is set appropriately, but it doesn't seem to work
      conf.withSasl(true)

Although I've only tested on 3.1.2, it appears that the issue remains in the latest source code as well.

Add Comment

Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS
This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100186-sha1:84fa40f)