There is a known issue with performance if you are running our intel based Docker image on an M1 or other ARM based system.

We will be pushing out support for M1/ARM shortly..
We have a test image out there if you want to try it - using this one should provide much better performance.
https://hub.docker.com/layers/fusionauth/fusionauth-app/1.32.1_multi/images/sha256-da71d5be2bc849ef9d4e1205508fa34994973d75798a47cab9a8484ee2592ff7?context=explore

is the latest current experimental version. Make sure you choose the arm64 based image.

The best solution is to migrate first name and last name from your previous provider.

I don’t know of any other options. Apple is stingy with those details about the user.

Yes we support this. These docs should help you through this process.

https://fusionauth.io/docs/v1/tech/identity-providers/apple/#building-your-own-integration

https://fusionauth.io/docs/v1/tech/apis/identity-providers/apple/#complete-the-apple-login

From the latter doc:

Using this API you can pass that id token returned from Apple to FusionAuth and we will complete the login workflow and reconcile the user to FusionAuth.

Reconciliation means that the user is created in FusionAuth if needed, a JWT is generated, and a login session is created as well. They will essentially look like any other FusionAuth user.

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.