Support for custom Google OAuth (bring-your-own client)

Right now, when users sign in with Google, the consent screen always says “to continue to base44.com. I’ve already set up SSO, but it still uses Base44’s Google OAuth project.

For branding and trust reasons, I’d like to use my own Google OAuth client so the login screen shows my app name/domain instead of Base44.


Why it matters:

  • White-label experience (users see my brand, not Base44).

  • Better trust for end-users since they recognize my company instead of a third party.

  • Consistency with custom domains and other white-label features.

Proposed solution:

  • Allow projects to supply their own Google OAuth client ID/secret.

  • Provide a way to configure redirect URIs in Base44.

  • If no custom OAuth is set, fall back to Base44’s default (current behavior).

This would give teams more control and a fully white-labeled login flow.

Please authenticate to join the conversation.

Upvoters
Status

In Review

Board
💡

Feature Request

Date

8 months ago

Author

Ginny Thomas

Subscribe to post

Get notified by email when there are changes.