[Cisco ASA] Support patterns with SGT tag:name as username #8205
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
When using Cisco ASA with the SXP protocol and SGT-tags to write firewall rules, the format of the
idfw_useris presented in their logs asSGT-tag:SGT-name. Multiple message_id are now required to support this change.Sample log:
<140>Oct 06 2023 09:22:19 myAsaHostname : %ASA-4-106023: Deny tcp src outside:192.168.2.2/51982(9999:my_SgtName) dst inside:192.168.2.3/443 by access-group \"outside_access_in\" [0x2a9e189a, 0x0]which will fail with existing GROK patterns as(9999:my_SgtName)is not handled.Fixed by updating
CISCO_USERpattern in each of these messages to supportSGT-tag:SGT-nameChecklist
changelog.ymlfile.Related issues
Screenshots