Skip to content

Commit

Permalink
fix the display of the credentials parameter (#20345)
Browse files Browse the repository at this point in the history
  • Loading branch information
yaakovi committed Aug 2, 2022
1 parent 83ee37f commit cbbb989
Show file tree
Hide file tree
Showing 4 changed files with 8 additions and 4 deletions.
2 changes: 1 addition & 1 deletion Packs/FeedTAXII/Integrations/FeedTAXII2/FeedTAXII2.yml
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ configuration:
name: url
required: true
type: 0
- display: Username / API Key (see '?')
- display: Username / API Key
name: credentials
required: false
type: 9
Expand Down
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
### Using API Token authentication
In order to use the integration with an API token you'll first need to change the `Username / API Key (see '?')` field to `_api_token_key`. Following this step, you can now enter the API Token into the `Password` field - this value will be used as an API key.
In order to use the integration with an API token you'll first need to change the `Username / API Key` field to `_api_token_key`. Following this step, you can now enter the API Token into the `Password` field - this value will be used as an API key.


### Using custom authentication header
In case the TAXII 2 server you're trying to connect to requires a custom authentication header, you'll first need to change the `Username / API Key (see '?')` field to `_header:` and the custom header name, e.g. `_header:custom_auth`. Following this step, you can now enter the custom authentication header value into the `Password` field - this value will be used as a custom authentication header.
In case the TAXII 2 server you're trying to connect to requires a custom authentication header, you'll first need to change the `Username / API Key` field to `_header:` and the custom header name, e.g. `_header:custom_auth`. Following this step, you can now enter the custom authentication header value into the `Password` field - this value will be used as a custom authentication header.

### Complex Observation Mode
Two or more Observation Expressions MAY be combined using a complex observation operator such as "AND", "OR", and "FOLLOWEDBY", e.g. `[ IP = 'b' ] AND [ URL = 'd' ]`. These relationships are not represented in CORTEX XSOAR threat intel management indicators. You can opt to create them while ignoring these relations, or you can opt to ignore these expressions - if you choose to ignore these expressions, then no indicators will be created for complex observations.
4 changes: 4 additions & 0 deletions Packs/FeedTAXII/ReleaseNotes/1_1_9.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@

#### Integrations
##### TAXII 2 Feed
- Documentation and metadata improvements.
2 changes: 1 addition & 1 deletion Packs/FeedTAXII/pack_metadata.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
"name": "TAXII Feed",
"description": "Ingest indicator feeds from TAXII 1 and TAXII 2 servers.",
"support": "xsoar",
"currentVersion": "1.1.8",
"currentVersion": "1.1.9",
"author": "Cortex XSOAR",
"url": "https://www.paloaltonetworks.com/cortex",
"email": "",
Expand Down

0 comments on commit cbbb989

Please sign in to comment.