Adding a custom OAuth provider without touching environment variables

Titre : Adding a custom OAuth provider without touching environment variables

Catégorie : Guides

Corps

Most boilerplates make you add OAuth support by editing .env, redeploying, and hoping you got the callback URL right on the first try. NeoSaaS ships with Google, GitHub, Microsoft, and Facebook already wired up — and none of them touch your environment variables.

Provider credentials are entered once from the admin panel and stored encrypted in the database. Toggling a provider on or off, or rotating a leaked client secret, takes effect immediately — no redeploy, no downtime.

Under the hood, each provider has its own route pair: one to start the flow (with CSRF protection via a signed state parameter) and one to handle the callback, exchange the code, and either create a new account or link the login to an existing one. If you're adding a fifth provider that isn't built in, this is the pair of routes you'd model it on.

CTA de fin

Full details in the Authentication documentation.