You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi folks, apologies if there's a better place to bring up this sort of inquiry.
I am setting up account lockouts and wanted to emit audit log events when a lockout occurs. I have my lockout_parameters set to AXES_LOCKOUT_PARAMETERS = ["ip_address", ["username", "user_agent"]] but when I emit an audit log I want to differentiate between when an ip_address alone gets locked out versus when a username+user_agent gets locked out. I'm fairly new to Django's signal handling, but as far as I can tell, it's not currently possible for a signal handler to determine which parameter caused a lockout, is it?
Do we think this would be something that could be implemented in a reasonable way? I think it could be useful just in general to be able to differentiate behaviors when a lockout occurs based on what parameter(s) caused the lockout.
The text was updated successfully, but these errors were encountered:
Hi folks, apologies if there's a better place to bring up this sort of inquiry.
I am setting up account lockouts and wanted to emit audit log events when a lockout occurs. I have my lockout_parameters set to
AXES_LOCKOUT_PARAMETERS = ["ip_address", ["username", "user_agent"]]
but when I emit an audit log I want to differentiate between when anip_address
alone gets locked out versus when a username+user_agent gets locked out. I'm fairly new to Django's signal handling, but as far as I can tell, it's not currently possible for a signal handler to determine which parameter caused a lockout, is it?Do we think this would be something that could be implemented in a reasonable way? I think it could be useful just in general to be able to differentiate behaviors when a lockout occurs based on what parameter(s) caused the lockout.
The text was updated successfully, but these errors were encountered: