Invalid JWT for edge functions invoking other edge functions after Restore of backup #40250
Unanswered
wallensound
asked this question in
Questions
Replies: 2 comments
-
|
I have issues with invalid JWT for edge functions too. This discussion seems to be giving some direction: https://github.com/orgs/supabase/discussions/29260 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
My issues have been fixed by switching from Legacy JWT Secret to JWT Signing Keys. And also some help via this discussion: #40300 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey, As the title says, we're getting a 401 Invalid JWT on all edgefunction invokes from other edgefunctions. This started happening only after a backup restore. We're not doing any manual auth stuff in our edgefucntions, it is fully relant on supabase automatic addition of the auth header in the invokes. Does anyone have any insight into why this might be happening and if the issue is on our side or if it's a supabase bug?
Beta Was this translation helpful? Give feedback.
All reactions