You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Recently switched from using Webhooks to OAuth and have run into an issue were the app 'forgets' its OAuth config. Alerts will work for a few days and then just stop. If you go to the app config page the OAuth token field will be empty.
To Reproduce
Steps to reproduce the behavior:
Configure app to use OAuth token per documentation
Wait a few days (up to 6)
When alerts stop functioning, go to app setup and you'll see the OAuth token field is empty.
Expected behavior
I would expect the configured OAuth token configuration to be permanently saved
Screenshots
If applicable, add screenshots to help explain your problem.
Splunk Environment:
Splunk Version: 9.0.3
OS: Windows
Cloud: No
App Version: 2.3
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Just took a look at the default\alerts_actions.conf file and it does appear that the app has a parameter for the OAuth token. I'm just going to use Puppet to configure this value which should resolve the issue.
Describe the bug
Recently switched from using Webhooks to OAuth and have run into an issue were the app 'forgets' its OAuth config. Alerts will work for a few days and then just stop. If you go to the app config page the OAuth token field will be empty.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect the configured OAuth token configuration to be permanently saved
Screenshots
If applicable, add screenshots to help explain your problem.
Splunk Environment:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: