<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Splunk Add-on for Nessus Tenable API: Getting error &amp;quot;Fail to decrypt the encrypted credential information - not well-formed (invalid token)&amp;quot;? in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218849#M23928</link>
    <description>&lt;P&gt;@perfecto25 - It looks like some text got cut off at the bottom. Also, this question is quite old so it may not garner much activity. I would suggest posting a new question. &lt;/P&gt;</description>
    <pubDate>Thu, 09 Mar 2017 18:50:20 GMT</pubDate>
    <dc:creator>aaraneta_splunk</dc:creator>
    <dc:date>2017-03-09T18:50:20Z</dc:date>
    <item>
      <title>Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218824#M23903</link>
      <description>&lt;P&gt;I have the latest TA Nessus installed and it was working fine for about a week importing nessus reports through the Tenable API calls.  It then stopped indexing events and reported the following error(s):&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;2016-08-08 17:04:27,658 +0000 log_level=ERROR, pid=18084, tid=MainThread, file=ta_mod_input.py, func_name=main, code_line_no=186 | Tenable task encounter exception Traceback (most recent call last): File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/data_collection/ta_mod_input.py", line 183, in main config_cls=configer_cls) File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/data_collection/ta_mod_input.py", line 100, in run tconfig = tc.create_ta_config(settings, config_cls or tc.TaConfig) File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/data_collection/ta_config.py", line 181, in create_ta_config return config_cls(meta_config, settings) File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/data_collection/ta_config.py", line 24, in __init__ self._load_task_configs() File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/data_collection/ta_config.py", line 48, in _load_task_configs self._client_schema) File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/data_collection/ta_helper.py", line 67, in __init__ self._load_conf_contents() File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/data_collection/ta_helper.py", line 93, in _load_conf_contents self._all_conf_contents = self._config.load() File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/config.py", line 127, in load raise ConfigException(msg) ConfigException: Fail to load endpoint "global_settings" - Unspecified internal server error. reason={"messages":[{"type":"ERROR","text":"\n In handler 'ta_tenable_settings': External handler failed with code '1' and output: 'REST ERROR[1021]: Fail to decrypt the encrypted credential information - not well-formed (invalid token): line 135, column 41'. See splunkd.log for stderr output."}]}
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;as well as:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;2016-08-08 17:04:27,658 +0000 log_level=ERROR, pid=18084, tid=MainThread, file=config.py, func_name=log, code_line_no=50 | UCC Config Module: Fail to load endpoint "global_settings" - Unspecified internal server error. reason={"messages":[{"type":"ERROR","text":"\n In handler 'ta_tenable_settings': External handler failed with code '1' and output: 'REST ERROR[1021]: Fail to decrypt the encrypted credential information - not well-formed (invalid token): line 135, column 41'.  See splunkd.log for stderr output."}]}
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/tenable_sc.py", line 21, in &amp;lt;module&amp;gt;
    ta_run()
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/tenable_sc.py", line 17, in ta_run
    ta_input.main(collector_cls, schema_file_path, 'tenable_sc')
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/data_collection/ta_mod_input.py", line 183, in main
    config_cls=configer_cls)
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/data_collection/ta_mod_input.py", line 100, in run
    tconfig = tc.create_ta_config(settings, config_cls or tc.TaConfig)
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/data_collection/ta_config.py", line 181, in create_ta_config
    return config_cls(meta_config, settings)
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/data_collection/ta_config.py", line 24, in __init__
    self._load_task_configs()
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/data_collection/ta_config.py", line 48, in _load_task_configs
    self._client_schema)
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/data_collection/ta_helper.py", line 67, in __init__
    self._load_conf_contents()
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/data_collection/ta_helper.py", line 93, in _load_conf_contents
    self._all_conf_contents = self._config.load()
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/config.py", line 126, in load
    log(msg, level=logging.ERROR, need_tb=True)
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/config.py", line 48, in log
    stack = ''.join(traceback.format_stack())
