Does getCurrentUser hit the JWT auth service on every request?

Hi all,
I’m asking this to get a better grasp on the mechanism behind service context as well as JWT logOut.

It looks like services are provided a context variable that includes the currentUser. On every request, does Redwood hit the auth service (like Supabase) prior to calling getCurrentUser in order to have the latest user state? Or does it work only with the decoded JWT?

Thank you for any help you can give. Would be fantastic if you can point me to the right place in the source code to look, too!

1 Like