Google 帐号关联（基于 OAuth 的应用快速关联）

OAuth-based App Flip Linking (App Flip) allows your users to easily and quickly link their accounts in your authentication system to their Google accounts. If your app is installed on your user’s phone when they initiate the account linking process, they are seamlessly flipped to your app to obtain user authorization.

This approach provides a faster and easier linking process since the user does not have to re-enter their username and password to authenticate; instead, App Flip leverages the credentials from the user's account on your app. Once a user has linked their Google account with your app, they can take advantage of any integrations that you have developed.

You can set up App Flip for both iOS and Android apps.

Figure 1. Account linking on a user's phone with App Flip.

Requirements

To implement App Flip, you must fulfill the following requirements:

• You must have an Android or iOS app.
• You must own, manage and maintain an OAuth 2.0 server which supports the OAuth 2.0 authorization code flow.

Note: Confirm that your OAuth2 implementation or provider supports the authorization code flow along with App Flip redirect URLs and client_ids as described in our guides.

Design guidelines

This section describes the design requirements and recommendations for the App Flip account linking consent screen. After Google calls your app, your app displays the consent screen to the user.

Requirements

1. You must communicate that the user’s account is being linked to Google, not to a specific Google product, such as Google Home or Google Assistant.

Recommendations

We recommend that you do the following:

1. Display Google's Privacy Policy. Include a link to Google’s Privacy Policy on the consent screen.

2. Data to be shared. Use clear and concise language to tell the user what data of theirs Google requires and why.

3. Clear call-to-action. State a clear call-to-action on your consent screen, such as “Agree and link.” This is because users need to understand what data they're required to share with Google to link their accounts.

4. Ability to cancel. Provide a way for users to go back or cancel, if they choose not to link.

5. Ability to unlink. Offer a mechanism for users to unlink, such as a URL to their account settings on your platform. Alternatively, you can include a link to Google Account where users can manage their linked account.

6. Ability to change user account. Suggest a method for users to switch their account(s). This is especially beneficial if users tend to have multiple accounts.

   • If a user must close the consent screen to switch accounts, send a recoverable error to Google so the user can sign in to the desired account with OAuth linking and the implicit flow.

7. Include your logo. Display your company logo on the consent screen. Use your style guidelines to place your logo. If you wish to also display Google's logo, see Logos and trademarks.

Figure 2. Account linking consent screen design guidelines.

在原生应用中实现应用快速关联

如需实现应用快速关联，您需要修改应用中的用户授权代码，以接受来自 Google 的深层链接。

如需在 Android 应用上支持应用快速关联，请按照 Android 实现指南中的说明操作。

如需在 iOS 应用中支持应用快速关联功能，请按照 iOS 实现指南中的说明操作。

测试应用快速关联

在获得正式生产应用之前，可以使用示例应用和模拟应用来模拟应用快速关联。

在应用快速关联期间，Google 应用会先打开您的应用，然后由 OAuth 2.0 服务器请求授权代码响应，然后在最后一步中将该响应返回给 Google 应用。

前提条件

如需模拟 Google 应用并触发用于启动应用的 intent，请下载并安装适用于 Android 和 iOS 的应用快速关联测试工具。

下载并安装适用于 Android 和 iOS 的应用快速关联示例。要模拟您的应用，请选择 OAuth 2.0 响应类型。

测试序列

1. 打开应用快速关联测试工具。
2. 按 Try Flip! 可启动应用快速关联示例应用。
3. 从示例应用的单选按钮中选择响应。
4. 按 Send 将模拟 OAuth 2.0 响应返回给测试工具。
5. 查看测试工具日志消息，了解 auth_code 或错误详情。

生产测试

完成注册和 OAuth 2.0 服务器实现后，应用快速测试可能会在生产中进行测试。

建议使用单个 Google 帐号和特定于任务的电子邮件地址进行自动测试。

以 Google 帐号持有者身份登录时，可以使用关联的帐号查看帐号关联状态。也可以在此处取消重复测试的帐号之间的关联。

（可选）您可以选择实现 RISC，以便以编程方式解除这项变更并通知 Google。