okta: make extra efforts to extract risk information from debug_data #4806
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
efd6
added
bug
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
🤖 GitHub commentsExpand to view the GitHub comments
To re-run your PR in the CI, just comment with:
|
🌐 Coverage report
|
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
kcreddy
approved these changes
Dec 14, 2022
packages/okta/data_stream/system/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
The format used by Okta in the debug data fields are not generally parsable with a kv processor, but the risk level and reason fields in are of enough value to make some extra effort to recover if the kv processor failed. In this case also retain the original object in case there were other fields in the object.
6 tasks
|
Package okta - 1.12.1 containing this change is available at https://epr.elastic.co/search?package=okta |
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.
What does this PR do?
The format used by Okta in the debug data fields are not generally parsable with a kv processor, but the risk level and reason fields in are of enough value to make some extra effort to recover if the kv processor failed. In this case also retain the original object in case there were other fields in the object.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
field [okta.debug_context.debug_data.flattened.risk] does not contain value_split [=]#4783Screenshots