Avoid leaking Authorization request headers in cleartext for Phoenix Controllers #160
  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.
  
    
  
    
Hello !
Similar to #156 I ran into the issue where my Phoenix application has some controllers that are receiving API requests that use an Authorization header. Similar to how the
ErrorTracker.Integrations.Plugdrops thecookieheader, as it is considered sensitive, I strongly believe that we should avoid storing and showing theAuthorizationheader in clear text, as this could allow for an attacker in a Privilege Escalation attack.For now all I've done is the following
ErrorTracker.Integrations.PlugErrorTracker.Integrations.Plugto avoid logging theAuthorizationandCookieheadersGiven that there wasn't any existing tests for this module, I'm open to feedback to make these tests more sensible to other users of this codebase.
I'd also like to consider, in a follow-up PR, to obfuscate, rather than avoid logging. In the context for an error occurrence, we would see something like the following
Fixes #156
Fixes #150