Golden Demo Master

Facebook APP setup

Version:

1.0

Keywords:

Facebook Ad campaigns
Facebook hybris marketing integration
Facebook APP setup
OAuth2 setup for FB

Document owner

GDM Facebook app setup

Contents
1 Objective...........................................................................................................3
2 Creation of Facebook App...................................................................................3
2.1 : Create a developer account............................................................................................................... 3
2.2 : Create a new Facebook App............................................................................................................... 3
2.2.1 : APP ID............................................................................................................................................. 3
2.2.2 : Basic settings................................................................................................................................ 4
2.2.3 : Add product................................................................................................................................... 5
2.2.4 : Review the App............................................................................................................................. 6

3: Configure an OAuth client.........................................................................6

3.1 : Launch configuration................................................................................6
3.2 : Add the scope...................................................................................................7
4: Configure proxy settings............................................................................8
5: Configure Secure Socket layer settings(add certificate)................10

Version 0.2.2.1

GDM Facebook app setup

1 Objective
This document will guide you through a series of steps that needs to be
performed for the setup of the facebook application and the OAuth
configuration which are required for the authentication between facebook and a
hybris marketing facebook ad campaign.
When a campaign is to be created as a facebook ad campaign which could be
used for creating a custom audience in facebook, the authentication needs to
be done between facebook and hybris marketing.
The authentication is done by the facebook app .

On successful implementation, after clicking on the authenticate button in the

campaign popup, it navigates to the facebook login page and after the
validation it redirects back to the campaign page. The procedure for this
integration is listed in the below steps.

2 Creation of Facebook App

2.1

: Create a developer account

You will need Facebook developer account to get started. If you don't have one
upgrade your personal Facebook account to a Facebook Developer account .
Skip this step, if you already have a developer account.
https://developers.facebook.com

Version 0.2.2.1

GDM Facebook app setup

2.2 : Create a new Facebook App

Choose Apps in the header navigation and select Add a New App .

2.2.1 : APP ID
The App ID and Secret are generated fields.

2.2.2 : Basic settings

Click on the basic settings and enter the required values . The fields Privacy
policy URL and the App Icon are mandatory fields if the app is to be review by
facebook.
Click on the Add platform button and create a platform of type website. Enter
the re-direction URL in the redirection URL field which is derived in step 3.1
below.

Version 0.2.2.1

GDM Facebook app setup

2.2.3 : Add product

Click on Add product and select Facebook login .

In the Client OAuth settings section enable the Yes option for Client OAuth login, web OAuth Login .
In the Valid OAuth redirect URLs field enter the re-direction url value which is derived in the OAuth
configuration in step 3.1 below and save the changes.

Version 0.2.2.1

GDM Facebook app setup

2.2.4 : Review the App

Click on the App review section and make the App public by toggling and
enabling the Yes option in the make app public section. The app is now public
and available for use.

Version 0.2.2.1

GDM Facebook app setup

3:

Configure an OAuth client

3.1 : Launch configuration

In the Hybris marketing system launch the transaction OA2C_CONFIG which
opens the OAuth 2.0 Client Configuration in a web browser.
From the OAuth 2.0 Clients window, choose Create, select FACEBOOK from the
client profile drop-down menu and enter the client identification (App ID)
number you received during registration of the application with Facebook.
Enter the following scenario-specific Target Endpoint:
/sap/bc/ui5_ui5/sap/CUAN_NAV_TO/index.html#CUAN_TI_F_INI_MKT_AUTOMATI
ON_ENDPOINT
The target endpoint entered on your ABAP application server is used to redirect the
browser of the end user after completing the authorization process.
Under General Settings, enter the Client Secret (App Secret) information you received
during registration of the application with Facebook and press Enter to confirm the
entry.

Version 0.2.2.1

GDM Facebook app setup

3.2 : Add the scope

From the Scopes tab page, verify that FACEBOOK is displayed in the profile table, and
Ads Management and Public Profile are listed in the Scopes table.
Save the OAuth 2.0 Client configuration.

Version 0.2.2.1

GDM Facebook app setup

4:

Configure proxy settings

Launch transaction SICF in the hybris marketing system and click on execute

Version 0.2.2.1

GDM Facebook app setup

In the menu options click on client and Proxy settings and maintain the proxy as 8080 as per the
below screen.

Version 0.2.2.1

10

GDM Facebook app setup

5: Configure Secure Socket layer settings(add

certificate)
5.1: Download certificate
Go to www.facebook.com and click on the lock symbol next to the URL to get the site
information

