✅ - Using user pool custom domain instead of default cognito domain for google sign in redirect uri? | AWS Amplify | Page 1

radiant monolith Jul 1, 2024, 3:42 PM

#

Implemented google sign in, but in order to get our oauth app in production and verified with google, we have to verify all domains. Can't verify amazoncognito.com which is the default cognito domain. I set up a custom domain for the user pool, but amplify itself seems to automatically use the default domain as a redirect uri, can I override this with the custom domain somehow?

thin wren Sep 17, 2024, 5:31 PM

#

Did you solved this problem?

twilit solstice Nov 18, 2024, 3:52 PM

#

@radiant monolith, apologies that a response on this thread took so long. If you're still experiencing this, it might be due to the config not being updated with the custom domain that's being used. Can you double check that the redirectSignIn and redirectSignOut have values that align with what's configured within the Cognito console?

hazy otterBOT Nov 25, 2024, 8:39 PM

#

✅ - Using user pool custom domain instead of default cognito domain for google sign in redirect uri?

#✅ - Using user pool custom domain instead of default cognito domain for google sign in redirect uri?