Support Staff22 Posted by Morgan on 19 Jun, 2012 04:24 PM
I have Just pushed this ticket up to high priority and Emailed
Herb to look into this issue again. Sorry about the delay on a
solution so far. I will keep you updated regularly.
Please let me know if you need anything!
Support Staff23 Posted by Herb on 20 Jun, 2012 02:05 PM
The exact same scenario is happening again? I'm having a hard
time replicating this. Notice is responsible for filtering
parameters and the method I've fixed hasn't been changed. The tests
I've added for this are also passing. I've even tried to reproduce
it inside a fresh rails application with the filtering options
Support Staff25 Posted by Herb on 22 Jun, 2012 12:05 AM
Hello again Fredrik!
I know it took me some time to provide a solution but I'm happy
to announce that I have the workaround for your unusual bug.
As we have suspected, it's not the Airbrake gem issue. It's
actually an issue related to Clearance filtering strategies.
Let me explain...
You can see
here that Clearance delegates filtering to Rails. Rails uses
regex matching to determine whether your parameter should be
filtered or not. So remember_token is matched with
/token/ and therefore your parameter gets hidden. We
have an independent filtering strategy which doesn't match the keys
with regex any more.
Removing the token from
filter_parameters in the application.rb
does not help, unfortunately, because Clearance uses initializer
hook to set it up again (defaults to
You have to use after_initialize hook to fix
Add this to your application.rb:
config.after_initialize do |app|
You could also monkeypatch the
to not use regex but I think this is more simple.