Environment settings
/
Hosted vs embedded
Last updated

Hosted vs embedded implementation

Integrate Frontegg into your app using embedded components or a hosted version on Frontegg's servers, which is built on OAuth2 standards. Each option includes a customizable, pre-built login box with powerful authentication features. The key distinction is that the hosted version supports using Frontegg as an IdP, right out of the box.

By default Frontegg's integration uses the hosted mode but if you'd like to switch to embedded, you can do that from [ENVIRONMENT] → Authentication → Login method.


hosted-embedded


If you choose the hosted method, you can still use the embedded option by setting hostedLoginBox:false and implementing embedded login authentication methods. Refer to the client-side SDKs guide for more details on embedded login.

Updating login URLs

Applications in your environment utilize the Login URL and App URL fields as variables across various environment settings, including Email Templates, Allowed Origins, and Hosted Login Redirects, Social login redirects and SSO (SP) redirects. These settings automatically reference the values configured for each application's Login URL and App URL.


hosted-embedded

Normally when an application uses a hosted login the fields will look as below:

  • Login URL - https://[frontegg-or-custom-domain]/oauth
  • App URL - https://[your-application-url], i.e https://acme.com

when an application uses an embedded login the fields will look as below:


  • Login URL - https://[your-application-url], i.e https://acme.com
  • App URL - https://[your-application-url], i.e https://acme.com

If you're switching from a hosted implementation to embedded, make sure to update
the Login URL to match your implementation.