Skip to main content

Authentication Overview

This document describes how authentication is implemented in the Aventian SaaS platform. We use Auth0 for secure, standards-based authentication and Single Sign-On (SSO).

Overview​

  • Identity Provider: Auth0
  • Token Format: JWT (JSON Web Token)
  • Usage:
    • Auth0 handles user authentication.
    • Once authenticated, Auth0 issues a JWT token.
    • This token is included in API requests for verification.
    • Backend services validate the token to authorize access.

Authentication Flows​

Currently, we support two authentication methods:

  1. Email/Password Authentication

    • Standard username/password login.
    • Credentials are stored securely by Auth0.
    • Auth0 issues a JWT on successful login.

  2. Google Authentication (SSO)

    • OAuth-based login using Google identity.
    • Enables Single Sign-On for users with Google accounts.
    • Auth0 acts as the broker and provides a JWT token.

JWT Verification​

  • All APIs expect an Authorization header with a valid JWT: 
    Authorization: Bearer <jwt_token>

  • Backend services validate:

    • Token signature (using Auth0 public keys).
    • Token expiry.

Token Verification API​

For verifying tokens in backend services, use the provided Aventian API: 👉 Auth API Documentation

Mermaid Diagram​

Support​

For authentication and Auth0-related support, contact the Aventian Team.