Security

select lookuptable based on role of the current user

FritzWittwer_ol
Contributor

We have an app which is deployed for different user groups which are distinguished by different roles which gives them access to their indexes. The searches use an asterisk in the index specification so each user gets the data from the index to which he gets access based on his role.

We need the same functionality for lookups, e.g.

  • lookuptable_a (belongs role a)
  • lookuptable_b (belongs role b)

spl: index=* | lookup lookuptable_* ...

Depending on the users role either lookuptable_a or lookuptable_b should be used, but wild-carding of lookup-table-name is not supported

0 Karma

somesoni2
Revered Legend

Give this a try

1) Create a macro (read by everyone or by both role_a and role_b)
Name: getlookupname
content:

[| rest /services/authentication/current-context splunk_server=local | table roles | eval search=case(isnotnull(mvfind(roles,"role_a")),"lookuptable_a",isnotnull(mvfind(roles,"role_b")),"lookuptable_b") | table search ]

2) Change sharing permissions on the lookup tables so that lookuptable_a is only accessible by role_a. same for lookuptable_b.

Now your users can use that macro in place of lookup table like this

index=* | lookup `getgetlookupname` ...
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...

Splunkbase Unveils New App Listing Management Public Preview

Splunkbase Unveils New App Listing Management Public PreviewWe're thrilled to announce the public preview of ...

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...