20
Google OAuth Does Not Return Separate First Name and Last Name Fields
Source: supabase/supabase#28415 · opened by @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…
No pledges yet. Be the first to back this.
Comments
Similar requests
Supabase cli to accept oauth tokens
2 votes · 0 comments
Enable Supabase SMTP configuration to use Google workspace OAUTH.
4 votes · 0 comments
Native Google Sheets Integration with Supabase (Two-Way Sync)
1 vote · 0 comments
OAuth server: an existing grant auto-approves and returns no client details, leaving no room for an account-confirmation step
1 vote · 0 comments
Ephemeral branches need a stable OAuth callback URL
2 votes · 0 comments
No comments yet.