OAuth2 integration no longer working (?)

[caue]

1. My goal: Fix my OAuth2 connection
2. Issue: Since early Monday (14th April, 2026) my OAuth2 integration is no longer working.

We built the OAuth2. connection to AWS's Cognito four months ago and it being working flawlessly, since the morning however I'm getting the following error:

It seems resource is now mandatory, at least this is what I can infer from the URL “https://oauth.retool.com/oauth/user/oauthcallback?error_description=identifier+for+resource-binding+must+have+a+valid+URI+scheme&state=xxxxxx&error=invalid_request”

If I pass a mocked resource, localhost for example, I'm able to actually get to Cognito login page, but after I proceed with the login I get the following error:

I can't find anything on the changelog of stating anything that could affect the OAuth2 integration. I can confirm that Cognito is working as we also use it in other integrations, as well as I did a few tests to validate it.

Do anyone have a clue of what could be happening?

[aolvictim]

We have exactly the same problem all in a sudden. No change to our Retool code or Cognito config. Cognito doesn’t like empty resource=

[caue]

If I may ask, have you managed to solve this issue?

[JayL]

Hey yall! Thanks for this report. We’re aware of the issue and are working on a fix.

In the meantime, if you see an issue with an invalid request or redirect, you may be able to delete the empty &resource= part of the URL and hit enter to proceed.

[JayL]

Just wanted to give yall the headsup that we rolled back the Resource field so this should back up and running as expected. Thanks for your patience!