Closed andrew-solidborder closed 11 years ago
Tried your suggestion to ensure that data was entered in the API key and now get:
Encountered the following error while trying to update: In handler 'localapps': A password already exists for id="credential::admin:"
OK, so I played with this a little more tonight. Entering a username and password combo without anything in the API key field generates an issue that is nearly impossible to get by without manually deleting the entries in app.conf and then restarting Splunk.
Maybe there just needs to be some error checking to ensure that all fields have something entered in them before allowing the username and password to be written to app.conf.
I'll upgrade my client's install to 3.3 at the start of the week given I've found the workaround.
Actually closed by d360c65. Accidentally lost commit 93e4b44.
The error is:
Encountered the following error while trying to update: In handler 'localapps': Password cannot contain all * characters
I've verified this in 2 separate environments with new Splunk for Palo Alto Networks installations.