Login Box Integration

When proceeding with your Frontegg's Login Box Integration, your next steps depend on whether you opt for the Hosted or Embedded option. Read on to learn more about each option.

Hosted or Embedded Login?

Embedded and hosted logins both use the same pre-built but highly customizable login box and robust authentication functionality.

The main difference is that embedded login allows you to embed the login box into your code, whereas with hosted login you host the login box on Frontegg servers.

With Embedded Login you import one of our software packages into your application and then use components, links, and subdomains to handle authentication for you with. You actually embed the login box into your code. When your customers click a button on your application to log in or sign up, your application handles authentication for you.

πŸ“˜

Embedded Login Limitations

Embedded login operates using cross-site authentication using cross-site http-only cookies. For this to operate flawlessly on modern browsers (which block 3rd party cookies by default) it is required to Add Custom Domains

With Hosted Login Frontegg hosts the authentication. When your customers click a button on your application to log in or sign up, your application redirects the user to the login page hosted by frontegg. The user is then authenticated and redirected using Open ID connect protocol back to your application.

This mode is extremely useful if your application is protected using standard API gateways such as Kong or NGINX

An additional very popular use case is when the login dialog is used by multiple applications and you want to share the user pool. In these use cases, hosted login will be a perfect choice.

Moving from Hosted to Embedded Login

If you are using Frontegg's Hosted Login and wish to increase your code flexibility and customization options, you may choose to move to Embedded login. To do so, you will need to do the following:

STEP 1: Change Cookie Policy

Change cookie policy to none using the Frontegg API. You can use postman or any other api tool.

Call the update identity management configuration route.

Send the following payload in the POST body.

{
   cookieSameSite: NONE
}

πŸ“˜

Authentication APIs

Learn how to get started with the Frontegg API and how to authenticate as a vendor.

STEP 2: Update Redirect URLs

Your application uses Redirect URLs for various features, like Email Templates, Social Logins, and SSO.

How you update the Redirect URLs depends upon whether you are using the {{LOGIN_URL}} template in your Redirect URLs.

Here is an example of Email Templates using the {{LOGIN_URL}} template as their base URL.

If all of the Redirect URLs on Email Templates, Social Logins, and SSO use the {{LOGIN_URL}} template.

Change your Login URL to be the same as your App URL in Authentication > Login method. Your app URL is located under the Settings tab of each application (go to the single account view via the Applications tab.


πŸ“˜

Allowed Origins

Go to **Env Settings ➜ Domains and add your Login URL and App URL (if using multiple applications, add all of your applications URLs)


If the Redirect URLs on Email Templates, Social Logins, and SSO do NOT use the {{LOGIN_URL}} template.

Check the following to make sure the Redirect URLs use {{APP_URL}} as the base.

Here is an example email template with the Redirect URL using {{APR_URL}} as its base.

STEP 3: Integrate Embedded

πŸ“˜

If you already integrated your application with Frontegg

You just need to change option hostedLoginBox to false in your Frontegg wrapper.

Or follow the relevant guide to integrate embedded login into your code.

STEP 4: Turn Off Hosted

Go to Environments ➜ [NAME OF ENVIRONMENT] ➜ Login Method.

Choose Embedded login.

🚧

Turning off 'Hosted Login'

Please complete the steps above before turning off hosted login. Otherwise, your users will no longer have access to the login/signup page.



🚧

Hosted Login Status

Note the you need to manually update the hosted login status for each environment separately.