Problem with Global Permissions on Field

brandonf · ‎08-13-2015

Hi

Just a note that your field extraction below has global permission and overwrites other "user" field name extraction. You should make it app permission level only.

default : EVAL-user user md5(clientip."_".http_user_agent)

jbjerke_splunk · ‎08-24-2015

Hi Brandonf

Thanks for reporting this in. There were a also few users who noted this.

There is a new version of the app (1.4) which fixes this issue and adds on some new functionality.
https://splunkbase.splunk.com/app/2699/

j

Problem with Global Permissions on Field

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Agent Mode Engaged! Enchaining Agentic Operations with Splunk AI Assistant 2.0

Announcing Modern Navigation: A New Era of Splunk User Experience

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

Join the Conversation

Problem with Global Permissions on Field

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Agent Mode Engaged! Enchaining Agentic Operations with Splunk AI Assistant 2.0

Announcing Modern Navigation: A New Era of Splunk User Experience

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk