Google

Wasp supports Google Authentication out of the box. Google Auth is arguably the best external auth option, as most users on the web already have Google accounts.

Enabling it lets your users log in using their existing Google accounts, greatly simplifying the process and enhancing the user experience.

Let's walk through enabling Google authentication, explain some of the default settings, and show how to override them.

Setting up Google Auth

Enabling Google Authentication comes down to a series of steps:

1. Enabling Google authentication in the Wasp file.
2. Adding the User entity.
3. Creating a Google OAuth app.
4. Adding the necessary Routes and Pages
5. Using Auth UI components in our Pages.

Here's a skeleton of how our main.wasp should look like after we're done:

main.wasp

// Configuring the social authentication
app myApp {
  auth: { ... }
}

// Defining routes and pages
route LoginRoute { ... }
page LoginPage { ... }

1. Adding Google Auth to Your Wasp File

Let's start by properly configuring the Auth object:

main.wasp

app myApp {
  wasp: {
    version: "^0.17.0"
  },
  title: "My App",
  auth: {
    // 1. Specify the User entity (we'll define it next)
    userEntity: User,
    methods: {
      // 2. Enable Google Auth
      google: {}
    },
    onAuthFailedRedirectTo: "/login"
  },
}

userEntity is explained in the social auth overview.

2. Adding the User Entity

Let's now define the app.auth.userEntity entity in the schema.prisma file:

schema.prisma

// 3. Define the user entity
model User {
  id Int @id @default(autoincrement())
  // Add your own fields below
  // ...
}

3. Creating a Google OAuth App

To use Google as an authentication method, you'll first need to create a Google project and provide Wasp with your client key and secret. Here's how you do it:

1. Create a Google Cloud Platform account if you do not already have one: https://cloud.google.com/

2. Create and configure a new Google project here: https://console.cloud.google.com/projectcreate

   

   

3. Search for Google Auth in the top bar (1), click on Google Auth Platform (2). Then click on Get Started (3).

   

   

4. Fill out you app information. For the Audience field, we will go with External. When you're done, click Create.

   

   

5. You should now be in the OAuth Overview page. Click on Create OAuth Client (1).

   

6. Fill out the form. These are the values for a typical Wasp application:

   #	Field	Value
   1	Application type	Web application
   2	Name	(your wasp app name)
   3	Authorized redirect URIs	http://localhost:3001/auth/google/callback

   note

   Once you know on which URL(s) your API server will be deployed, also add those URL(s) to the Authorized redirect URIs.
   For example: https://your-server-url.com/auth/google/callback

   

   Then click on Create (4).

7. You will see a box saying OAuth client created. Click on OK.

   

8. Click on the name of your newly-created app.

   

9. On the right-hand side, you will see your Client ID (1) and Client secret (2). Copy them somewhere safe, as you will need them for your app.

   

   info

   These are the credentials your app will use to authenticate with Google. Do not share them anywhere publicly, as anyone with these credentials can impersonate your app and access user data.

10. Click on Data Access (1) in the left-hand menu, then click on Add or remove scopes (2). You should select userinfo.profile (3), and optionally userinfo.email (4), or any other scopes you want to use. Remember to click Update and Save when done.

    

    

11. Go to Audience (1) in the left-hand menu, and add any test users you want (2). This is useful for testing your app before going live. You can add any email addresses you want to test with.

    

12. Finally, you can go to Branding (1) in the left-hand menu, and customize your app's branding in the Google login page. This is optional, but recommended if you want to make your app look more professional.

    

4. Adding Environment Variables

Add these environment variables to the .env.server file at the root of your project (take their values from the previous step):

.env.server

GOOGLE_CLIENT_ID=your-google-client-id
GOOGLE_CLIENT_SECRET=your-google-client-secret

5. Adding the Necessary Routes and Pages

Let's define the necessary authentication Routes and Pages.

Add the following code to your main.wasp file:

main.wasp

// ...

route LoginRoute { path: "/login", to: LoginPage }
page LoginPage {
  component: import { Login } from "@src/pages/auth"
}

We'll define the React components for these pages in the src/pages/auth.tsx file below.

6. Create the Client Pages

info

We are using Tailwind CSS to style the pages. Read more about how to add it here.

Let's now create a auth.tsx file in the src/pages. It should have the following code:

JavaScript

src/pages/auth.jsx

import { LoginForm } from "wasp/client/auth";

export function Login() {
  return (
    <Layout>
      <LoginForm />
    </Layout>
  );
}

// A layout component to center the content
export function Layout({ children }) {
  return (
    <div className="h-full w-full bg-white">
      <div className="flex min-h-[75vh] min-w-full items-center justify-center">
        <div className="h-full w-full max-w-sm bg-white p-5">
          <div>{children}</div>
        </div>
      </div>
    </div>
  );
}

TypeScript

src/pages/auth.tsx

import type { ReactNode } from "react";
import { LoginForm } from "wasp/client/auth";

export function Login() {
  return (
    <Layout>
      <LoginForm />
    </Layout>
  );
}

// A layout component to center the content
export function Layout({ children }: { children: ReactNode }) {
  return (
    <div className="h-full w-full bg-white">
      <div className="flex min-h-[75vh] min-w-full items-center justify-center">
        <div className="h-full w-full max-w-sm bg-white p-5">
          <div>{children}</div>
        </div>
      </div>
    </div>
  );
}

