invalid_request - Invalid web redirect url.

Question

PUSHArtst OP

Created 1w

Replies 1

Boosts 0

Participants 1

Hi,

I have setup Apple SignIn on a platform i am developing and configure all the required Service IDs and redirect URLs.

The integration worked up until I moved the platform to a new domain name last friday. I have reconfigured the list of allowed domains and redirect urls to the new domain name, and removed all the mentions of the former one. Since then, when trying to Sign In with Apple, I am greated with the following error : " invalid_request - Invalid web redirect url".

I have also observed that if i manually change the domain name in the redirect_uri parameter but keep the rest of the OAuth URL identical, the error disappears. This should not be possible since the former domain name has been completely removed from the Service ID configuration.

Is there a propagation time for this ? And if so, it seems very long (5 days and pending).

I have checked and rechecked and tripled checked my configuration, every time by going in my dev account > Identifiers > Service IDs > Sign In with Apple > Configure, then clicking Done > Continue > Save.

I can confirm that :

the redirect domains and URLs there are correct, and no mention of the former domain name is present
I can still login using the former domain redirect urls (so my implementation is valid, but the configuration is not up to date)
the new redirect urls are still not working as of now
https is included in the redirect_urls, no trailing slash is present. again, the same URLs but with a different domain name were configured and worked (if anything, still work) properly
TLS 1.3 connection (i know 1.2 is a requirement)

Any advice would be welcome

Boost

Answer 1

PUSHArtst OP

1w

To anyone reading this, i have no clue what changed, i have tripled checked before posting this, as I had done the last 5 days every day. I just tested in Safari (hadn't tested there before, only the other two major browsers), and got presented with the native SignIn dialog with TouchID, which immediately worked. Went back to the other browsers to check again, and the tabs i had left opened on the "invalid_request" error from 5min before posting this, magically worked now. I have not changed a thing in my config, except maybe saving again what was already there. As i had done every day since last friday.

I am glad the issue now seems resolved, but I would still consider that this propagation issue be fixed. On other OAuth providers it took less than a minute for this configuration to be updated and work. Configure OAuth shouldn't feel so obscure.

0