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:

• Limited Login for iOS
• Limited Login for Unity

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.

Ini akan mengautentikasi pengguna Anda dan mengisi instance bersama dari token autentikasi. Informasi tambahan dari panggilan autentikasi akan digunakan untuk mengisi instance Profil Pengguna bersama dengan kolom dasar.

Permintaan grafik akan gagal karena tidak ada token akses. Untuk mendapatkan token akses, gunakan kembali metode login klasik (pelacakan default diaktifkan), atau panggil FBSDKLoginManagerlogInFromViewController:configuration:completion: dengan konfigurasi yang menentukan bahwa pelacakan diaktifkan. Sadarilah bahwa ketika Anda melakukan ini, pengguna dilacak.

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.

Ya. Ada dua properti publik tambahan:

• loginTracking, yang dapat digunakan untuk mendapatkan atau mengatur preferensi pelacakan yang dikehendaki untuk digunakan dalam upaya login. Default-nya .enabled.

• nonce, yang dapat digunakan untuk mendapatkan atau mengatur nonce opsional untuk digunakan dalam upaya login. Nonce yang valid harus berupa string yang tidak kosong tanpa spasi. Catatan: Nonce yang tidak valid tidak akan diatur. Sebaliknya, nonce unik default akan digunakan untuk upaya login.

Tidak ada perubahan dari perspektif pengguna. Di bawah sistem, ini akan mengatur AuthenticationToken, AccessToken, dan Profile saat ini ke nil.

Login Terbatas tidak tersedia untuk tvOS saat ini.

Tidak. Kami tidak mengembangkan Login Terbatas untuk React Native SDK karena sudah tidak digunakan lagi di SDK v9.0. Lihat dokumentasi React Native untuk detail selengkapnya.

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.

Tidak. Bendera Login Terbatas adalah khusus perangkat.

Anda dapat merekonsiliasi pengguna melalui email dan/atau ASID.

Tidak. fb_login_id masih ada dalam mode Login Terbatas. Token akses pengguna (entitas terpisah) adalah yang ditukar dengan token OIDC dalam mode Login Terbatas.

Mode Login Terbatas hanya mendukung profil dasar (nama dan gambar) dan izin email. Jika aplikasi Anda memerlukan izin bisnis, Anda tidak dapat menggunakan Login Terbatas untuk memintanya. Namun, pengguna Anda dapat memberikan izin bisnis dalam Login Klasik dengan cara berikut:

• Login ke aplikasi Anda melalui web.
• Login ke aplikasi Anda melalui iOS dalam mode Login Klasik.
• Login ke aplikasi Anda melalui 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_business will also change
• If you request the token_for_business field and the app is not associated with a Business Manager, the call returns an error.
• The value returned by token_for_business is 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.