Splunk DB Connect 2: Unable to restrict identities based on user role

[premwebs]

There are two 2 DB connections (say A and B) in our Splunk , I wanted to restrict user access only to "B" database and should not have access to "A"

I have created user role and granted read and write permission to "B" DB connection. but the problem here is, Still they are able to access "A" database.

looks like, if DBX capabilities granted to a role, then they can access all the db connections. is there anyway where we can have users to access only one connection and not all.

I restricted permission at identity level, db connection level but still no luck.

Thanks in Advance!
Prem

[jcoates]

Hi, that sounds familiar. there was a known issue along these lines which I thought was fixed around 3.1.0. I just browsed through the release notes for the last few versions and don't see anything though. You might need to contact support to get details and resolution.