Cannot access POST data from AuthenticationBackend
See original GitHub issueCommon use case: Retrieve POST data sent by an HTML login <form>
to validate within AuthenticationBackend
middleware.
- Passing usernames / passwords over GET with passwords visible in the URL is not acceptable.
- Passing Authorization headers along with a form requires Javascript, a poor solution.
Any common techniques or help appreciated.
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (6 by maintainers)
Top Results From Across the Web
No Django POST data when sent over a form? - Stack Overflow
1 Answer 1 ... In request.POST you don't have keys from id attribute, but from name . Add it to inputs and you're...
Read more >Customizing authentication in Django
An authentication backend is a class that implements two required methods: get_user(user_id) and authenticate(request, **credentials) , as well as a set of ...
Read more >Kubernetes - Auth Methods | Vault - HashiCorp Developer
curl \ --request POST \ --data '{"jwt": "<your service account jwt>", ... However, the client tokens cannot be revoked before their TTL expires, ......
Read more >Requests - Django REST framework
data. request.data returns the parsed content of the request body. This is similar to the standard request.POST and request ...
Read more >Authenticate with a backend server - Google Developers
... try restarting your device. Your browser can't play this video. ... Then, send the ID token to your server with an HTTPS...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I don’t like closing issues without resolution. Thanks for reopening it. 🙏
No problem, I was just under the impression that Starlette wanted to get to 0 issues before 1.0, and this is only a DX issue that may never be resolved.