-
Notifications
You must be signed in to change notification settings - Fork 673
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Axes messages #124
Comments
Hi. By any chance did you figure this out? |
@patrickoramah are you confused about the lockout URL that's returned? Is there a certain Django axes message that is sent on lockout? |
@errrken Hi. I have the same problem. I'm using DRF and simplejwt. When I get lockout I can't get template to work. Have you found the solution maybe ? cheers |
Like what OP said, you'll need to override the serializer. Go to
django-axes, find their middleware, and see what attributes they're setting
on the request object using the AxesProxy. Then in your inherited
serializer, check for that attribute. You should be able to use the new
auth rule (sorry it's not documented. Search it up in the PRs) to allow
authorization to continue which should then properly redirect to your Axes
view.
…On Tue, Dec 15, 2020 at 3:49 PM Damian Kuich ***@***.***> wrote:
@errrken <https://github.com/errrken> Hi. I have the same problem. I'm
using DRF and simplejwt. When I get lockout I can't get template to work.
Have you found the solution maybe ? cheers
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#124 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOLG4VUKZPD52EJV24MCIUDSU7DWJANCNFSM4HSAWUTA>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
When using django-axes, and I get a lockout, I would like this to be shown in the error message instead of the "No active account found with the given credentials". Do I have to override TokenObtainSerializer in order to achieve this?
Thanks
The text was updated successfully, but these errors were encountered: