As of February 2023, Meta has implemented a business verification requirement when publishing new and existing apps.
Updating the Facebook app API or creating a new app will break existing logins. See troubleshooting at the bottom of this post for a solution.
Configuration
Go to developers.facebook.com/apps and …
- Login with the credentials of the account you want to connect to Discourse and follow the wizard.
If you already have other apps instead ofGet Startedyou will see the entryMy Apps, then just click on
Add new appand follow the guide from step 1b
1a. Select Developer
1b. Provide a name for the app, for example `Discourse Login` and click on <kbd>Next</kbd>.
1c. Click on <kbd>Add your first product</kbd>
-
Click Set Up below Facebook Login.
-
From the menu on the left, exit Quickstart by clicking on Settings under
Facebook Login
-
Setup the
Valid OAuth redirect URIfield, enteringhttps://discourse.example.com/auth/facebook/callback– obviously, replacing the domain with your site’s actual domain name and matching the HTTPS protocol. Remember that the HTTPS protocol is now mandatory for all URI redirects. Click Save Changes.
Once completed, a successful setup should look like this in Products/Facebook Login/Settings:
-
Navigate to Settings/Basic, enter your Discourse URL (
https://discourse.example.com) in theApp Domainsfield and also enter the URL for your Discourse site privacy policy and Terms of Service in the appropriate fields and also upload the icon of your site. (Mind that for your privacy and tos link to be verified, you should have a valid SSL certificate integrates, which is not self-signed. If the certificate is missing, or self-signed, you won’t be able to save your changes).
If you have a company that does business in the European Union, you may want to fill in theData Protection Officer Contact Informationform before clicking on Save Changes.⚠️ Facebook has changed this step to ask for extra information. We are currently working to determine what you need to provide; see recent replies. (November 2020)
There is now a field for
User Data Deletioninformation for GDPR compliance. Select “Data Deletion Instructions URL” from the dropdown and add a link to a page (such ashttps://discourse.example.com/tos#deletion) which contains a sentence like “Accounts on this site can be anonymized or deleted at the user’s request. Contact our@supportgroup for details.” -
At the bottom of the page click on
Add Platformand selectWebsite
-
Enter your Discourse URL here, for example
https://discourse.example.comand click Save Changes
-
Click on the Status button to change your app from
in developmenttopublic.
The category you select does not matter.
After a few seconds the button will become:
-
In Discourse site settings, enter your Facebook app’s App ID and App Secret in the
facebook app idandfacebook app secretfields. You’ll also want to check offEnable Facebook authentication, requires facebook_app_id and facebook_app_secret
That’s it! Facebook login should work now. Be sure to test it from a “normal” Facebook account, not your developer account.
Troubleshooting
Hosted Customers
If you are a Discourse hosting customer, contact us via the email address on your site dashboard and we will be happy to assist.
If you’re hosted by another provider you will need to contact them for any server-related tasks or issues.
Self-hosters
If the Facebook app API is updated, or the app ID/secret are changed, you’ll need to remove existing associations from your site before users can log in again. To remove this data, run the following:
cd /var/discourse
./launcher enter app
rails c
UserAssociatedAccount.where(provider_name: "facebook").delete_all
Last edited by @martin 2024-06-11T07:00:30Z
Check document
Perform check on document:
. Es scheint, dass meine Communities Facebook doch nicht besonders mögen…
