Now we've solved this problem.
We have LDAP integrated authentification, it seems like that:
LDAP_User -> LDAP_SplunkAdminGroup -[group mapping]-> SplunkAdminRole
(the Splunk-group "SplunkAdminRole" inherits from Splunk-group "admin")
The "admin" Group inherits from "power", "user" and (!) "dbx_user" and has further manually selected capabilities. This way it works for any other capabilities except DB Connect 😕
It strange, because I can see that the capability "db_capable" is definitely there.
But, If I put "dbx_user" as Inheritance inside of Group-Mapping (that means: die LDAP group is mapped to "SplunkAdminGroup" AND "dbx_user"), then it works, so most probably we would create a new LDAP group for it and map it to "dbx_user" and then grant the permissions in LDAP.
Now it looks like that:
LDAP_User -> LDAP_SplunkAdminGroup -[group mapping]-> SplunkAdminRole,dbx_user
It is really weird behavior!
What I'm asking me is: is it a issue of splunk or DB connect app?
... View more