Skip to content

Modification of asset keeping cached info. #63

Description

@wzhiana

Name of the app
http_app

Describe the bug
After initial setup, where we were using basic credentials for authentication on endpoint, we tried to switch to token autherization. And suprizingly we identified, that soar keeps using old username/password and form doesn't clean it.

looks like save button ignores empty fields, which is not expected.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'asset management'
  2. update values, delete old values
  3. save
  4. do test and be surprised that nothing works.

Expected behavior
SOAR updates asset info AS IT IS PROVIDED IN FORM.
if field has no value - there should be no data!

Screenshots
no screenshots, but i had to modify http_connector.py to get extra data. and there i saw that script has some input in username and password. so it is not even trying to use token.

Splunk SOAR Version (please complete the following information):

  • on-prem, al23
  • soar : 7.1.0.225
  • http_app : 3.7.9

Additional context
i managed to find workaround:

curl -k -u 'username:pass' \
  -H "Content-Type: application/json" \
  -X POST "https://soar_url/rest/asset/60" \
  -d '{
    "configuration": {
      "base_url": "https://some_endpoint/rest/api/",
      "test_path": "content",
      "auth_token_name": "",
      "auth_token": "",
      "username": "",
      "password": "",
      "oauth_token_url": "",
      "client_id": "",
      "client_secret": ""
    }
  }'

this wipes setting. And basically i filled fields with this restapi to override settings and it started to work.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions