Splunk token values are visible in URL when we redirect from one page to another. How can we hide them

[kumasaua]

Dear All,

Splunk token values are visible in URL when we redirect from one page to another. How can we hide them

Regards
Saurabh kumar agrawal

[niketn]

@kumasaua, you can possibly extend the concept of one of my previous answer and use KV Store (example shows lookup file based implementation for simplicity) to save some information before switching to another dashboard (preferably using JavaScript code) and then switch to the new dashboard which should pick selected values from lookup file or KV Store.

https://answers.splunk.com/answers/617305/how-can-i-give-the-to-the-users-to-save-their-sele.html

[kumasaua]

Actually I used |inputlookup xyz.csv in my page as a token... and use this token in my query..
something like this
index=xyz $tokenname$

data correctly show in dashboard but when i clink on search button for showing my query.. it say URL is too long...
in URL it show token value that is too long...

How I hide this token value to see my query.

[martin_mueller]

That's expected, and necessary to allow users to send a URL to someone else - that way someone else will have the same tokens set, and will see the same dashboard configuration.

[martin_mueller]

Can you provide the actual example case, and the reasoning behind trying to hide the token values?

[kumasaua]

Thank you for your quick response... but I have requirement to hide token value to someone else.

[niyaz006]

Hey @kumasaua , were you able to achieve this?

[niketn]

@niyaz006 @kumasaua following approach can be taken. Please try out and confirm if any assistance would be required at any step or the following is good enough 🙂

1. On click on URL redirect the form input values can be stored to KV Stored for the User logged in.

2. In the destination dashboard do not use Splunk's built in form inputs, instead use HTML inputs.

3. Fetch the values for various inputs using KV Store data for logged in user using the inputlookup and store in respective tokens within dashboard (not form tokens).

4. Delete row from KV Store as launch is complete.

5. Use Simple XML JS Extension to populate selected values from tokens to respective inputs.

6. Use Simple XML JS extension to code change/click event handler for your html inputs to set respective tokens (not form tokens) within the dashboard.