I was missing the zookeeper client configuration from my machine. The file
has the following in it:
instance.name=agile_accumulo
instance.rpc.sasl.enabled=True
instance.zookeeper.host=dev:2181
instance.zookeeper.timeout=30s
kerberos.server.primary=accumulo
Either create this file and put it here:
This is one of the tests I used to figure out how Kerberos worked with
Accumulo.
https://gist.github.com/wjsl/93c8528e8f27bbeb31bf
You'll see the pattern where I would call `val someUser =
loginUserFromKeytabAndReturnUGI(...)` and then execution connections inside
of a doAs call.
On Tue, Mar 8,
I think one thing is that we can at least guarantee you can connect to the
KDC.
It kind of seems like there's an issue with communication between the
client and Accumulo.Can you try `new KerberosToken(principal, keytab,
true)`? I think I ran into this when figuring things out my own. By passing
in
One thing I've noticed is that my client stack trace makes no mention of
using an SASL transport (It's the last log dump in this email). Maybe this
is the problem; Accumulo wants an SASL connection, but for some reason the
client app isn't using an SASL transport even though I'm using a Kerberos
To
Any logs on the Accumulo and/or KDC side?
On Tue, Mar 8, 2016 at 5:05 PM, Tristen Georgiou
wrote:
> Here is a simple Java program to attempt to get a connection to Accumulo
> and list the local users:
>
> package com.phemi.testing;
>
> import org.apache.accumulo.core.client.Connector;
> import o
Here is a simple Java program to attempt to get a connection to Accumulo
and list the local users:
package com.phemi.testing;
import org.apache.accumulo.core.client.Connector;
import org.apache.accumulo.core.client.Instance;
import org.apache.accumulo.core.client.ZooKeeperInstance;
import org.apa
