My goal: Set up GitLab OAuth2 integration that silently refreshes tokens in the background. Issue: Refreshing the tokens works, but Retool still prompts for a re-auth until I refresh the page. When I do so, the token has been refreshed in the background and the API call works. Steps I've taken to…

GitLab OAuth prompts for re-auth despite refresh token working correctly

Mike_M June 25, 2025, 7:35pm 5

Hi @dennisameling, I looked through this guide on troubleshooting resource connections and found something that may help. If you check the box "Share credentials between users" it may fix this problem?

Let me know!

Topic		Replies	Views
Google OAuth2 refresh tokens 💬 Queries and Resources oauth2 , authentication , welcoming-replies	4	1142	September 23, 2024
Gmail API + OAuth 2.0 - second auth flow does not save access/refresh token 💬 Queries and Resources bug , api , oauth2 , rest-api	5	54	December 15, 2025
OAuth2 client credentials flow is not issuing updated tokens after expiry 💬 Queries and Resources oauth2 , authentication	7	836	April 3, 2025
OAuth 2.0 token refresh does not block or retry parallel requests (self-hosted Retool) 💬 Queries and Resources	2	11	January 23, 2026
OAuth2.0 Authentication with Retool for API Access 💬 Queries and Resources	2	478	February 22, 2024

GitLab OAuth prompts for re-auth despite refresh token working correctly

Related topics