User object from the SDK is not set about fusionauth-react-sdk

[mooreds]

I'm going to track the access cookie remaining in a separate issue: #27

[joshdura]

Not sure if this is part of the same issue or not, but will post this here until confirmed otherwise. When I login for the first time (when the access_token cookie doesn't exist and the POST /token-exchange endpoint is called), the user cookie is correctly populated. However, when I logout and then log back in, the access_token cookie remains the same, and the user cookie is set to the string undefined.

[mooreds]

Hmm, seems to me that the access_token needs to be removed on logout.

[joshdura]

Hmm, seems to me that the access_token needs to be removed on logout.

Yeah, that's what I was thinking as well. Is that something that should be handled on my side? Or something that the SDK should be taking care of?

[mooreds]

I think the SDK should handle that. I think we can get that fixed in the next few days.

[mooreds]

Okay, heard a bit from one of the devs who wrote this. They pointed me to https://github.com/FusionAuth/fusionauth-example-react-sdk/blob/main/server/routes/token-exchange.js#L35 and said that for some reason it isn't being populated. Need to do some more research.

[JakeLo123]

Looking at the provider code, there are some instances where user and isAuthenticated are not set at the same time. There are cases where they may be out of sync. We can adjust the code to handle these and add tests to watch for future breakage.

This PR inadvertently addresses some of it — we can address the rest once it goes in.