I am using Kong 0.11 with datastax cassandra. Kong was working fine till we were using it with community edition cassandra but as we moved, we started seeing this error User <xyz> has no CREATE permission on <all keyspaces> or any of its parents. Why does kong need permission on ? I have given right permission to kong keyspace that should be enough, isn’t it?
I already have a keyspace with all the permission on that keyspace except for CREATE on ALL KEYSPACES. So, does it need that permission or is there a way to avoid that too?
Hi, I am running Kong 1.1.2 with a cassandra database backend. I am seeing the same issue as amolp where it is trying to create the keyspace even though the keyspace already exists.
Centos 7
Kong version --> 1.1.2
kong migrations bootstrap --> results in unauthorized user kongadmin has no CREATE permision on or any of its parents.
kong.conf:
database=cassandra
cassandra_username = kongadmin
cassandra_keyspace = kong
from cassandra database connected as kongadmin
desc kong;
CREATE KEYSPACE kong with replication = {‘class’: ‘NetworkTopologyStrategy’,‘xx3’: ‘2’, ‘yy1’:‘1’} and durable_writes=true;
Is there a known fix, I don’t have superuser privs for this cluster.