Vinculación de Cuentas de Google con Flip de apps basado en 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.

This figure shows the steps for a user to link their Google account to your authentication system. The first screenshot shows how a user can select your app if their Google account is linked to your app. The second screenshot shows the confirmation for linking their Google account with your app. The third screenshot shows a successfully linked user account in the Google app.
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.

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.

This figure shows an example consent screen with call-outs to the individual requirements and recommendations to be followed when you design a user consent screen.
Figure 2. Account linking consent screen design guidelines.

Implementa App Flip en tus apps nativas

Para implementar App Flip, debes modificar el código de autorización del usuario en tu app a fin de aceptar un vínculo directo de Google.

Si deseas admitir App Flip en tu app para Android, sigue las instrucciones de la Guía de implementación de Android.

Si quieres admitir App Flip en tu app para iOS, sigue las instrucciones de la guía de implementación de iOS.

Prueba de cambio de app

App Flip se puede simular con apps de muestra y de prueba antes de que estén disponibles las apps de producción verificadas y un servidor de OAuth 2.0 que funcione.

Durante la vuelta a la app, Google app primero abrirá tu app y, luego, solicitará una respuesta con código de autorización al servidor de OAuth 2.0. En el paso final, se mostrará la respuesta en Google app.

Requisitos previos

Para simular una app de Google y activar el intent que inicia tu app, descarga y, luego, instala la herramienta de prueba de Flip de App para iOS y Android.

Descarga y, luego, instala la app de ejemplo de Flip para iOS y Android a fin de simular tu app y seleccionar un tipo de respuesta de OAuth 2.0.

Secuencia de prueba

  1. Abre la Herramienta de prueba de Flip de la app.
  2. Presiona Try Flip! para iniciar la app de ejemplo de Flip de la app.
  3. Selecciona una respuesta de los botones de selección en la aplicación de muestra.
  4. Presiona Send para mostrar una respuesta de OAuth 2.0 simulada a la herramienta de prueba.
  5. Revisa los mensajes de registro de Test Tool para ver detalles de error o código de autenticación.

Pruebas de producción

Se puede probar App Flip en fase de producción después de completar el registro y la implementación del servidor de OAuth 2.0.

Para la prueba automatizada, se recomienda tener una sola Cuenta de Google y una dirección de correo electrónico específica de tareas.

El estado de vinculación de las cuentas se puede ver mediante Cuentas vinculadas cuando accedes como titular de la Cuenta de Google. Las cuentas se pueden desvincular entre pruebas repetidas desde aquí también.

De forma opcional, puedes implementar RISC para desvincular y notificar a Google de manera programática el cambio.