[Cisco ISE] Keep cisco-av-pair values with embedded 'equals' as keywords#18964
Conversation
|
Pinging @elastic/integration-experience (Team:Integration-Experience) |
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
🚀 Benchmarks reportTo see the full report comment with |
…integration-update-to-1323
Niceplace
left a comment
There was a problem hiding this comment.
Given we paired on this I feel comfortable giving my 👍 LGTM and all tests are green so that's a good sign. I have one question and one nitpick, but nothing blocking.
| def rest = v.substring(firstEq + 1); | ||
|
|
||
| // Only mdm-tlv uses nested subkeys (device-platform=win, ...). Other pairs | ||
| // (e.g. FQSubjectName=...cn=...,ou=...) may contain '=' in the value and must stay scalar. |
There was a problem hiding this comment.
Question: Would it make sense to link to official cisco docs or spec that would justify what top-level keys may contain = in the value and which ones may not ? This could help with future similar issues and possibly allow us to pre-emptively fix other fields that would be in the same situation.
Co-authored-by: Simon Beaulieu <Niceplace@users.noreply.github.com>
💚 Build Succeeded
History
|
|
Package cisco_ise - 1.32.4 containing this change is available at https://epr.elastic.co/package/cisco_ise/1.32.4/ |
Proposed commit message
Keep cisco-av-pair values with embedded 'equals' as keywords
Changes:
Fixes the Cisco ISE passed authentications ingest pipeline so
cisco-av-pairvalues that contain extra=characters are parsed correctly (kept as full keyword strings). Adds pipeline tests, field/docs updates, changelog entry, and a package version bump.Checklist
changelog.ymlfile.