WildFire V2 - updating for wf500 api key format #37279
Open
+18
−7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wf500 appliance api key format is 64 chars, updating logic to add that as an option for an API key
content-bot
added
Community
Contribution Form Filled
content-bot
changed the base branch from
master
to
contrib/epartington_epartington-wildfirev2-wf500-apikey-update
|
Thank you for your contribution. Your generosity and caring are unrivaled! Make sure to register your contribution by filling the Contribution Registration form, so our content wizard @MLainer1 will know the proposed changes are ready to be reviewed. |
|
Hi @epartington, thanks for contributing to the XSOAR marketplace. To receive credit for your generous contribution please follow this link. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
wf500 appliance api key format is 64 chars, updating logic to add that as an option for an API key
Contributing to Cortex XSOAR Content
Make sure to register your contribution by filling the contribution registration form
The Pull Request will be reviewed only after the contribution registration form is filled.
Status
Related Issues
fixes: link to the issue
Description
Updating the WildFire V2 integration to account for a 64 char API key generated from WF 500 Appliances. The appliance API ignores the agent=wf500 string added to the integration but this makes the XSOAR code much easier to update by adding a wf500 input option.
Must have