#bungee_api
brazen oliveBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- bungee_api, 1 day ago, 6 messages
vernal citrusBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1258049790856532061
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
astral trail
I don't see a way to reset oauthContext
What's your end goal? Why do you need to it?
Have you tried invoking createOAuthState again? I wonder if that invalidates current context
glass rock
When performing the OAuth PKCE flow and the redirect occurs, we need to check for the code and verifier in the app to retrieve the token. This is handled in React inside a useEffect. The problem is that if the user logs out, closes the app in the drawer, and opens it again, the verifier and code are still present, causing the user to be automatically signed in once more.
astral trail
Have you tried invoking `createOAuthState` again? I wonder if that invalidates c...
Essentially, when you refresh the page createOAuthState is invoked again. I wonder if it does the same thing if you call it programatically without the refresh
glass rock
Let me give it a quick try! Brb
Didn't work 😦 - the context still holds the previous verifier and code
astral trail
Hmm okay. Yeah I don't think there's a way to reset these programatically. I'd recommend writing in via our support team to raise this as feature request
https://support.stripe.com/?contact=true
glass rock
Sure! Given the current PKCE flow, is it safe to assume that this issue affects all users implementing oauth? It seems that users need to listen for the verifier and code in a useEffect after the redirect to continue the flow.
astral trail
Yes, I believe so
glass rock
Okok, I will fill this a bug then! Thank you for your time!