On this page
Sign in with Facebook
Note: In proxy model architectures, where a server-side app using the embedded SDK is used as a proxy between client apps and Okta servers, a request context for the client apps is required. The expectation is that security enforcement is based on the client request context's IP address and user agent.
However, since these values are currently derived from the server app rather than the client, this enforcement isn't available. As a result, network zones or behaviors that drive their conditions based on these request context values (geolocation, IP Address, or user agent) won't work until a solution to the issue is found.
This guide covers a sequence of steps that you can follow to build an app that allows users to sign in with the Facebook social Identity Provider.
Learning outcomes
- Configure your Okta org to use Facebook as an Identity Provider.
- Challenge a user's identity using Facebook.
What you need
- An app that uses the embedded Identity Engine SDK
- Okta org already set up for a social IdP use case
- Identity Engine SDK set up for your own app
Sample code
Configuration updates
Before you build the Facebook IdP sign-in flow, ensure that you've completed the following steps: