Authentication Pattern
Opened this issue · 1 comments
Hi @bertho-zero
I understand that this repo is not being maintained due to lack of time on your end. However I am sure many have and are still taking advantage of this great repo.
I have a simple question that needs a bit of explanation for the sake of my understanding and wanting to go ahead and update this repo for my own use.
Question I have is on Authentication. Once the user is logged in, what is causing the user to stay authenticated. My understanding is that the saved token and cookie causes the persist of the user. The issue I am having is that after updating all the @feathersjs/... packages, user can no longer stay logged in even though the cookie is still retained on the browser side.
As the App container fetches and dispatches loadAuth() it does not get the user back from the server. Only if a route is changed then the app fetches the user otherwise just refreshing the page makes the app lose the persisted state.
Any help will be appreciated ?
Hi, and thank you !
This is an old version of feathers, I'm not sure I can help you as I don't use feathers authentication on the professional side yet.