React Login with Apollo Server, Context, JWT (Apollo Server Tutorial) 

Thanks for the comment! Glad to know that my explanations are helpful, I try to put an emphasis on understanding the thought process so it’s glad to see that’s helping you :)

Thank you for the comment! Gonna keep going :) Appreciate the kind words

Glad to hear the content is helpful, best of luck with your project / deadline!

Comments like this mean a bunch to me! I’ll keep goin! Thanks for watching my stuff and glad it’s valuable to you

Hah that is a high compliment! Thanks for watching I appreciate it

This has to be one of the highest compliments that I have received on this channel, so thank you for that! Thanks for watching the video.

Glad it was helpful, thank you for watching :)

Oh I see, I’ll look into onCompleted 👍 thanks for the comment and info

You are most welcome! Thanks for supporting the channel

Yep you're 100% correct! I mainly opted for the useContext and useReducer as the scope of this project was specifically authentication (and we just need to remove / add token based on certain requests). It is a pretty simple system, if you have a project with a more complicated state it may be worth weighing the options of my solution vs something like Redux. Thanks for the comment :)

No problem! Thank you for your consistent support it means a bunch 😁

Two thoughts come to mind: You’re storing things in headers that could just be in the body of the request instead, so see if anything could be changed there. My second thought is that maybe you have a bunch of cookies stored locally being sent in the request, so clearing cookies may help. I can only really recommend that basic advice but hopefully that helps :)

I have token and I can render email and other info but, how can I use mutations and show full user details from the db

I need to figure out a solid system to do this myself, but I would recommend creating some type of "Get user data from email or userID" in your backend. Then cache this data in your frontend. You could have some global state that holds the users info, and if that object is empty and you have a JWT then you grab the data of that specific user. I recommend this because the JWT on the client just stores the users ID, so you need a way to get info from your backend based off the validated user ID. I also believe that Apollo Client uses the InMemoryCache so if you make the same query with the same inputted JWT it should not even cause your backend to get called again, and would instead just be like "yo, we already called GetUserData( ID: "User_id_here"), just grab it from the cache"

@@CooperCodes Thank you very much Cooper!

@@rezade5960 Just specify what you need back

Full transparency I'm doing some research currently on the best way to make requests based on a certain user. I am planning to release a longer form video soon (2-3 hours) of creating a full website where users can publish articles. My current understanding is that if your context shows User: "Cooper Codes", that User: "Cooper Codes" was set because a validated JWT came from your backend auth server. So I would say that you can trust the context as its information came from a JWT that you "unpacked" and saved. I would just pass along the data in the query for now, but I am looking into it myself as that seems messy. My point though is that if your context is showing User: "Cooper Codes", then that person can do the actions such as create an article as Cooper Codes or like a comment as Cooper Codes. It is tough having an audience! I am not exactly a security expert but want to make sure I am creating tutorials where viewers can create scalable / secure projects as a result :). Trying my best

@@CooperCodes No worries man, I think I figured out a way to do it today (at least it seems to work). What I do now is use GraphQL-shield, there you can make certain rules based on the arguments and context. I for example use the rule const IsAuthenticated = async (root, args, context) { return !!context.currentUser } (wrote it by recollection so might be wrong) and then add that rule to a certain Query/Mutation or Field It might help you out too :) Thanks for the answer

GraphQL shield actually looks pretty great! I may do a video on the basics of GraphQL shield after I get up to speed myself here. Thanks for bringing this to my attention :)

@@CooperCodes did you make video on "how would you handle certain mutations/queries that can only be accessed by certain users/ how to make certain routes secure or access of some users to certain route? I am waiting for your video ?

Ah I forgot about the XSS attacks stuff, I am a dummy. I am creating a full stack project tutorial soon where I will create everything from scratch again and will make sure to incorporate protected routes and a localstorage alternative. Thanks for this info :)

what would an alternative be?

@@stephanpaul8954inMemoryCache is practically same with minor devPreferred based application (smll/big data siz and or the complexities those data handlers