For our new friends:

Logto is an Auth0 alternative designed for modern apps and SaaS products. It offers both Cloud and Open-source services to help you quickly launch your identity and management (IAM) system. Enjoy authentication, authorization, and multi-tenant management all in one.

We recommend starting with a free development tenant on Logto Cloud. This allows you to explore all the features easily.

In this article, we will go through the steps to quickly build the Facebook sign-in experience (user authentication) with PHP and Logto.

Prerequisites

• A running Logto instance. Check out the introduction page to get started.
• Basic knowledge of PHP.
• A usable Facebook account.

Create an application in Logto

Logto is based on OpenID Connect (OIDC) authentication and OAuth 2.0 authorization. It supports federated identity management across multiple applications, commonly called Single Sign-On (SSO).

To create your Traditional web application, simply follow these steps:

1. Open the Logto Console. In the "Get started" section, click the "View all" link to open the application frameworks list. Alternatively, you can navigate to Logto Console > Applications, and click the "Create application" button.
2. In the opening modal, click the "Traditional web" section or filter all the available "Traditional web" frameworks using the quick filter checkboxes on the left. Click the "Laravel" framework card to start creating your application.
3. Enter the application name, e.g., "Bookstore," and click "Create application".

🎉 Ta-da! You just created your first application in Logto. You'll see a congrats page which includes a detailed integration guide. Follow the guide to see what the experience will be in your application.

Integrate Laravel with Logto

This guide will show you how to integrate Logto into your PHP web application.

tip:

• The example uses Laravel, but the concepts are the same for other frameworks.

Installation

composer require logto/sdk

Init LogtoClient

First, create a Logto config:

index.php

use Logto\Sdk\LogtoClient;
use Logto\Sdk\LogtoConfig;

$client = new LogtoClient(
  new LogtoConfig(
    endpoint: "https://you-logto-endpoint.app",
    appId: "replace-with-your-app-id",
    appSecret: "replace-with-your-app-secret",
  ),
);

tip:

You can find and copy "App Secret" from application details page in Admin Console:

By default, the SDK uses the built-in PHP session to store the Logto data. If you want to use other storage, you can pass a custom storage object as the second parameter:

index.php

$client = new LogtoClient(
  new LogtoConfig(
    // ...
  ),
  new YourCustomStorage(),
);

See Storage for more details.

Configure redirect URIs

Before we dive into the details, here's a quick overview of the end-user experience. The sign-in process can be simplified as follows:

1. Your app invokes the sign-in method.
2. The user is redirected to the Logto sign-in page. For native apps, the system browser is opened.
3. The user signs in and is redirected back to your app (configured as the redirect URI).

Regarding redirect-based sign-in

1. This authentication process follows the OpenID Connect (OIDC) protocol, and Logto enforces strict security measures to protect user sign-in.
2. If you have multiple apps, you can use the same identity provider (Logto). Once the user signs in to one app, Logto will automatically complete the sign-in process when the user accesses another app.

To learn more about the rationale and benefits of redirect-based sign-in, see Logto sign-in experience explained.

---

note:

In the following code snippets, we assume your app is running on http://localhost:3000/.

Configure redirect URIs

Switch to the application details page of Logto Console. Add a redirect URI http://localhost:3000/callback.

Just like signing in, users should be redirected to Logto for signing out of the shared session. Once finished, it would be great to redirect the user back to your website. For example, add http://localhost:3000/ as the post sign-out redirect URI section.

Then click "Save" to save the changes.

Handle callback

After the user signs in, Logto will redirect the user to the callback URL you set in the Logto Console. In this example, we use /callback as the callback URL:

Route::get('/callback', function () {
  try {
    $client->handleSignInCallback(); // Handle a lot of stuff
  } catch (\Throwable $exception) {
    return $exception; // Change this to your error handling logic
  }
  return redirect('/'); // Redirect the user to the home page after a successful sign-in
});

Implement sign-in route

In your web application, add a route to properly handle the sign-in request from users. For example:

Route::get('/sign-in', function () {
return redirect($client->signIn('http://localhost:3000/callback'));
});

Replace http://localhost:3000/callback with the callback URL you set in your Logto Console for this application.

If you want to show the sign-up page on the first screen, you can set interactionMode to signUp:

