Add warden.user rack data to default filters list #436
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
snmaynard
reviewed
Mar 2, 2018
tobyhs
approved these changes
Mar 5, 2018
|
We would whitelist the fields in the session tab and then if warden changes we would be alerted. |
snmaynard
reviewed
Mar 5, 2018
spec/report_spec.rb
Outdated
| } | ||
| }) | ||
| report.meta_data.merge!({ | ||
| :wardenUser => { |
There was a problem hiding this comment.
Can we put this in a representative place in the payload?
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.
Ensures rack data containing warden user id's and partial encrypted password hashes will be correctly filtered by default.
Warden data will still be available as metadata added via the Warden user middleware.