Splunk Cloud vetting is failing since new major release 2.0:
The bearer token configured from UI is stored as plain text in the backend in plain text. The same token is used for authentication with Splunk's endpoint. This is not permissible in Splunk cloud, either use Splunk's session key or use storage/passwords endpoint to save the token. File: bin/ta_service_desk_simple_addon/modalert_jira_service_desk_replay_helper.py Line Number: 231
The value of the bearer token is logged in a python file, which is not permissible in the Splunk cloud. Consider removing this debug log. File: bin/ta_service_desk_simple_addon/modalert_jira_service_desk_replay_helper.py Line Number: 204
Splunk Cloud vetting is failing since new major release 2.0:
The bearer token configured from UI is stored as plain text in the backend in plain text. The same token is used for authentication with Splunk's endpoint. This is not permissible in Splunk cloud, either use Splunk's session key or use storage/passwords endpoint to save the token. File: bin/ta_service_desk_simple_addon/modalert_jira_service_desk_replay_helper.py Line Number: 231
The value of the bearer token is logged in a python file, which is not permissible in the Splunk cloud. Consider removing this debug log. File: bin/ta_service_desk_simple_addon/modalert_jira_service_desk_replay_helper.py Line Number: 204