Understanding the architecture of Stytch Connected Apps authentication
This diagram shows the relationship between your connected apps and the centralized authentication service. Multiple apps (acmecalendar.com, acmemail.com) all point to a single auth service (accounts.acme.com) which handles authentication through two main endpoints: /idp for OAuth authorization and /login for user authentication.
Auth Service
A centralized auth service containing two routes: /idp which loads the Identity Provider component and /login which loads a standard Stytch powered authentication component.
Connected App
An app connected to the centralized Auth Service (Acme Mail and Acme Calendar in this example). A Connected Apps Client will need to be created in Stytch for each Connected App.
<B2BIdentityProvider />
A Stytch component that handles the OAuth flow.
<StytchB2B />
A Stytch component that loads prebuilt authentication flows.