Authorize page shows "Invalid redirect_uri"

Question

daniel.kolb OP

Created Sep ’19

Replies 4

Boosts 0

Views 6.4k

Participants 5

Hi,

i'm trying to implement the Sign in with apple feature to our web login.

I configured the App ID and Service ID and added the return Url "https://example-app.com/redirect".

If i request the following authorize endpoint

https://appleid.apple.com/auth/authorize?response_mode=form_post&response_type=code&client_id=<clientId>&scope=name+email&state=<state>&redirect_uri=https://example-app.com/redirect

i constantly get the error message "invalid_request. Invalid redirect_uri."

Tried a lot of things. Using an uri under the registered domain, used this uri url encoded and not encoded, short uri, long uri, etc.

The uri i used in the link, ist the same i configured in the service ID configuration backend.

I have no idea whats wrong here. Maybe someone had the same problems and any solution for me.

Thanks a lot!

Daniel

Boost

Answer 1

OP

Apple

Sep ’19

Hi Daniel,

To help troubleshoot this, can you report this through the Feedback Assistant providing the following information

1. your client_id

2. Redirect URI

0

Answer 2

cristianocucco OP

Sep ’20

I have quite the same problem...
I configured the serviceId according to documentation, registered the return urls I use as redirecturi in the authorize url, check all parameters (like clientid) are correct.
But I keep getting the very same error: "invalid_request Invalid web redirect url."
Any one who felt into this with any suggestions?

Thanx

P.S. = I already post an issue to Feedback assistant

0

Answer 3

billylouis OP

Mar ’21

same issue here calling a rest API.
I am using customed redirect_uri myapp://.
Please help.

1

Answer 4

sherlockholmesau OP

Apr ’21

I think it's an Apple problem. I cannot make it to work with any browser other than Safari. It works perfectly fine on Edge on iOS but Edge, Chrome, Firefox shows that error. It looks like that they have a Policy error and those scripts are not running on those browsers. Now, it's either they don't give a crap of other browsers and they developers are testing only on Safari, or they are working on it but very slowly...

I tried with multiple laptops, using brand new browsers. Safari and iOS (all browsers) seem the only ones that work.

0