Add “Are you an agent?”
Connect your platform's Auth0 to Versine without replacing your existing auth.
1. Create your workspace
Open Console and sign up using Google or an email code. Complete your name, verified email, company name and company logo. Console is separate from a personal My account. New organizations default to 20 members. See Console onboarding.
2. Register the project
Choose Create project. Add a platform name and an optional platform logo (separate from the company logo). Select Auth0, then provide:
- Auth0 tenant or custom-domain HTTPS origin.
- The connection name you will use in Auth0.
- The exact broker callback: that same origin followed by
/login/callback. - The default S256 PKCE security profile.
- Your public HTTPS authorization-webhook URL.
Under Advanced, optionally enter your platform's Terms of Service and/or Privacy Policy URL. With neither set, Versine introduces no legal-acceptance step. These are your platform's documents—not Versine's own policies.
3. Configure Auth0
Follow the Auth0 guide. Copy the project's client ID and reveal the
client secret only when entering it in Auth0. Never put that secret in the browser.
Use discovery at https://auth.versine.com/.well-known/openid-configuration.
The callback registered in Versine belongs to Auth0. Your application's callback belongs in Auth0's application configuration. Do not interchange them.
4. Add the entry point
Label your login/signup button Are you an agent? and connect it to your existing Auth0 SDK's login operation with the saved Versine connection name. Let the SDK generate and validate state, nonce and PKCE.
For a custom React login page, use your app's Button and a brief accessible description. Do not copy client secrets, one-time codes or tokens into markup. A small description can explain that connecting Versine once lets an assistant sign in with the user's permission. Do not imply it bypasses consent or platform rules.
5. Receive and test authorization
Verify webhook signatures, deduplicate the event ID and return exactly 200 OK after durable handling. Other responses retry; a webhook is not the browser's sign-in completion mechanism.
Test a new user and a returning user, with and without legal URLs. Confirm the same application identity is reused, required approvals block completion, and revocation/blacklist take effect. Verify the final Auth0 session with your existing SDK and keep your app's authorization rules.