Authentication

This page is about authentication inside the app you are building on RIB Creative.

Use it when your generated app needs end-user signup, login, logout, sessions, account access, or protected data.

Generated apps can use RIB Cloud auth when the project backend is ready and the required policy allows auth configuration.

The current app-facing auth model supports email/password and Google sign-in.

Email/password flows include:

• Sign up.
• Log in.
• Log out.
• Get the current session.
• Complete a password reset or re-enrollment flow when supported by the project.

Runtime app sessions belong to the generated app and its users.

Auth management

Project owners can use cloud/auth management surfaces when available to inspect auth readiness and app user state without exposing sensitive internals.

Safe owner-facing information can include:

• Whether auth is ready.
• Whether sign-up and login are available.
• Total app users.
• Recent app users.
• Basic user email and creation time.

When direct controls are available, owners can also update an app user's email, enable or disable access, and cancel a pending re-enrollment request from the Cloud Users panel.

It should not expose password hashes, raw session cookies, reset-token internals, or database implementation details.

Google auth inside generated apps

Google sign-in can be configured in Cloud -> Users -> Google.

You can use Managed by Rib or your own Google OAuth credentials. Managed by Rib is the default setup. BYOK requires exact redirect URIs in Google Cloud. The Google settings form shows suggested callback URIs for your published Rib domain and active custom domains, and it keeps saved Client secrets hidden.

Ask the agent to add Google sign-in only after Google auth is enabled for the project. The generated app should use the RIB runtime helpers and must not implement fake Google auth, local-only sessions, or direct browser-side token handling.

Connector policy

RIB Cloud connector policy includes auth-related capabilities.

If auth changes are blocked, the project may need an owner or admin to adjust workspace or project connector settings before the agent can configure real app auth.

Copyable prompt

Plan real authentication for this generated app.
Use the available RIB Creative auth path for this project.
Do not use fake users, hardcoded credentials, or localStorage-only sessions as the final implementation.
Tell me if Google sign-in is not currently available for this app.

Next steps

• Review app auth feature guidance: Google auth
• Learn connector permissions: Connectors
• Configure backend features: Build mode (Agent)