Closed hipsterjazzbo closed 9 years ago
The default parse implementation stores all of it's session data as an array with a storageKey. I think it would be a good idea to do that here as well, otherwise you could be clearing all session data, when you actually only want to clear the parse session.
I can make a pull request if it helps?
good point, pull request welcome!
On a related note, I did notice the other day that calling Auth::logout() was not unsetting the ParseUser when I do ParseUser::getCurrentUser. I have to explicitly call ParseUser::logout() in my Auth Controller which isn't ideal - need to have a look at this as well
I've actually written a different implementation of your UserProvider which returns an Illuminate\Auth\GenericUser instead of the ParseUser object. So far it seems to work with Facebook login/logout and normal credentials login/logout. I'll try to make a pull request for that as well.
Tested and is working fine
@danjordan did you get a chance to create a PR for your version of the UserProvider? It'd be good to see some sample code to see how you've done it
Nah, I've been on holiday and I've stopped working on the project that required it :(
I'll see if I can have a look into it over the next few days and whack a pull request up next week.
This will need to be tested to make sure that: