The login screen presents a login button that will kick off a third-party authentication flow to complete the sign-in. The user is first presented with the login screen, and only after they sign in, can they proceed to the home screen. We will build a simple app with a login screen and a home screen. In today’s example, our app will make a request to Google, obtain the identity token, and we will use it to sign the user in as well as obtain basic user information.

We will be utilizing this feature in this example to display the user profile upon the user signing in. Upon signing a user with the signInWithIdToken method, Supabase automatically populates the content of the ID token in the Supabase user metadata for easy access to the information. Supabase auth provides signInWithIdToken method where we can sign in a user using their ID token obtained from third-party auth providers such as Google. This identity token can then be verified and decoded by the application to obtain that personal information. Open ID Connect, or OIDC is a protocol built on top of OAuth 2.0 that allows third-party applications to request the users to provide some personal information, such as name or profile image, in the form of an identity token along with an access token. We will implement third-party login with Google utilizing the Open ID Connect functionality of Supabase Auth. Supabase - create your account here if you do not have one.Flutter - we used v3.10.5 for this article.This article assumes you are comfortable with writing a basic application in Flutter.

You can check out the code of the sample in this article here. We will also dive into the deep ends of Open ID Connect sign-in to better understand how third-party sign-ins are being performed. In this article, we will take a look at how we can implement authentication using Google sign-in to secure our application using the Supabase SDK for Flutter. Flutter is Google’s open-source framework to develop cross-platform applications.

Login google flutter