Local OAuth testing
dummyauth
Run the sign-in path you will ship, on your machine, without opening OAuth apps in every vendor dashboard just to iterate.
Sign in and create a project. Add a provider preset, register your redirect URLs, and add dummy users for consent screens.
On Integration, copy ready-to-paste env vars so names match what you use in production. When you go live, change the base URL and client id and secret.
- GitHub
- Microsoft
- Cognito
- Generic OIDC
Use cases
For anyone who needs realistic login flows without provisioning real Google, GitHub, or similar projects for every machine and pipeline.
App developers
Exercise the same login path you ship against the preset that matches production, without creating OAuth apps in every vendor dashboard.
Teams and shared dev setups
Share one project slug and the same Integration copy so local setup stops drifting into "works on my machine."
CI and end-to-end tests
Point automation at a stable local base URL. Use redirect URLs that fit your runner, including wildcards when ports change every run.
Library and SDK authors
Hit each vendor's metadata and key URLs through one local stand-in instead of hand-maintaining mocks per provider.
Demos and workshops
Walk through real redirects and consent without provisioning cloud identity projects for the room.
Multi-provider and migration prep
Keep the environment variable names your framework expects. Point at dummyÔauth until you go live, then swap the URL and client id and secret.
How it works
Three steps from sign-in to a working login loop on your machine.
Account
Sign in with GitHub, then create projects and add provider presets.
Project and providers
Each project gets its own URL. Add one or more presets per project.
Clients and dummy users
Register redirect URLs, add dummy personas, then copy env snippets and endpoints from Integration into your app.
Ready to try it?
Sign in with GitHub and create a project in minutes.
Development and automated testing only
dummyÔauth is for local development and automated tests only. Do not expose it to the public internet without hardening. It is not a production identity provider.