ForjioHuudisIdentityPlugipayPaymentsStorlaunchE-commerceFulkrumaFulfilmentRiplloMarketingLinkSnapShort URLsPawpadoGPU streamingCatentioAgent runtime
Huudis Docs
⌘K

Bring your own social login

By default, "Sign in with Google / Apple / Facebook" runs on Huudis-managed platform credentials — a shared OAuth app maintained by Huudis. That's the fastest way to turn social login on, and for most workspaces it's all you need.

If you'd rather your end-users authenticate against an OAuth app you own, configure your own credentials per provider under Dashboard → Social providers (/dashboard/social-providers). When a provider is configured and enabled, that workspace's end-users sign in through your OAuth app instead of the managed one; leave it unconfigured (or disabled) and the managed credentials remain the fallback.

This governs your workspace's end-users — not the Huudis dashboard login. BYO credentials apply to people signing into your apps through Huudis. The Huudis dashboard's own "Sign in with Google" always uses the platform credentials.

When to use BYO vs managed

Managed (platform) Bring your own
Setup Nothing to do — it just works. Create an OAuth app in the provider's console.
Consent screen Shows Huudis branding. Shows your app name, logo, and domain.
Scopes & quotas Shared platform limits. Your own provider quotas and scope grants.
Best for Getting started, internal tools, low-volume apps. Production apps that want their own brand on the OAuth consent screen, or control over provider quotas.

The two are decided per provider: you can run Google on your own credentials while Facebook stays on the managed fallback.

Configuration fields

Open Dashboard → Social providers, pick a provider, fill in the fields, tick Enabled, and Save. The secret is encrypted at rest and is never shown again — leave it blank on a later edit to keep the stored value, or paste a new value to replace it.

Google

Field Where to find it
Client ID Google Cloud Console → Credentials → OAuth 2.0 Client (type "Web application").
Client secret Same OAuth client.

Facebook

Field Where to find it
App ID Meta for Developers → your App → Settings → Basic.
App secret Same screen.

Apple

Apple needs four values — it doesn't use a simple id/secret pair:

Field Where to find it
Services ID Apple Developer → Identifiers → your Services ID (e.g. com.yourapp.service). Used as the client id.
Team ID Apple Developer → Membership (10-character team identifier).
Key ID The ID of the "Sign in with Apple" key you created.
Private key The .p8 key contents, pasted as PKCS8 PEM (-----BEGIN PRIVATE KEY-----…). Apple lets you download it only once.

The callback URL

Each provider card shows the exact redirect / callback URI to register in the provider's console. It's:

https://huudis.com/api/v1/auth/<provider>/callback

— e.g. https://huudis.com/api/v1/auth/google/callback. Register this exact URL (the match is exact; trailing slashes matter) as an authorized redirect URI in Google Cloud Console, a valid OAuth redirect URI in Meta, or a Return URL on the Apple Services ID. Copy it straight from the dashboard with the Copy button.

You still configure the consent screen / app review with the provider. BYO only swaps in your credentials — Google's consent-screen publishing, Meta's app review for the email permission, and Apple's Services ID setup are unchanged. See Social providers for the per-provider console walkthroughs.

Disabling or removing

  • Disable — untick Enabled and save. End-users immediately fall back to the managed platform credentials for that provider.
  • Remove — deletes the stored credentials for that provider; the workspace reverts to the managed fallback.

A config that's enabled but incomplete (missing secret, or Apple missing the team/key) is treated as not configured — Huudis falls back to managed rather than failing the login.

Next