[ping_federate] Apply timezone setting correctly in the audit data stream#14222
Merged
chrisberkhout merged 2 commits intoJun 16, 2025
Merged
Conversation
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
|
💚 Build Succeeded
|
efd6
approved these changes
Jun 15, 2025
|
Package ping_federate - 1.0.1 containing this change is available at https://epr.elastic.co/package/ping_federate/1.0.1/ |
This file contains hidden or 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
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
Discussion
Here's how a system test document's output changes with this setting:
The
event.ingestedvalue is the correct ingest time.In 1.0.0, the local time is taken to be UTC, but in the fixed version it is assigned the configured offset and stored as the correct UTC equivalent.
Checklist
changelog.ymlfile.