PRACTICAL FIELD GUIDE
App signup fails because authentication is disabled
End-user authentication is enabled per project, so a valid-looking signup request can fail when that project has auth disabled. Confirm configuration before debugging password storage.
MCPBackend editorial team · · Examples are illustrative
Put it into practice
- Check the project ID and whether end-user auth is enabled there.
- Use the supported dashboard or MCP configuration flow to enable the intended feature.
- Test a disposable signup and a follow-up current-user request.
What this looks like
ILLUSTRATIVE EXAMPLE
A project copied from a public-data prototype never enabled app auth. Its signup endpoint is present but the feature is not active.
A boundary to keep clear
Enabling authentication does not automatically choose row policies for every table. Configure access separately.
MCPBackend context
Application email/password authentication is separate from the developer dashboard login and MCP OAuth connection. The current app-user tokens are project-scoped and do not automatically expire. Do not assume built-in refresh, password reset, per-token revocation or social login; check supported behavior before designing those flows.
Take the next step
Inspect the current project contract, try the change with disposable data, and verify the result through the same credentials your app will use. Record the expected response and one denied-access case before release.
Sources and further reading
These references explain the underlying protocols and design principles. For supported MCPBackend operations and exact request shapes, inspect your project’s generated API contract.