Route::get('/sign-in', function () {
return redirect($client->signIn('http://localhost:3000/callback', InteractionMode::signUp));
});

Now, whenever your users visit http://localhost:3000/sign-in, it will start a new sign-in attempt and redirect the user to the Logto sign-in page.

Note Creating a sign-in route isn't the only way to start a sign-in attempt. You can always use the signIn method to get the sign-in URL and redirect the user to it.

Implement sign-out route

After the user makes a signing-out request, Logto will clear all user authentication information in the session.

To clean up the PHP session and Logto session, a sign-out route can be implemented as follows:

Route::get('/sign-out', function () {
return redirect(
  // Redirect the user to the home page after a successful sign-out
  $client->signOut('http://localhost:3000/')
);
});

postLogoutRedirectUri is optional, and if not provided, the user will be redirected to a Logto default page after a successful sign-out (without redirecting back to your application).

Note The name postLogoutRedirectUri is from the OpenID Connect RP-Initiated Logout specification. Although Logto uses "sign-out" instead of "logout", the concept is the same.

Handle authentication status

In Logto SDK, we can use $client->isAuthenticated() to check the authentication status, if the user is signed in, the value will be true, otherwise, the value will be false.

We also need to implement a home page for demonstration:

• If the user is not signed in, show a sign-in button;
• If the user is signed in, show a sign-out button.

Route::get('/', function () {
  if ($client->isAuthenticated() === false) {
    return "Not authenticated <a href='/sign-in'>Sign in</a>";
  }

  return "<a href='/sign-out'>Sign out</a>";
});

Checkpoint: Test your application

Now, you can test your application:

1. Run your application, you will see the sign-in button.
2. Click the sign-in button, the SDK will init the sign-in process and redirect you to the Logto sign-in page.
3. After you signed in, you will be redirected back to your application and see the sign-out button.
4. Click the sign-out button to clear token storage and sign out.

Add Facebook connector

To enable quick sign-in and improve user conversion, connect with Laravel as an identity provider. The Logto social connector helps you establish this connection in minutes by allowing several parameter inputs.

To add a social connector, simply follow these steps:

1. Navigate to Console > Connectors > Social Connectors.
2. Click "Add social connector" and select "Facebook".
3. Follow the README guide and complete required fields and customize settings.

note:

If you are following the in-place Connector guide, you can skip the next section.

Set up Facebook login

Step 1: Set up an app on Facebook App Dashboard

Before you can use Facebook as an authentication provider, you must set up an app on the Facebook developer platform to obtain OAuth 2.0 credentials.

1. Register as a Facebook Developer if you don't already have an account.
2. Visit the Apps page.
3. Click your existing app or create a new one if needed.

tip:

A use case is the primary way your app will interact with Meta and determines which APIs, features, permissions, and products are available to your app. If you need social authentication only (to get email & public_profile), select "Authentication and request data from users with Facebook Login". If you want to access Facebook APIs, choose your preferred use cases - most of them also support integrating "Facebook Login for business" after app creation.

4. After app creation, on the app dashboard page, navigate to Use cases > Facebook Login > Settings or Facebook Login for business > Settings.
5. Fill in the Valid OAuth Redirect URIs with the Logto Callback URI (copy this from your Logto Facebook connector). After users sign in with Facebook, they'll be redirected here with an authorization code that Logto uses to finish authentication.
6. Navigate to Use cases and click Customize of your use case to add the scopes. We recommend adding email and public_profile which are required to implement Sign-in with Facebook in Logto.

Step 2: Set up Logto connector with client credentials

1. In the Facebook App Dashboard, click the sidebar App settings > Basic.
2. You will see the App ID and App secret on the panel.
3. Click the Show button next to the App secret input box to reveal and copy its content.
4. Configure your Logto Facebook connector settings:
   • Fill the clientId field with the App ID.
   • Fill the clientSecret field with the App secret.
   • Click Save and Done in Logto to connect your identity system with Facebook.

Step 3: Configure scopes

Scopes define the permissions your app requests from users and control which private data your project can access from their Facebook accounts.

Configure scopes in Facebook App Dashboard

1. Navigate to Facebook App Dashboard > Use cases and click the Customize button.
2. Add only the scopes your app needs. Users will review and authorize these permissions on the Facebook consent screen:
   • For authentication (Required): email and public_profile.
   • For API access (Optional): Any additional scopes your app needs (e.g., threads_content_publish, threads_read_replies for accessing the Threads API). Browse the Meta Developer Documentation for available services.