Auth UI

Our pages use an automatically-generated Auth UI component. Read more about Auth UI components here.

Conclusion

Yay, we've successfully set up Google Auth! 🎉

Running wasp db migrate-dev and wasp start should now give you a working app with authentication. To see how to protect specific pages (i.e., hide them from non-authenticated users), read the docs on using auth.

Default Behaviour

Add google: {} to the auth.methods dictionary to use it with default settings:

main.wasp

app myApp {
  wasp: {
    version: "^0.17.0"
  },
  title: "My App",
  auth: {
    userEntity: User,
    methods: {
      google: {}
    },
    onAuthFailedRedirectTo: "/login"
  },
}

When a user signs in for the first time, Wasp creates a new user account and links it to the chosen auth provider account for future logins.

Overrides

By default, Wasp doesn't store any information it receives from the social login provider. It only stores the user's ID specific to the provider.

There are two mechanisms used for overriding the default behavior:

• userSignupFields
• configFn

Let's explore them in more detail.

Data Received From Google

We are using Google's API and its /userinfo endpoint to fetch the user's data.

The data received from Google is an object which can contain the following fields:

[
  "name",
  "given_name",
  "family_name",
  "email",
  "email_verified",
  "aud",
  "exp",
  "iat",
  "iss",
  "locale",
  "picture",
  "sub"
]

The fields you receive depend on the scopes you request. The default scope is set to profile only. If you want to get the user's email, you need to specify the email scope in the configFn function.

For an up to date info about the data received from Google, please refer to the Google API documentation.

Using the Data Received From Google

When a user logs in using a social login provider, the backend receives some data about the user. Wasp lets you access this data inside the userSignupFields getters.

For example, the User entity can include a displayName field which you can set based on the details received from the provider.

Wasp also lets you customize the configuration of the providers' settings using the configFn function.

Let's use this example to show both fields in action:

main.wasp

app myApp {
  wasp: {
    version: "^0.17.0"
  },
  title: "My App",
  auth: {
    userEntity: User,
    methods: {
      google: {
        configFn: import { getConfig } from "@src/auth/google",
        userSignupFields: import { userSignupFields } from "@src/auth/google"
      }
    },
    onAuthFailedRedirectTo: "/login"
  },
}

schema.prisma

model User {
  id          Int    @id @default(autoincrement())
  username    String @unique
  displayName String
}

// ...

JavaScript

src/auth/google.js

import { defineUserSignupFields } from "wasp/server/auth";

export const userSignupFields = defineUserSignupFields({
  username: () => "hardcoded-username",
  displayName: (data) => data.profile.name,
});

export function getConfig() {
  return {
    scopes: ["profile", "email"],
  };
}

TypeScript

src/auth/google.ts

import { defineUserSignupFields } from "wasp/server/auth";

export const userSignupFields = defineUserSignupFields({
  username: () => "hardcoded-username",
  displayName: (data: any) => data.profile.name,
});

export function getConfig() {
  return {
    scopes: ["profile", "email"],
  };
}

Wasp automatically generates the defineUserSignupFields function to help you correctly type your userSignupFields object.

Using Auth

To read more about how to set up the logout button and get access to the logged-in user in both client and server code, read the docs on using auth.

When you receive the user object on the client or the server, you'll be able to access the user's Google ID like this:

const googleIdentity = user.identities.google

// Google User ID for example "123456789012345678901"
googleIdentity.id

Read more about accessing the user data in the Accessing User Data section of the docs.

API Reference

Provider-specific behavior comes down to implementing two functions.

• configFn
• userSignupFields

The reference shows how to define both.

For behavior common to all providers, check the general API Reference.

main.wasp

app myApp {
  wasp: {
    version: "^0.17.0"
  },
  title: "My App",
  auth: {
    userEntity: User,
    methods: {
      google: {
        configFn: import { getConfig } from "@src/auth/google",
        userSignupFields: import { userSignupFields } from "@src/auth/google"
      }
    },
    onAuthFailedRedirectTo: "/login"
  },
}

The google dict has the following properties:

• configFn: ExtImport

  This function must return an object with the scopes for the OAuth provider.

  JavaScript

  src/auth/google.js

  export function getConfig() {
    return {
      scopes: ["profile", "email"],
    };
  }

  TypeScript

  src/auth/google.ts

  export function getConfig() {
    return {
      scopes: ["profile", "email"],
    };
  }

• userSignupFields: ExtImport

  userSignupFields defines all the extra fields that need to be set on the User during the sign-up process. For example, if you have address and phone fields on your User entity, you can set them by defining the userSignupFields like this:

  JavaScript

  src/auth.js

  import { defineUserSignupFields } from "wasp/server/auth";
  
  export const userSignupFields = defineUserSignupFields({
    address: (data) => {
      if (!data.address) {
        throw new Error("Address is required");
      }
      return data.address;
    },
    phone: (data) => data.phone,
  });

  TypeScript

  src/auth.ts

  import { defineUserSignupFields } from "wasp/server/auth";
  
  export const userSignupFields = defineUserSignupFields({
    address: (data) => {
      if (!data.address) {
        throw new Error("Address is required");
      }
      return data.address;
    },
    phone: (data) => data.phone,
  });

  Read more about the userSignupFields function here.