[Cisco FTD] Fix the handling of spaces in 113005 messages #8798
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
bhapas
added
bug
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
bhapas
force-pushed
the
sdh_4227_cisco_ftd
branch
from
b59dacd
to
5501462
Compare
chemamartinez
approved these changes
Dec 27, 2023
|
Package cisco_ftd - 3.0.2 containing this change is available at https://epr.elastic.co/search?package=cisco_ftd |
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.
Proposed commit message
This PR fixes the parsing of a 113005 Cisco ASA message as follows:
The
grokprocessor failed because of an unexpected space afterAAA user authentication Rejected. This can potentially happen with every field so now the pattern expects that every value can be followed by spaces.Checklist
changelog.ymlfile.