Configure scopes in Logto

Choose one or more of the following approaches based on your needs:

Option 1: No extra API scopes needed

• Leave the Scopes field in your Logto Facebook connector blank.
• The default scope email public_profile will be requested to ensure Logto can get basic user info properly.

Option 2: Request additional scopes at sign-in

• Enter all desired scopes in the Scopes field, separated by spaces.
• Any scopes you list here override the defaults, so always include the authentication scopes: email public_profile.

Option 3: Request incremental scopes later

• After the user signs in, you can request additional scopes on demand by reinitiating a federated social authorization flow and updating users' stored token set.
• These additional scopes do not need to be filled in the Scopes field in your Logto Facebook connector, and can be achieved through Logto's Social Verification API.

By following these steps, your Logto Facebook connector requests exactly the permissions your app needs - no more, no less.

tip:

If your app requests these scopes to access the Facebook API and perform actions, make sure to enable Store tokens for persistent API access in Logto Facebook connector. See the next section for details.

Step 4: General settings

Here are some general settings that won't block the connection to Facebook but may affect the end-user authentication experience.

Sync profile information

In the Facebook connector, you can set the policy for syncing profile information, such as user names and avatars. Choose from:

• Only sync at sign-up: Profile info is fetched once when the user first signs in.
• Always sync at sign-in: Profile info is updated every time the user signs in.

Store tokens to access Facebook APIs (Optional)

If you want to access Facebook APIs and perform actions with user authorization (whether via social sign-in or account linking), Logto needs to get specific API scopes and store tokens.

1. Add the required scopes following the tutorial above.
2. Enable Store tokens for persistent API access in the Logto Facebook connector. Logto will securely store Facebook access tokens in the Secret Vault.

note:

Facebook doesn't provide refresh tokens. However, when token storage is enabled, Logto automatically requests a long-lived access token (60 days) upon user authentication. During this period, users can manually revoke access tokens, but otherwise won't need re-authorization to access Facebook APIs. Note: Don't add offline_access to the Scope field as this may cause errors.

Step 5: Test sign-in with Facebook's test users (Optional)

You can use test, developer, and admin user accounts to test sign-in with the app. You can also publish the app directly so that any Facebook user can sign in.

1. In the Facebook App Dashboard, click the sidebar App roles > Test Users.
2. Click the Create test users button to create a testing user.
3. Click the Options button of an existing test user to see more operations, such as "Change name and password".

Step 6: Publish Facebook sign-in settings

Usually, only test, admin, and developer users can sign in with the app. To enable normal Facebook users to sign in with the app in the production environment, you may need to publish this app.

1. In the Facebook App Dashboard, click the sidebar Publish.
2. Fill out the Privacy Policy URL and User data deletion fields if required.
3. Click the Save changes button at the bottom right corner.
4. Click the Live switch button on the app top bar.

Save your configuration

Double check you have filled out necessary values in the Logto connector configuration area. Click "Save and Done" (or "Save changes") and the Facebook connector should be available now.

Enable Facebook connector in Sign-in Experience

Once you create a social connector successfully, you can enable it as a "Continue with Facebook" button in Sign-in Experience.

1. Navigate to Console > Sign-in experience > Sign-up and sign-in.
2. (Optional) Choose "Not applicable" for sign-up identifier if you need social login only.
3. Add configured Facebook connector to the "Social sign-in" section.

Testing and Validation

Return to your PHP app. You should now be able to sign in with Facebook. Enjoy!

Further readings

End-user flows: Logto provides a out-of-the-box authentication flows including MFA and enterprise SSO, along with powerful APIs for flexible implementation of account settings, security verification, and multi-tenant experience.

Authorization: Authorization defines the actions a user can do or resources they can access after being authenticated. Explore how to protect your API for native and single-page applications and implement Role-based Access Control (RBAC).

Organizations: Particularly effective in multi-tenant SaaS and B2B apps, the organization feature enable tenant creation, member management, organization-level RBAC, and just-in-time-provisioning.

Customer IAM series Our serial blog posts about Customer (or Consumer) Identity and Access Management, from 101 to advanced topics and beyond.