None
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I've tried restarting the Heavy Forwarder that is collecting it, as well as changing the "start_time" located in the tenable_sc_inputs.conf to try and reset the checkpoint information, but no luck.  &lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:33:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218824#M23903</guid>
      <dc:creator>jonathan_cooper</dc:creator>
      <dc:date>2020-09-29T10:33:36Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218825#M23904</link>
      <description>&lt;P&gt;First guess is that it's having trouble decrypting the password stored in passwords.conf.  Maybe it was made on a node with a different splunk.secret?  Does resetting the credentials by hand help?&lt;/P&gt;</description>
      <pubDate>Mon, 08 Aug 2016 19:55:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218825#M23904</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2016-08-08T19:55:41Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218826#M23905</link>
      <description>&lt;P&gt;So that was part of the issue, it was in fact that the passwords.conf that was generated was messed up during an ES upgrade and merging of TA's.  The unfortunate issue is how this gets deployed via the Deployment Server.  Being that it generates a passwords.conf after restart, it doesn't jive well with how the Deployment Server works.&lt;/P&gt;

&lt;P&gt;Once manually installed on the Heavy Forwarder and the passwords.conf cleared and re-generated, it seems to be working fine.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Aug 2016 19:59:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218826#M23905</guid>
      <dc:creator>jonathan_cooper</dc:creator>
      <dc:date>2016-08-08T19:59:57Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218827#M23906</link>
      <description>&lt;P&gt;This problem seems to have reared it's ugly head again, and this time it's not the passwords.conf.&lt;/P&gt;

&lt;P&gt;After running fine for a few days, it began erroring out, this time with ERROR regarding invalid credentials and invalid tokens in the request.  I verified my login credentials directly, which worked, and updated the app, while removing the passwords.conf and allowing it to regenerate, which had no effect.&lt;/P&gt;

&lt;P&gt;I ran some curl commands against the passwords API to validate it was getting the right results and began seeing odd behavior.  For instance, I ran the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;curl -q --insecure -u 'admin:password' 'https://localhost:8089//servicesNS/nobody/Splunk_TA_nessus/storage/passwords?count=1'
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The result returned for the &lt;STRONG&gt;&lt;EM&gt;Splunk_TA_cisco-ise&lt;/EM&gt;&lt;/STRONG&gt; (WHAAAT?) app instead.  If I changed the "count" to 0 or -1, I would get the right app to return, but the following text for clear password:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;s:key name="clear_password"&amp;gt;proxy_password``splunk_cred_sep````splunk_cred_sep``proxy_username``splunk_cred_sep``&amp;lt;/s:key&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Could this be a bug?  I'm not sure what could cause this.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:38:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218827#M23906</guid>
      <dc:creator>jonathan_cooper</dc:creator>
      <dc:date>2020-09-29T10:38:30Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218828#M23907</link>
      <description>&lt;P&gt;Latest error I'm receiving.  I was able to resolve the curl issue, but only after removing passwords.conf and replacing the password in tenable_sc_server.conf and then restarting Splunk a few times.  Still doesn't explain why it just stops working randomly.  I have verified the credentials are good, and curl returns the right information, but it's still not working:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;2016-08-25 15:00:05,516 +0000 log_level=ERROR, pid=3366, tid=Thread-7, file=ta_data_collector.py, func_name=_do_safe_index, code_line_no=161 | [stanza_name="sc_input" data="sc_vulnerability" server="prod_sc"] Failed to get msg
Traceback (most recent call last):
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/data_collection/ta_data_collector.py", line 151, in _do_safe_index
    events, ckpt = self._client.get()
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/splunktaucclib/data_collection/ta_data_client.py", line 73, in get
    return self._gen.next()
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/ta_tenable_sc_data_collector.py", line 93, in _process_sc_vulnerability
    _pre_process_ckpt(sc, task_config, ckpt, logger_prefix)
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/ta_tenable_sc_data_collector.py", line 212, in _pre_process_ckpt
    job_start_time, end_time))
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/security_center.py", line 134, in perform_request
    self._error_check(response, result)
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/security_center.py", line 177, in _error_check
    result['error_msg'])
