Connecting Facebook Login

To let users of your service sign up with a Facebook account, you first register your service with Facebook and receive an App ID and an App secret.

This page covers the order in which you receive the App ID and the App secret. Putting the two values you received into WEEGLOO is covered in Putting the App ID and App secret into WEEGLOO.

Getting the App ID and App secret from Facebook

Sign in with your Facebook account, then work through the four steps below in order. What you do here costs nothing.

1

Creating an app

If you already have an app you have been using and that app's Use cases screen has a Facebook Login item, you can use that app as it is instead of creating a new one. In that case, skip this step and go on to Adding the email permission.

You go through five screens in order: App details, Use cases, Business, Requirements, and Overview.

  1. Open the app list screen (https://developers.facebook.com/apps (opens in a new tab)).

  2. Click Create App.

    The Apps screen with no apps at all. The No apps yet notice and the Create App button are in the middle

  3. In App name, enter a name you will recognize later (for example, Cozy Closet).

  4. In App contact email, enter the address that will receive inquiries. This is the address Facebook uses when it contacts you about this app.

  5. Click Next.

    The App details step of the step-by-step screen. The App name box and the App contact email box are there, with the Next button at the bottom right

  6. Check Authenticate and request data from users with Facebook Login.

  7. Click Next.

    The Use cases step of the step-by-step screen. Authenticate and request data from users with Facebook Login is checked among the six items

  8. Choose the I don’t want to connect a business portfolio yet. option. As the screen explains, you can add a business portfolio later.

  9. Click Next.

    The Business step of the step-by-step screen. The I don’t want to connect a business portfolio yet. option and the notice that there is no business are visible

  10. Read what is on the Requirements screen and click Next. There is nothing to enter.

    The Requirements step of the step-by-step screen. Business verification and App Review are listed under Publishing requirements

  11. On the last screen, Overview, check what you have chosen so far and create the app.

2

Adding the email permission

When a user logs in with Facebook, WEEGLOO receives the email along with it and puts it on the member. In the same Space, one email can sign up only once. Facebook does not hand the email over unless you add the email permission, so do not skip this step.

  1. If the app screen is not open, on the app list screen (https://developers.facebook.com/apps (opens in a new tab)), click the app you will use for login.

  2. In the left menu, click Use cases.

  3. Click Customize on the Facebook Login item.

  4. On the left, click Permissions and features.

  5. Click + Add on the email row.

    The Permissions and features list. The email row has nothing in Status and a + Add button in Action, and the public_profile row shows Ready for testing

  6. Check that Status is Ready for testing on both the email row and the public_profile row.

    The same list. Status is Ready for testing on both the email row and the public_profile row

3

Registering the login address

  1. If the Customize use case screen is not open, on the app list screen (https://developers.facebook.com/apps (opens in a new tab)), click the app you will use for login. Then, under Use cases in the left menu, click Customize on the Facebook Login item.

  2. On the left, click Settings.

  3. Paste the address below into the Valid OAuth Redirect URIs box. Pick your Space and the identifier is filled in.

    Space
    https://auth.weegloo.com/v1/spaces/{spaceId}/login/oauth2/code/facebook

    If you are not sure which Space is yours and you have handed the integration to an AI agent, you can also ask the agent. Ask in the chat, "Tell me the redirect address to register with Facebook Login", and you receive the finished address.

    Redirect URI Validator at the top of the same screen is not where you register the address. Put an address into Redirect URI to check and click Check URI, and you can check that address.

  4. Click Save Changes.

    The Settings screen. Redirect URI Validator is at the top, and the Valid OAuth Redirect URIs box is in Client OAuth settings below

4

Copying the App ID and the App secret

The App ID and the App secret are on the app's basic settings screen.

A red Currently ineligible for submission banner may appear at the top of this screen. It is a notice that App icon, Privacy policy URL, and Category are empty. Those three items are needed when you submit for review, and they are not needed for connecting login right now.

  1. If the app screen is not open, on the app list screen (https://developers.facebook.com/apps (opens in a new tab)), click the app you will use for login.

  2. In the left menu, click App settings.

  3. Click Basic.

  4. Copy the value written in App ID.

  5. Click Show to the right of App secret.

  6. Copy the value that appears.

    The Basic screen under App settings. The App ID value is visible, and App secret is hidden behind dots with a Show button to its right

You can see both values again on this screen whenever you want. For App secret you click Show, so even if you leave the screen before writing it down, you do not have to create a new one. App secret is a secret value, though, so do not tell it to anyone, and do not write it down anywhere public.

Adding the people who will try it as Testers

The WEEGLOO connection does not have to wait for the review. Once you put the App ID and the App secret into WEEGLOO, login works right away.

The app you just created has not been through review yet, though, and until it has, only the account that created the app can log in. To let someone else log in and try it, add that person to the app as a Tester.

  1. In the left menu, expand App roles and click Roles.

  2. Click Add People at the top right.

    The App roles screen. There are All roles, Administrators, Developers, Testers, and Analytics Users tabs, with the Add People button at the top right

  3. Choose Tester.

  4. Enter the name or the Facebook ID of the person you want to add in the box below, and click Add.

    The Add people to your app window. Tester is selected among Administrator, Developer, Tester, and Analytics User, with a box for finding a person below

The Test users menu right below it does not work.

To open it to every user, you go through review

To let any user log in, not just the people you added as a Tester, you have to go through Facebook's review. When you are ready, expand Review in the left menu and open App Review. The email and public_profile you added earlier are listed under Not submitted. Check that the two permissions are right and click Next at the bottom right, and you move on to the submission procedure.

The App Review screen under Review. email and public_profile are listed under Not submitted

Several more steps follow after Next, and this page covers only as far as starting the submission. The rest of the procedure and the review criteria are in the Meta docs (opens in a new tab). Once you pass the review, any user can log in with this app from then on.

Putting the App ID and App secret into WEEGLOO

Now you have the App ID and the App secret in hand. Here is which box in the content studio each of the two values goes into.

Facebook screenContent studio
App IDApp ID
App secretApp secret

From here the path splits depending on how you have been working so far.

If you were configuring this directly in the content studio, follow these steps.

  1. Go back to turning on social login in Service Member Login.
  2. Turn on Facebook.
  3. Enter the App ID in the App ID box in Step 2.
  4. Enter the App secret in the App secret box.
  5. Click Save.

If you handed the integration to an AI agent and were told to go and get the App ID and the App secret, paste the two values you received into the chat as they are and carry on with what you were doing. The agent handles the rest of the configuration from there.

What to do next

  • Service Member Login: put the values you received into the content studio and finish the rest of the member login configuration.
  • Member Roles and Permissions: create the ServiceUserRole that decides what a signed-up member can see and use.
  • Auth API: covers technical specifications such as the request format you need when wiring login into your own site's code.