Wasp•4mo ago

custom onaftersignup

How can I add a custom hook to run after creating a user using OAuth (Google)? I want to copy the email address from Google to the username field.

6 Replies

kapa.ai•4mo ago

Hi @cmilazzo. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- Wasp does not currently support custom "onAfterSignup" hooks for OAuth (Google) out of the box. However, you can achieve your goal—copying the email address from Google to the username field—by customizing the user creation logic using the userSignupFields override. Here's how you can do it: 1. Override userSignupFields for Google
In your src/auth/google.ts (or .js), define userSignupFields so that the username is set to the user's email from Google:

   import { defineUserSignupFields } from 'wasp/server/auth'

   export const userSignupFields = defineUserSignupFields({
     username: (data: any) => data.profile.email, // Set username to email
     displayName: (data: any) => data.profile.name,
   })

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

   import { defineUserSignupFields } from 'wasp/server/auth'

   export const userSignupFields = defineUserSignupFields({
     username: (data: any) => data.profile.email, // Set username to email
     displayName: (data: any) => data.profile.name,
   })

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

Then, in your main.wasp, import these fields for the Google auth method:

   auth: {
     userEntity: User,
     methods: {
       google: {
         configFn: import { getConfig } from "@src/auth/google.ts",
         userSignupFields: import { userSignupFields } from "@src/auth/google.ts"
       }
     },
     onAuthFailedRedirectTo: "/login"
   }

   auth: {
     userEntity: User,
     methods: {
       google: {
         configFn: import { getConfig } from "@src/auth/google.ts",
         userSignupFields: import { userSignupFields } from "@src/auth/google.ts"
       }
     },
     onAuthFailedRedirectTo: "/login"
   }

2. Result
With this setup, whenever a user signs up with Google, their email address will be copied to the username field in your User entity automatically—no explicit "after signup" hook is needed for this use case. Note:
Wasp does not yet support general-purpose hooks to run arbitrary code after signup for OAuth providers. If you need to run more complex logic, this is not currently possible directly, but the userSignupFields mechanism covers most field-mapping needs for social auth flows Using the Data Received From Google Social Auth Overview: Overrides. If you need to perform actions beyond field mapping, you may need to wait for future Wasp releases that add support for such hooks, as mentioned in community discussions. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @cmilazzo, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

cmilazzoOP•4mo ago

@kapa.ai I tried adding the usename mapping, but I get a database error when saving. "Argument 'username' is missing". Does the usernname field need to be optional?

kapa.ai•4mo ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- Based on the Wasp documentation, whether the username field should be optional depends on your authentication setup and how you handle user creation. - If you are using social auth (like Google) and you want to ensure that every user has a username, then the username field in your User entity should not be optional (i.e., it should be defined as String, not String?). This way, Wasp will require a value for username when creating a user, and you must ensure that your userSignupFields mapping always provides it. - If you make username optional (String?), then Wasp will allow users to be created without a username, but you must handle the logic for when and how it gets set later. From your error ("Argument 'username' is missing"), it sounds like your User entity expects username to be present (not optional), but your userSignupFields mapping or the data from Google is not providing it in some cases. Double-check that your mapping is correct and that data.profile.email (or whichever field you use) is always available from Google. Example User entity with required username:

entity User {=psl
  id Int @id @default(autoincrement())
  username String @unique
  displayName String
psl=}

entity User {=psl
  id Int @id @default(autoincrement())
  username String @unique
  displayName String
psl=}

Example User entity with optional username:

entity User {=psl
  id Int @id @default(autoincrement())
  username String? @unique
  displayName String
psl=}

entity User {=psl
  id Int @id @default(autoincrement())
  username String? @unique
  displayName String
psl=}

Key points from the docs: - "You can add any other fields you want to the user entity. Make sure to also define them in the userSignupFields field if they need to be set during the sign-up process."
Email Auth API Reference - If a required field is missing during user creation, you will get a database error.
Discord support thread - For social auth, you must ensure your userSignupFields always provides the required fields, or make them optional in the schema.
Social Auth Overview: Overrides Summary:
If you want username to always be set, keep it required and ensure your mapping always provides it. If it might not be set at signup, make it optional in your User entity. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @cmilazzo, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?

Filip•4mo ago

Hey @cmilazzo, just to see if I got everything correctly. You did what Kappa suggested, and then you get this error?

cmilazzoOP•3mo ago

Hi @sodic. There were a number of issues all stacked on each other. I did fix it in the end...

Vinny (@Wasp)•3mo ago

nice. Do you need anymore help?

Gaming

Programming

custom onaftersignup

Did you find this page helpful?