SSO
SSO (Single Sign-On) is not yet available in Robost.
Current authentication
Section titled “Current authentication”Robost uses email and password authentication. When you sign in, the backend accepts a POST /api/auth/login request with your email and password, verifies your credentials against a hashed password stored in the database, and creates a server-side Redis session. The session ID is stored in an HttpOnly cookie named clarity_session, which is scoped to your browser and is not accessible to JavaScript. Sessions have a configurable time-to-live and are deleted on sign-out (POST /api/auth/logout).
If your account has been deactivated by an admin, login returns a 403 error. Invalid credentials return a 401 without revealing whether the email or password was wrong.
Roadmap
Section titled “Roadmap”SAML 2.0, OIDC, Google Workspace, Okta, and Azure AD integrations are on the roadmap. No release date is currently committed.
Early access
Section titled “Early access”If your organisation requires SSO before the feature is generally available, contact support to discuss enterprise pilot options.