We’re giving away 1,500 more DJI Tello drones. Enter to win ›
Get the code
View the demo
Review the architecture
by Devipriya Selvarajan, Shikha Maheshwari | Published November 28, 2018
Mobile developmentObject StorageSecurity
Note: This pattern is part of a composite pattern. These are code patterns that can be stand-alone applications or might be a continuation of another code pattern. This composite pattern consists of:
In this code pattern, learn how you can leverage IBM Mobile Foundation service to implement user authentication mechanisms using social logins or enterprise logins by using an LDAP server.
User authentication is a fundamental requirement in almost all enterprise mobile apps. For internal mobile apps, such as those related to payroll or business travel booking, organizations want to leverage single-sign-on by authenticating users against its on-premise LDAP server. And, for apps targeted to end users where enterprise data is not exposed, such as an app for product users that allows them to raise service requests, organizations want to allow users to authenticate using their social login such as Facebook login or Google login. In this developer code pattern, we show you how to authenticate users using both social login and enterprise login mechanisms.
When you have completed this code pattern, you will understand:
This architecture diagram illustrates the social login flow (here described with Google but also relevant to Facebook or other social providers). The diagram shows that the trigger to call social providers is initiated by the client.
Please see detailed instructions in the README.
Get the Code »
Back to top