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
Currently, the login process requires the browser to reload. This is annoying when the user fails to login due to incorrect credentials or some other reason.
The text was updated successfully, but these errors were encountered:
@itaditya can you please suggest a better workflow for this? When we were building the connect, then we tried to change this but due to constrained setting of allauth package, we could not do it. Please let me know if you suggest something better.
@deshraj , I read about django-allauth but I'm unable to understand how it works at the core. So if you can give a little idea of it's mechanics then it would be great. Also, some questions -
does it use JWT?
does it uses page reload to save session data in the browser's cookie or whatever..
I think it would require a non-trivial amount of effort and time to change the workflow. Also, the time and effort that you guys will spend in implementing this are not worth it. Please feel free to close it. :)
I was just thinking, that we can ease the process when the login attempt fails like incorrect data or something else, if there are no such issues then django-allauth may proceed as usual
Currently, the login process requires the browser to reload. This is annoying when the user fails to login due to incorrect credentials or some other reason.
The text was updated successfully, but these errors were encountered: