Google OAuth Does Not Return Separate First Name and Last Name Fields

[theodorosmd]

Description:

I'm using Supabase for authentication in my project and have integrated Google OAuth for user sign-in. However, I have encountered an issue where the user's first name and last name are not returned as separate fields in the authentication response. Instead, the full name is returned as a single string.

Steps to Reproduce:

Set up a Supabase project.
Integrate Google OAuth following the official documentation.
Authenticate using a Google account.

Expected Behavior:

The authentication response should include separate fields for the user's first name and last name, allowing for easier manipulation and storage of user information.

Actual Behavior:

The authentication response includes a single name field containing the user's full name. This requires additional parsing to separate the first name and last name.

Impact:

This issue complicates user management and data handling, especially in applications that require distinct first and last names for personalization, form filling, and other purposes.

Suggested Solution:

It would be beneficial if Supabase could modify the Google OAuth integration to return the user's first name and last name as separate fields. This change would align with the data structure provided by many other OAuth providers and simplify user data handling.

Thank you for your attention to this matter.

[CRREO]

Description:

I'm using Supabase for authentication in my project and have integrated Google OAuth for user sign-in. However, I have encountered an issue where the user's first name and last name are not returned as separate fields in the authentication response. Instead, the full name is returned as a single string.

Steps to Reproduce:

Set up a Supabase project. Integrate Google OAuth following the official documentation. Authenticate using a Google account.

Expected Behavior:

The authentication response should include separate fields for the user's first name and last name, allowing for easier manipulation and storage of user information.

Actual Behavior:

The authentication response includes a single name field containing the user's full name. This requires additional parsing to separate the first name and last name.

Impact:

This issue complicates user management and data handling, especially in applications that require distinct first and last names for personalization, form filling, and other purposes.

Suggested Solution:

It would be beneficial if Supabase could modify the Google OAuth integration to return the user's first name and last name as separate fields. This change would align with the data structure provided by many other OAuth providers and simplify user data handling.

Thank you for your attention to this matter.

hi @theodorosmd - any chance you came to a solution for this? Thank you