APIError: 'status=403, error_code=12, error_msg=This request contains an invalid token.'
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:45:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218828#M23907</guid>
      <dc:creator>jonathan_cooper</dc:creator>
      <dc:date>2020-09-29T10:45:23Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218829#M23908</link>
      <description>&lt;P&gt;Unaccepted just because I'm still having on-going issues, this was the answer to the original problem however.  &lt;/P&gt;</description>
      <pubDate>Thu, 25 Aug 2016 15:11:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218829#M23908</guid>
      <dc:creator>jonathan_cooper</dc:creator>
      <dc:date>2016-08-25T15:11:23Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218830#M23909</link>
      <description>&lt;P&gt;I am having the same issues and looking for a resolution.&lt;/P&gt;

&lt;P&gt;APIError: 'status=403, error_code=12, error_msg=This request contains an invalid token.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:53:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218830#M23909</guid>
      <dc:creator>supreetsingh</dc:creator>
      <dc:date>2020-09-29T10:53:06Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218831#M23910</link>
      <description>&lt;P&gt;Same issue here too:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/splunk_ta_nessus/security_center.py", line 177, in _error_check
    result['error_msg'])
APIError: 'status=403, error_code=12, error_msg=This request contains an invalid token.'
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Has anyone tried a support ticket yet?&lt;/P&gt;</description>
      <pubDate>Wed, 07 Sep 2016 20:33:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218831#M23910</guid>
      <dc:creator>worshamn</dc:creator>
      <dc:date>2016-09-07T20:33:21Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218832#M23911</link>
      <description>&lt;P&gt;I had another consultant get a Jira ticket opened internally, I'll see if I can get a status&lt;/P&gt;</description>
      <pubDate>Wed, 07 Sep 2016 20:42:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218832#M23911</guid>
      <dc:creator>jonathan_cooper</dc:creator>
      <dc:date>2016-09-07T20:42:01Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218833#M23912</link>
      <description>&lt;P&gt;I opened a support ticket with Splunk. The issue of the "This request contains an invalid token" in my case is because we are using Security Center 5.4. Splunk informed me that in 5.4, Tenable changed their set-cookie format (which was that it returns 2 cookies, one of which is valid). Splunk knows of the issue and is planning on adding support for 5.4 in a future version, but could not provide a timeline. &lt;/P&gt;</description>
      <pubDate>Mon, 12 Sep 2016 18:39:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218833#M23912</guid>
      <dc:creator>worshamn</dc:creator>
      <dc:date>2016-09-12T18:39:40Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218834#M23913</link>
      <description>&lt;P&gt;@worshamn - I received the same answer with support...  Same issue, same version of Security Center.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2016 14:48:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218834#M23913</guid>
      <dc:creator>jbailey_splunk</dc:creator>
      <dc:date>2016-09-13T14:48:45Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218835#M23914</link>
      <description>&lt;P&gt;Resolution:&lt;/P&gt;

&lt;P&gt;Edit the following file on the HF:  Splunk_TA_nessus/bin/splunk_ta_nessus/security_center.py&lt;BR /&gt;
Insert the following at Line 138 within the file:  Code: self._cookie = self._cookie[74:]&lt;BR /&gt;
Save the file&lt;BR /&gt;
Restart Splunk&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 11:02:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218835#M23914</guid>
      <dc:creator>jbailey_splunk</dc:creator>
      <dc:date>2020-09-29T11:02:52Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218836#M23915</link>
      <description>&lt;P&gt;This worked for me, thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 20 Sep 2016 19:17:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218836#M23915</guid>
      <dc:creator>stmyers84</dc:creator>
      <dc:date>2016-09-20T19:17:14Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218837#M23916</link>
      <description>&lt;P&gt;which version is this fix for? i just tried it on 5.1.1 and its not working.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Dec 2016 21:20:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218837#M23916</guid>
      <dc:creator>gdavid</dc:creator>
      <dc:date>2016-12-06T21:20:21Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218838#M23917</link>
      <description>&lt;P&gt;I believe this was originally for 5.0, but then fixed in 5.1.0 which is the version I'm currently on.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Dec 2016 21:36:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218838#M23917</guid>
      <dc:creator>stmyers84</dc:creator>
      <dc:date>2016-12-06T21:36:06Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218839#M23918</link>
      <description>&lt;P&gt;5.1.1 installed and seeing the same problem. &lt;/P&gt;

