<![CDATA[403 error when registering with Apple]]>We are seeing a 403 error when completing registration with the Apple identity provider. It appears to when 302 redirecting to complete-registration. Do you have insight to why the 302 is being thrown?

More details: it appears only to be when using Safari and a webview. It began happening recently (in the past few weeks) and worked before. We're using FusionAuth's hosted login pages.

Could this be a CORS issue?

]]>https://fusionauth.io/community/forum/topic/699/403-error-when-registering-with-appleRSS for NodeMon, 08 Jun 2026 11:24:56 GMTTue, 29 Dec 2020 14:55:51 GMT60<![CDATA[Reply to 403 error when registering with Apple on Tue, 29 Dec 2020 14:58:02 GMT]]>Yes, just confirmed the fact that this is a Safari only issue. Only Safari seems to be doing this, we don’t return a 403 so this must a CORS failure. Perhaps Apple is sending additional headers on the request when using Safari that need to be accounted for in the Allowed headers.

I added GET to the allowed methods for CORS and it works that seems to allow it to work in Safari. Please test and let me know.

The redirect workflow looks to be different in Safari when using native controls vs Chrome or other browsers.

]]>https://fusionauth.io/community/forum/post/2073https://fusionauth.io/community/forum/post/2073Tue, 29 Dec 2020 14:58:02 GMT