Security

Search head pooling and authorize.conf

echalex
Builder

Hi,

I'm wondering how Splunk (4.3.x) deals with new roles created through the GUI. Since they're located in etc/system, I suppose you have to distribute any changes by yourself, or is there a way to automate this?

1 Solution

echalex
Builder

Answering my own question, this situation has been documented.
(5.0.2, 4.3.5)

View solution in original post

0 Karma

rmorlen
Splunk Employee
Splunk Employee

That is how we handle authorize.conf. We have the common (shareable) information in a "splunk_system" app and the server specific information in $SPLUNK_HOME/etc/system/local. We do this for all the $SPLUNK_HOME/etc/system/local config files.

0 Karma

echalex
Builder

Maybe I should've searched better, but hopefully the link to the doc is useful to you. 🙂

0 Karma

echalex
Builder

Answering my own question, this situation has been documented.
(5.0.2, 4.3.5)

0 Karma

alacercogitatus
SplunkTrust
SplunkTrust

I'm in a similar situation, but on 5.0.1. I'd love to see the solution as well.

Get Updates on the Splunk Community!

Splunk Search APIを使えば調査過程が残せます

   このゲストブログは、JCOM株式会社の情報セキュリティ本部・専任部長である渡辺慎太郎氏によって執筆されました。 Note: This article is published in both Japanese ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...