-
Notifications
You must be signed in to change notification settings - Fork 149
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
authentication_classes = () in password validate/confirm endpoints? #67
Comments
yeah. it seems authentication needs to be changed on these views to allow unauthenticated access to the views. |
I ended up just inheriting from all the views and adding my own throttling and authentication settings via the |
After completing this i suggest the documentation just mention how to inherit from the existing view classes. There are many permission possibilities and throttling possibilities. |
Hey @guzzijones , could you show how to inherit from the existing view classes? I have tried to override them in this way:
And adding these views into urls.py:
But I get: I agree with you saying that this should be inserted in the documentation. |
Hi everyone, I'm facing the same problem. I've created a pull request to solve this issue #148 |
I found that if the user has an (invalid) local
Bearer: <hex>
cookie that gets sent as a header, the three views can fail authentication and return a 401. Is this intentional? Shouldn't these views haveauthentication_classes = ()
so they work even if there's a leftover token in the browser?There might be a security-related reason for it to be this way but I'm not sure I can think what it is.
The text was updated successfully, but these errors were encountered: