Vinculação da Conta do Google com o App Flip baseado em 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.

Implementar a função "App Flip" nos seus apps nativos

Para implementar o recurso, você precisa modificar o código de autorização do usuário no app para aceitar um link direto do Google.

Para oferecer suporte ao recurso "App Flip" no seu app Android, siga as instruções do Guia de implementação do Android.

Para oferecer suporte ao recurso "App Flip" no seu app para iOS, siga as instruções no guia de implementação para iOS.

Testar a vinculação no app

A alternância de apps pode ser simulada usando apps de exemplo e de teste antes que os apps de produção verificados e um servidor OAuth 2.0 em funcionamento estejam disponíveis.

Durante o App Flip, um app do Google abre seu app, que solicita uma resposta de código de autorização do servidor OAuth 2.0. Na etapa final, a resposta é retornada ao Google app.

Pré-requisitos

Para simular um app do Google e acionar a intent que inicia seu app, faça o download e instale a ferramenta de teste de virada de app para Android e iOS.

Faça o download e instale o App Flip Sample para Android e iOS. Para simular seu app, selecione um tipo de resposta do OAuth 2.0.

Sequência de teste

  1. Abra a ferramenta de teste de virada de tela do app.
  2. Pressione Try Flip! para iniciar seu app de exemplo do App Flip.
  3. Selecione uma resposta nos botões de opção do app de exemplo.
  4. Pressione Send para retornar uma resposta simulada do OAuth 2.0 à ferramenta de teste.
  5. Verifique as mensagens de registro da ferramenta de teste para conferir um auth_code ou detalhes do erro.

Teste de produção

O App Flip pode ser testado na produção depois de concluir o registro e a implementação do servidor do OAuth 2.0.

Uma única Conta do Google e um endereço de e-mail específico para a tarefa são recomendados para testes automatizados.

O estado de vinculação de contas pode ser visualizado usando Contas vinculadas ao fazer login como titular da Conta do Google. As contas também podem ser desvinculadas entre testes repetidos.

Como alternativa, é possível implementar o RISC para desvincular de forma programática e notificar o Google sobre a mudança.