Locate the certificate as indicated in note 2250699 and export it to a file

DigiCertHighAssura
nceEVRootCA.crt

Version 0.2.2.1

11

GDM Facebook app setup

5.2 : Import certificate

Start transaction STRUST in SAP Easy Access menu and switch to change mode.
Choose PSE SSL Client Anonymous.
From the Certificate area, choose Import Certificate and import the saved
Facebook certificate
file.
Choose Add to Certificate List and save the PSE file.
The AS ABAP will now trust SSL servers whose identity is confirmed by this
certificate.

5.3 Accept Terms and condition In following URLS,

https://www.facebook.com/customaudiences/app/tos?
https://www.facebook.com/ads/manage/customaudiences/tos.php
2159754 for App version v2.6

Version 0.2.2.1

12

GDM Facebook app setup

6. Troubleshooting:
6.1 : Re-direction error

While authenticating the FB ad campaign if the above error occurs then the redirection URl needs to be checked.

6.2 : Miscellaneous/generic error

While authenticating the FB ad campaign if the above error occurs then this can
be traced by running the transaction /IWFND/GW_CLIENT in the SAPGUI and
executing it with the HTTP method as GET and the Request URI parameter as
www.facebook.com.
If there is an error then the details can be traced in the error log.

Version 0.2.2.1

13

GDM Facebook app setup

Version 0.2.2.1

14

Copyright
2016 SAP AG or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express
permission of SAP AG. The information contained herein may be changed without prior notice. Some software products
marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Adobe, the
Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in
the United States and other countries. Apple, App Store, FaceTime, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, MultiTouch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. Bluetooth is a
registered trademark of Bluetooth SIG Inc. Citrix, ICA, Program Neighborhood, MetaFrame now XenApp, WinFrame,
VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc. Computop is a registered
trademark of Computop Wirtschaftsinformatik GmbH. Edgar Online is a registered trademark of EDGAR Online Inc., an
R.R. Donnelley & Sons Company. Facebook, the Facebook and F logo, FB, Face, Poke, Wall, and 32665 are trademarks
of Facebook. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads,
Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail,
YouTube, Dalvik, and Android are trademarks or registered trademarks of Google Inc. HP is a registered trademark of
the Hewlett-Packard Development Company L.P. HTML, XML, XHTML, and W3C are trademarks, registered trademarks,
or claimed as generic terms by the Massachusetts Institute of Technology (MIT), European Research Consortium for
Informatics and Mathematics (ERCIM), or Keio University. IBM, DB2, DB2 Universal Database, System i, System i5,
System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power
Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter,
System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner,
WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Microsoft,
Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation.
INTERMEC is a registered trademark of Intermec Technologies Corporation. IOS is a registered trademark of Cisco
Systems Inc.
The Klout name and logos are trademarks of Klout Inc. Linux is the registered trademark of Linus Torvalds in the United
States and other countries. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Mozilla and Firefox
and their logos are registered trademarks of the Mozilla Foundation. Novell and SUSE Linux Enterprise Server are
registered trademarks of Novell Inc.
OpenText is a registered trademark of OpenText Corporation. Oracle and Java are registered trademarks of Oracle and
its affiliates.
QR Code is a registered trademark of Denso Wave Incorporated. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry
Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry
AppWorld are trademarks or registered trademarks of Research in Motion Limited. SAVO is a registered trademark of
The Savo Group Ltd. The Skype name is a trademark of Skype or related entities. Twitter and Tweet are trademarks or
registered trademarks of Twitter. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Wi-Fi is
a registered trademark of Wi-Fi Alliance. SAP, R/3, ABAP, BAPI, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP
BusinessObjects Explorer, StreamWork, SAP HANA, the Business Objects logo, BusinessObjects, Crystal Reports,
Crystal Decisions, Web Intelligence, Xcelsius, Sybase, Adaptive Server, Adaptive Server Enterprise, iAnywhere, Sybase
365, SQL Anywhere, Crossgate, B2B 360 and B2B 360 Services, m@gic EDDY, Ariba, t he Ariba logo, Quadrem, bprocess, Ariba Discovery, SuccessFactors, Execution is the Difference, BizX Mobile Touchbase, It's time to love work
again, SuccessFactors Jam and BadAss SaaS, and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG in Germany or an SAP affiliate company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this
document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group
products and services are those that are set forth in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an additional warranty.

Version 0.2.2.1

15