Limited Login FAQ
In response to the upcoming changes to ATT enforcement, we made changes to the iOS SDK and the SDK no longer provides valid user access tokens in scenarios where the user opts out of ATT. The access token validation or Graph API requests may throw errors like OAuthException - “Invalid OAuth access token - Cannot parse access token”. Our recommendation is that users integrate Limited Login following the official documentation:
When users opt out of ATT, all Facebook Login traffic will be performed on the Limited Login domain. Limited Login does not support business permissions. Our recommendation is that developers integrate Limited Login following the official documentation. See limited login supported permissions in this document.
When users opt out of ATT, all Facebook Login traffic will be performed on the limited login domain via the in-app browser. Limited Login does not support fast app switch (that is, redirecting to fb app to login). See limitations section of the Limited Login for iOS document.
Please see the official documentation, Validating the Limited Login OIDC Token.
Please see key considerations for user_friends with Limited Login in the Permissions in Limited Login document.
We made changes both to the iOS SDK and our core login systems to support the privacy manifest requirements based on the upcoming App Transparency Tracking enforcement so that iOS users who have opted out of ATT are able to use FBLogin. As a result, we do not plan to release the privacy manifest as part of a minor update.
This will authenticate your user and populate a shared instance of an authentication token. The additional information from the authentication call will be used to populate the shared User Profile instance with basic fields.
A graph request will fail because there is no access token. To get an access token, either reuse the classic login method (defaults tracking to enabled), or call FBSDKLoginManager logInFromViewController:configuration:completion: with a configuration that specifies that tracking is enabled. Be aware that when you do this, users are tracked.
To access the Graph API, you need an access token. Either reuse the classic login method (defaults tracking to enabled), or call FBSDKLoginManager logInFromViewController:configuration:completion: with a configuration that specifies that tracking is enabled. This will allow you obtain an access token that can be used for Graph API calls. Be aware that when you do this, users are tracked. Be aware that Limited Login safeguards are not supported in this context.
When you use Limited Login to request user_friends from a user, we provide you with a list of app scoped IDs (ASIDs) associated with the friends of the authorizing user, if the friends have also granted your app the user_friends permission. Depending on how you have implemented Limited Login, some of the ASIDs on this list may represent other users that have connected to your app using Limited Login. To ensure that Limited Login safeguards are maintained for such users, do not make Graph API calls using their ASIDs. Instead, continue to rely on Limited Login for these users.
Yes. There are two added public properties:
loginTracking, which can be used to get or set the desired tracking preference to use for login attempts. It defaults to.enabled.nonce, which can be used to get or set an optional nonce to use for login attempts. A valid nonce must be a non-empty string without whitespace. Note: An invalid nonce will not be set. Instead, default unique nonces will be used for login attempts.
No change from the user perspective. Under the hood it will set the current AuthenticationToken, AccessToken, and Profile to nil.
Limited Login is not available for tvOS at this time.
No. We are not developing Limited Login for React Native SDK due to its deprecation in SDK v9.0. See the React Native documentation for more details.
There is no impact to existing logged in users from adopting Limited Login in your app. If you would like to take advantage of Limited Login safeguards for existing, logged-in users, you must log them out by so they can log back in with Limited Login.
No. The Limited Login flag is device-specific.
No. fb_login_id is still present in Limited Login mode. It is the user access token (separate entity) which is swapped for an OIDC token in Limited Login mode.
Limited Login mode only supports basic profile (name and picture) and email permissions. If your app requires business permissions, you cannot use Limited Login to request them. However, your users can grant business permissions In Classic Login in the following ways:
- Logging into your app via web.
- Logging into your app via iOS in Classic Login mode.
- Logging into your app via Android.
Yes, but this will require the use of an app access token to request the token_for_business field on the User node. Limited Login safeguards are not supported in this context. For apps that are associated with your business by means of Business Manager, you can use the app-scoped ID (ASID) included in the OIDC token returned after a successful login to get a unique string for a user. Using your app's app access token, request the token_for_business field on the User node and pass in the user's app-scoped ID. This call returns a string which is the same for this user across all the apps managed by the same Business Manager.
GET /ASID?fields=token_for_business
This returns the values.
{
"id": "1234567890"
"token_for_business": "weg23ro87gfewblwjef"
}Usage notes:
- The person being queried must have logged into this app.
- If the owning business changes, the value of
token_for_businesswill also change - If you request the
token_for_businessfield and the app is not associated with a Business Manager, the call returns an error. - The value returned by
token_for_businessis a token, not an ID - it cannot be used directly against the Graph API to access a person's information. You should still store the ID in your database.