@mehamm

I am working on a multi tenant guide. Thank you very much for your feedback; I'll make sure to include it.

As you continue to build out your multi tenant application, please continue to post on the forum about your progress and/or any other questions. 🙂

We often hear our multi tenant support is a differentiator for FusionAuth, and would love to make it easy/clearer for everyone.

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.

The mobile app really shouldn’t be calling FusionAuth APIs. You should be using your backend to call FusionAuth. Usually, this is a proxy style setup, as outlined in this post about OAuth and React. This will work for both OAuth and regular API calls.

If you really want the mobile app to call the OAuth flow directly, make sure you follow the best practices from RFC 8252 (use the browser, not an embedded webview). Here's a React Native tutorial that you can adapt.