Documentation

Overview Fabrixly-IDS allows users to log in with their mobile phone number instead of an email! Works with all auth modes (password, OTP, 2FA, flexible)! Step 1: Configure Mobile Login for Your Client First, enable mobile login for your OIDC client! Admin Console Setup 1. Go to Fabrixly-IDS

Magic links let users log in by clicking a one-time link sent to their email — no passwords or OTPs required. Fabrixly-IDS handles token generation, storage, expiry, and email delivery automatically. How It Works 1. Your app calls POST /api/auth/magic-link with the user's email

Overview The Implicit Flow was designed for browser-based single-page apps (SPA) that can't keep a client secret secure. It returns tokens directly from the authorization endpoint. ⚠️ Important: Authorization Code Flow with PKCE is now recommended instead of Implicit Flow for SPAs! But we still support it

Overview The Hybrid Flow combines aspects of Authorization Code Flow and Implicit Flow! It returns some tokens immediately from the authorization endpoint and an authorization code that can be exchanged for more tokens! It's useful for apps that want both immediate tokens and refresh tokens! Step 1: Configure

Overview Flexible authentication gives users a choice! They can either enter their password for quick login OR leave it blank to get an OTP! This is the most user‑friendly auth mode! Step 1: Configure Flexible Mode for Your Client First, configure your Fabrixly-IDS client for flexible auth: Admin

This guide describes how to configure SMTP/SMS providers and manage templates dynamically using the REST APIs. 🔐 Authentication & Prerequisites All configuration and template endpoints require administrative authentication. Include the administrator's token: Authorization: Bearer <your-admin-jwt-token> Part A: SMTP & SMS Config APIs 1.

This guide describes how to manage OIDC clients programmatically using the Fabrixly-IDS Client Management APIs. 🔐 Authentication & Prerequisites All client management endpoints require administrative authentication. To call them: 1. Include the Token in the Authorization Header: Add -H "Authorization: Bearer <your-admin-jwt-token>" to

Overview The Client Credentials Flow is for server-to-server (machine-to-machine, M2M) communication—no user involved! Your server authenticates with Fabrixly-IDS using client ID and secret to get an access token for APIs! Step 1: Configure M2M Client First, set up a client for client credentials flow!

Overview The Authorization Code Flow is the most secure and recommended flow for web applications with a backend. It exchanges an authorization code for tokens, keeping the client secret secure. Prerequisites 1. Fabrixly-IDS instance running 2. OIDC client registered in Fabrixly-IDS 3. Node.js (for example code) Step

This guide describes how to register users, manage auth sessions, verify emails, perform password resets, and update user profiles via the REST APIs. 🔑 Authentication Most endpoints in this guide require standard user authentication. Include the user JWT token in your requests: Authorization: Bearer <user-jwt-token> Exceptions: /api/