This is a part of an online Codename One course published around 2017 see it all for free at https://debugagent.com/series/cn1

1. Creating an Uber Clone - Part XXXIII
We already prepared a lot of the groundwork for social login on the server but didn't finish all the pieces so before I step into the client side changes needed for social
login lets discuss some of the required server side work.

2. public boolean existsByFacebook(String fb) {
List<User> us = users.findByFacebookId(fb);
return !us.isEmpty();
}
public boolean existsByGoogle(String google) {
List<User> us = users.findByGoogleId(google);
return !us.isEmpty();
}
UserService (Server)
I had to include support for the exists functionality that works based on a social token

3. @RequestMapping(method=RequestMethod.GET,value = "/exists")
public @ResponseBody boolean exists(String v) {
return users.existsByPhone(v);
}
@RequestMapping(method=RequestMethod.GET,value = "/existsFacebook")
public @ResponseBody boolean existsFacebook(String v) {
return users.existsByFacebook(v);
}
@RequestMapping(method=RequestMethod.GET,value = "/existsGoogle")
public @ResponseBody boolean existsGoogle(String v) {
return users.existsByGoogle(v);
}
UserWebservice
I also had to include a similar call in the UserWebservice class. I also have a smaller subtle change to the regular exists method. The argument name was phone and is
now v which means I can invoke all 3 webservices with very similar code on the client side.
That's it, pretty much everything else was already done.

4. Social Login
✦Seamless: Low Friction Sign-in
✦Native support or social app will be used when
available
✦When unavailable we’ll see a web based login
✦If we are on the simulator we will fallback to an OAuth
based login
✦Driver & User Apps - we’ll need to do each step twice!
© Codename One 2017 all rights reserved
Social login lets us authenticate a user without getting into the username/password complexity. This is usually almost seamless on devices where the preinstalled social
app is invoked explicitly and the user just needs to "approve the permissions”.
This is defined as a "low friction" approach to authenticate the user and is often superior to phone number activation. In Codename One this is pretty trivial to accomplish
especially for Google & Facebook login both of which are builtin to Codename One and into Android/iOS respectively.
Connection to social networks in Codename One has several common concepts. If the device has native support or the social app installed this native integration will
perform a login
If it doesn't but we are on the device the native SDK will show a web based login
If we are on the simulator we will fallback to an OAuth based login. This leads to a situation where login might work on one device but fail on the simulator or fail on a
different device type. It also makes the configuration process a bit more tedious. To be fair the native configuration is MUCH harder and involves more code.
Since the driver app is physically a separate app we’ll need to redo some of the steps and effectively go through everything twice

5. Facebook
© Codename One 2017 all rights reserved
https://developers.facebook.com/apps/
A core concept of the login process in Facebook is the "app" which is a Facebook internal term unrelated to your actual app. Facebooks view of an app is anything that
uses the Facebook graph API and authentication. In this case we need to create a new app and should name it like we do our actual app so the user will be able to
identify it.
The steps are pretty easy we navigate to https://developers.facebook.com/apps/ and press the Add a new app button.

6. Facebook
© Codename One 2017 all rights reserved
Next we need to select the product we are trying to use and we need to select Facebook login. Once there we are presented with a wizard containing multiple steps to
set up your app.

7. Facebook
© Codename One 2017 all rights reserved
You need to run through the wizard twice. Once for iOS and once for Android.

8. Facebook iOS Wizard
© Codename One 2017 all rights reserved
The content of the wizard changes but the gist is the same, we don't really need much information and can skip almost everything...
The first step is download and Install the Facebook SDK for iOS. This is obviously unnecessary for us so we can just press next

9. Facebook iOS Wizard
© Codename One 2017 all rights reserved
The second step is add Login Kit to your Xcode Project. Again there is no need to do anything and we can press next

10. Facebook iOS Wizard
© Codename One 2017 all rights reserved
The third step is Add your Bundle Identifier. It’s more interesting. We need to enter the project package name here and press Save then we are effectively done with iOS
as everything else is more of the same…

11. keytool -exportcert -alias YOUR_RELEASE_KEY_ALIAS
-keystore YOUR_RELEASE_KEY_PATH
| openssl sha1 -binary | openssl base64
Facebook Android Wizard
The Android wizard has one task that is a bit challenging but other than that it should be trivial.
Before we begin we need to generate key hashes for facebook which need to be done on your development machine. To do that you will need a command line with the
JDK's bin directory in your path. You will also need the path to the Android keystore you use for signing. You can find this file in the Android signing section in Codename
One Settings. If there is no certificate file there make sure to generate it.
Once all of this is in place you can use this command for Linux/Mac. This will provide the SHA1 key you will need in the Android wizard.

12. keytool -exportcert -alias androiddebugkey -keystore
"C:UsersUSERNAME.androiddebug.keystore" |
"PATH_TO_OPENSSL_LIBRARYbinopenssl" sha1 -binary |
"PATH_TO_OPENSSL_LIBRARYbinopenssl" base64
Facebook Android Wizard
Similarly on windows the command follows a similar structure but uses Windows command line conventions. Now that this is out of the way lets go over the Android
wizard steps

13. Facebook Android Wizard
© Codename One 2017 all rights reserved
The first step is download the Facebook SDK for Android. This is obviously unnecessary for us so we can just press Next

14. Facebook Android Wizard
© Codename One 2017 all rights reserved
The next step is import the Facebook SDK. Again there is no need to do anything and we can press Next

15. Facebook Android Wizard
© Codename One 2017 all rights reserved
The next step is tell Us about Your Android Project - We need to specify the package name for the application which in our case is com.codename1.apps.uberclone we
also need to specify the main class which is UberCN1Stub. The main class is effectively the main class name with the word “Stub" with an uppercase S appended at the
end. We can then press next.
After I pressed next I got this warning because the app isn’t in the store yet. Facebook thinks I might have typed the package incorrectly and provides this warning which
we can ignore

16. Facebook Android Wizard
© Codename One 2017 all rights reserved
And finally we are at the Add Your Development and Release Key Hashes. Here we need to add the hash we got before and press Next. The rest of the wizard isn’t
important…

17. Facebook Dashboard
© Codename One 2017 all rights reserved
Before we proceed we need to enter the facebook dashboard and copy two values. The app id and app secret which we will need when we setup the code