If there are modifications done directly via system/console, avoid editing your cloud service configurations from touch UI to avoid overwriting. If additional scope is desired, it is necessary to edit the OSGI configuration directly. The default scope is the standard permissions for Facebook login. The result is an Adobe Granite OAuth Application and Provider instance which does not require further modification unless adding additional scope (permissions). For Sites where anonymous users are disabled, chose to add users to corresponding community-members group meant for that closed community site. Auto membership only applies to new users being created post this field update. But existing users’s memberships won’t be affected. Groups may be added or removed at any time.
Add to User Groups select Add User Group to choose one or more member groups for the community site to which users will be added.Scope Email: email id of user should be fetched from Facebook.Default is checked (strongly recommended). Create Users If checked, logging in with a Facebook account will create an AEM user entry and add them as a member to the selected user group(s).
App Secret ( Required) Enter the App Secret for the Facebook App. This identifies the Adobe Granite OAuth Application and Provider instance created from the dialog. App ID/API Key ( Required) Enter the App ID for the Facebook App. It is recommended to use the same name entered as the Display Name for the Facebook app. Title ( Required) Enter a display title that identifies the Facebook App. See the Configuration Browser documentation for more information.Ĭreate/Edit Facebook cloud service configuration. Enable Cloud Configurations if not enabled yet. Go to Tools > General > Configuration Browser. On the AEM author instance, sign in with administrator privileges.įrom global navigation, select Tools > Cloud Services > Facebook Social login configuration.Ĭontext path should be the same as the cloud configuration path that you have selected while creating/editing a community site.Ĭheck if your context path is enabled to create cloud services below it. The Adobe Granite OAuth Application and Provider instance, instantiated by creating a cloud service configuration, identifies the Facebook application and the member group(s) to which the new users are added. This information is required for configuring the Facebook cloud service. Once the application has been created, locate the App ID and App Secret settings. Social login and the we-retail Facebook sample were developed when the Facebook Graph API was version 1.0.Īs of AEM 6.4 GA and AEM 6.3 SP1 social login was updated to work with the newer Facebook Graph API 2.5 version. The default fields are sufficient for most use cases but can be modified. These fields are specified in AEM Communities Facebook OAuth Provider and AEM Communities Twitter OAuth Provider. The Facebook and Twitter Adobe Granite OAuth Application and Provider instances, by default, include the basic app permissions within their scope.įields (params) specifies the actual data requested using URL parameters. Scope (permissions) specifies the data the app is allowed to request. Create and publish a Twitter Connect cloud service.Įnable social login for a community site. Create and publish a Facebook Connect cloud service. Without OAuth enabled, attempts to log in fail. While the we-retail sample provides sample Facebook and Twitter apps and cloud services, they are not available on a production website.Įnable OAuth authentication on all AEM publish instances. To include social login, it is required to create custom Facebook and Twitter applications. Therefore, including permitted Facebook or Twitter data in their AEM member profile. Social login is the capability to present a site visitor the option to sign in with their Facebook or Twitter account.
0 kommentar(er)
