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

[dennisameling]

1. My goal:
   Set up GitLab OAuth2 integration that silently refreshes tokens in the background.
2. 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.
3. Steps I've taken to troubleshoot:

• Validated that the auth verification endpoint is configured correctly in Retool
• Set the access token lifespan to 7200, which is in line with the GitLab documentation.

4. Additional info: (Cloud or Self-hosted, Screenshots)
   We're using the cloud versions of both Retool and GitLab.

GitLab OAuth config:

Auth verification endpoint:

Yet the app that's using this resource is prompting for a re-auth every now and then:

When looking in the debug tab of the app when this happens, I'm seeing the following:

Any hints as to where we should be looking would be greatly appreciated. Thanks!

[Mike_M]

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!