&lt;P&gt;output: 'REST ERROR[1021]: Fail to decrypt the encrypted credential information - not well-formed (invalid token): line 33, column 47'.  See splunkd.log for stderr output."}]}&lt;BR /&gt;
  File "/opt/splunk/etc/apps/Splunk_TA_nessus/bin/tenable_sc.py"&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 12:02:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218839#M23918</guid>
      <dc:creator>gdavid</dc:creator>
      <dc:date>2020-09-29T12:02:02Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218840#M23919</link>
      <description>&lt;P&gt;This answer evolved over time as there were two issues eventually listed - the first related to "Fail to decrypt the encrypted credential information - not well-formed (invalid token)", and the second related to the following message:  "APIError: 'status=403, error_code=12, error_msg=This request contains an invalid token".&lt;/P&gt;

&lt;P&gt;The second issue was resolved by the latest TA release...  From following the answer thread, the first issue was resolved from the post on August 25 @ 8:07 am, which states:  "I was able to resolve the curl issue, but only after removing passwords.conf and replacing the password in tenable_sc_server.conf and then restarting Splunk a few times."  &lt;/P&gt;

&lt;P&gt;I would recommend re-configuring the TA, ensuring the passwords.conf and tenable_sc_server.conf files are correct.  Also, make sure Splunk is restarted - just in case.&lt;/P&gt;

&lt;P&gt;Hope that helps...&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 12:02:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218840#M23919</guid>
      <dc:creator>jbailey_splunk</dc:creator>
      <dc:date>2020-09-29T12:02:50Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218841#M23920</link>
      <description>&lt;P&gt;Do we know if this fix works for when using Security Center 5.4+ or is it as @worshamn says below and 5.4+ just isn't supported yet? Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 01 Feb 2017 18:45:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218841#M23920</guid>
      <dc:creator>jat75</dc:creator>
      <dc:date>2017-02-01T18:45:13Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218842#M23921</link>
      <description>&lt;P&gt;@jbailey's provided fix worked for 5.4 &lt;/P&gt;</description>
      <pubDate>Wed, 01 Feb 2017 19:41:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218842#M23921</guid>
      <dc:creator>worshamn</dc:creator>
      <dc:date>2017-02-01T19:41:11Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Nessus Tenable API: Getting error "Fail to decrypt the encrypted credential information - not well-formed (invalid token)"?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218843#M23922</link>
      <description>&lt;P&gt;I am running SC 5.4.2...wonder if that's why I am seeing this. Or maybe I applied the line of code wrong. Could you tell me which line comes before/after the line you added from jbailey? I have code on line 138 so i wasn't sure if it should go before or after said line. &lt;/P&gt;

&lt;P&gt;To be clear i am getting this error message when trying to add a Security Center server to the TA config.&lt;/P&gt;

&lt;P&gt;Thanks @worshamn !&lt;/P&gt;</description>
      <pubDate>Wed, 01 Feb 2017 19:56:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Nessus-Tenable-API-Getting-error-quot-Fail-to/m-p/218843#M23922</guid>
      <dc:creator>jat75</dc:creator>
      <dc:date>2017-02-01T19:56:43Z</dc:date>
    </item>
  </channel>
</rss>

