topic Re: Customize globalConfig.json in Splunk Dev

Customize globalConfig.json

Wonamor — Thu, 14 Nov 2024 22:59:15 GMT

Hi everyone,

I'm trying to personalize the "configuration" tab of my app generated by add-on builder.
By default when we try to add an account, we enter the Account Name / Username / Password.
Firstly I would simply like to change the labels linked to Username and Password to replace them with Client ID and Client Secret. (and secondly add the Tenant ID field).

I achieved this by editing the file in $SPLUNK_HOME/etc/apps/<my_app>/appserver/static/js/build/globalConfig.json.
Then I incremented the version number in the app properties.
(as shown in this post https://community.splunk.com/t5/Getting-Data-In/Splunk-Add-on-Builder-Global-Account-settings/m-p/570565)

However when I make new modifications elsewhere in my app, the globalConfig.json file is reset to its default values.

Do you know how to do this?

Splunk Version : 9.2.1

Add-On Builder version : 4.3.0

Thanks

Re: Customize globalConfig.json

marnall — Mon, 18 Nov 2024 19:37:53 GMT

You may have better results by un-checking the "Global account settings" in Add-on setup parameters in the Add-On Builder and then adding your own Add-on Setup Components like a Text field for Client ID and a Password field for Client Secret, rather than attempting to re-name the account username and password.

Re: Customize globalConfig.json

Wonamor — Tue, 19 Nov 2024 10:00:12 GMT

Hi @marnall,

Thanks a lot for your feedback !

I also thought about using a password field instead of Global account settings.

But I will have to re-enter the client secret every time I update the input which is not a good experience for the end user.

Again this solution "works" but temporary and I don't understand why it is not persistent 🤔

Re: Customize globalConfig.json

marnall — Tue, 19 Nov 2024 19:35:23 GMT

No you shouldn't need to enter it every time as an input. You can make custom add-on settings which are not username/password and then these will be set once on app configuration and can be re-used for inputs.

Re: Customize globalConfig.json

Wonamor — Wed, 20 Nov 2024 08:56:40 GMT

Hello @marnall ,

I see what you mean but doing it this way will apply the same login password to all inputs. That's not what I'm looking for 🙁

The ‘best way’ for me is to use this solution and stop editing my application using Add-on Builder. And if I need to update my application with Add-on Builder, I have to restore the files (globalConfig and <input>_rh_account) manually.

Normally, I'll be taking part in the application building course on Monday. If I get the answer, I'll update this post.

Have a good day