1. Home
  2. Knowledge Base
  3. BuddyBoss Platform
  4. BuddyBoss Social Login
  5. How to Set Up Apple Social Login for BuddyBoss

How to Set Up Apple Social Login for BuddyBoss

Introduction

Apple Social Login allows users to log in and register on your BuddyBoss Platform (Web and App) using their Apple ID.

This guide provides detailed, step-by-step instructions to enable and configure Apple Social Login, enhancing user convenience and streamlining the registration process.

Tutorial Video

Prerequisites and Key Considerations

App Publishing Requirements

  • If Social Login is enabled in the BuddyBoss App, both Google and Apple Social Logins are required for publishing on app stores. This is mandatory even if other social providers (e.g., Facebook, X, LinkedIn) are used, ensuring compatibility with device-associated accounts.
  • Google and Apple Social Logins are optional only if the BuddyBoss App exclusively uses your company’s account sign-in system.
  • Active Apple Developer Program Subscription: Required for creating and maintaining the Apple app.
  • SSL Certificate: Your website must use HTTPS, as Apple only allows secure URLs.

Note: Any changes to the Social Login settings require new builds for both iOS and Android apps. Ensure to regenerate and publish updated app versions after making any modifications.

Required Information for Apple Social Login

To enable Apple Social Login, you need the following details:

  • Private Key ID
  • Private Key
  • Team Identifier
  • Service Identifier

Creating an Apple App for Social Login

Follow these steps to create an Apple App and obtain the necessary keys for integrating Apple Social Login with your BuddyBoss Platform.

Access Apple Developer Account

  1. Navigate to the Apple Developer Account.
  2. Log in with your Apple Developer credentials.

Create the Associated App

Scenario A: Create a New App Identifier

  1. From Program Resources, go to Certificates, IDs & Profiles > Identifiers.
  1. Click the + icon next to Identifiers.
  1. Select App IDs and click Continue.
  1. Choose App and click Continue.
  1. Add a Description for your app.
  2. In the Bundle ID field:
    • Select Explicit.
    • Enter your domain name in a reverse-domain style (e.g., site.ddev.bbplatform.nslapp).
  1. Under Capabilities, check the Sign In with Apple option.
  2. Click Register to save the configuration.

Once registered, you will be redirected to Identifiers and see the one you created reflecting

Scenario B: Use an Existing Apple or iOS App

  1. Go to Program resources > Certificates, IDs & Profiles > Identifiers.
  1. Click the existing Identifier for your Apple app.
  1. In the Edit your App ID Configuration page:
    • Enable Sign in with Apple.
    • Click Save.

Note: Your Server-to-Server Notification Endpoint works natively with your app, so you don’t need to fill in the pop-up shown below.

  1. Go to WordPress Dashboard > BuddyBoss App > Configure > iOS Settings > App Configuration.
  2. Regenerate both Signing Certificates and Provisioning Profiles.

5.1. Regenerate Signing Certificates

  • Under Signing Certificates, disable Generate Certificate or “Automatically generate signing certificates“, and click Save Changes.
  • Remove the Release App Signing Certificate and Test App Signing Certificate, and click Save Changes.
  • Enable Generate Certificate or “Automatically generate signing certificates“, and click Save Changes to successfully regenerate Signing Certificates.
  • Proceed to regenerate and update your Provisioning Profiles.

5.2 Regenerate Provisioning Profiles

  • Under Provisioning Profiles, click Generate New Profiles.
  • Now, the Provisioning Profiles are regenerated based on the new Signing Certificates. Proceed to request a new iOS build.

Create the Key for Apple Social Login

  1. From the same page, navigate to the Keys tab.
  1. Click the + icon next to Keys.
  1. Enter a Key Name.
  1. Check Sign In with Apple and click Configure.
  • If you have multiple apps, select the App ID created earlier.
  • Click Save, then Continue, and finally Register.

Important:
Only download the key when you are ready.
Once downloaded, it cannot be re-downloaded. Be sure to store the key file in a secure location.

Create the Service Identifier

  1. From Download Your Key, click All Keys.
  1. Click Identifiers.
  1. In the Identifiers tab, click the + icon to go to the Services IDs.
  1. Select Services IDs and click Continue.
  1. Add a Description for your service.
  1. In the Identifier field, enter a reverse-domain style identifier (e.g., site.ddev.bbplatform.nslclient).
  2. Click Continue, then Register.

Configure Sign-In with Apple

  1. In the Services IDs section, select the newly created Service ID.
  1. Check Sign In with Apple and click Configure.
  • Select the Primary App ID if multiple apps exist.
  1. Fill the Domains and Subdomains field with your domain name (e.g., bbplatform.ddev.site).
  • Add the following Return URL: https://yourdomain.com/wp-login.php?bb_social_login=apple
  • To obtain this URL:
    • Go to WordPress Dashboard > BuddyBoss Plugin > Settings > General > Registration.
    • Click the pencil icon for Apple Social Login and copy the Callback URI / Redirect URL.
  1. Click Next, then Done.
  1. Click Continue, then Save.

Configure Apple Social Login in BuddyBoss Platform

  1. Go to WordPress Dashboard > BuddyBoss Plugin > Settings > General > Registration.
  2. Enable Social Login by checking the box.
  3. Click the pen icon next to Apple Social Login.

Fill in the Required Fields

  • Private Key ID:
    • Go to Apple Developer Account > Authentication Keys.
    • Click on the Key Name to find the Private Key ID.
  • Private Key:
    • Download the Private Key file.
      • Note: Once this file is downloaded, it will no longer be available. Ensure that you keep this file safe.
    • Open it in a text editor and copy all its contents.
    • Paste it into the Private Key field.
  • Team Identifier:
    • Find this under your Apple Developer Account name (10-character ID).
  • Service Identifier:
    • Navigate to Apple Developer Account > Identifiers > Service ID.
    • The Identifier will be in reverse-domain style (e.g., site.ddev.bbplatform.nslclient).
  1. Click Save Changes.
  2. Sign in on the Apple Account pop-up page.
  1. Click Verify Settings to complete the setup.
  • Once done, there will be a notice in your X Social Login pop-up: “Settings have been verified. Please wait while we redirect you.

7. Enable the Apple Social Login and click Save Settings.

  • Note: If you face the following errors, try to open your site in a private or Incognito window and authenticate again.
    • “Error: The username field is empty”
    • “Error: The password field is empty”
    • For site users:
      • When a user registers for the first time using their Apple credentials, the username is generated based on their Apple account information.
      • However, if the user registers again, the username is generated randomly instead of using their actual Apple account name.

This behavior is a limitation of the Apple registration process. Apple does not provide the user’s actual name during subsequent registrations for privacy reasons.

Troubleshooting and FAQs

Q: Why is the Apple Social Login checkbox greyed out?
A: Open your site in a private/incognito window and authenticate again. Click the pencil icon next to Apple Social Login and select Verify Settings.

Q: Why am I getting “Error: The username/password field is empty”?
A: Ensure all required fields are filled correctly in the Apple Social Login setup. Verify that the Private Key and Service Identifier are accurate.

Q: Why is the username generated randomly during Apple Social Login?
A: Apple’s Privacy Policy: During re-registration, Apple does not provide the actual username for privacy reasons. Instead, a random username is generated.

Was this article helpful?

Related Articles

To speak to our Agency consultant, fill in the form found at our Contact Page.

  • Get Started

    Enter your name and email address to get started with your project...

  • This field is for validation purposes and should be left unchanged.

Not recently active