FAQs
Frequently Asked Questions
General
What is Fabrixly IDS?
Fabrixly Identity Server (IDS) is a complete authentication and authorization platform built on OpenID Connect 1.0 and OAuth 2.0. It is available as a cloud-hosted SaaS — sign up and start using it immediately — and also supports self-hosting for teams who want to run it on their own infrastructure.
Is Fabrixly IDS free?
Yes — Fabrixly IDS offers a free tier on the cloud that you can sign up for and start using immediately, with no credit card required. The free tier includes core features suitable for evaluation and small projects.
For advanced features, higher limits, or custom requirements, additional plans are available. Contact us to discuss your needs or to enquire about upcoming plans.
How is Fabrixly different from Auth0 or Okta?
Auth0 and Okta are cloud-only SaaS platforms. Fabrixly IDS gives you both options — use it as a managed cloud service (sign up and go) or self-host it on your own infrastructure for full control over your data and environment. The free tier makes it easy to get started, and custom plans are available for growing teams and enterprises.
Is Fabrixly IDS compatible with OIDC/OAuth 2.0 standards?
Yes. Fabrixly IDS is fully compliant with OpenID Connect 1.0 and OAuth 2.0. It publishes a standard OIDC discovery document at /.well-known/openid-configuration and works with any standard OIDC client library.
Installation & Setup
What are the minimum server requirements?
For development or low-traffic production:
- 1 vCPU
- 1 GB RAM
- 20 GB disk
- Ubuntu 20.04+ (or any Linux distro with Docker support)
For production with multiple services:
- 2+ vCPUs
- 4 GB RAM recommended
Can I run Fabrixly IDS on a shared hosting plan?
No. You need a VPS or dedicated server with Docker support. Shared hosting providers typically don't allow Docker.
How do I update to a newer version?
docker compose pull
docker compose up -d
docker compose exec backend npm run migrate
Always check the release notes before upgrading for any breaking changes.
Does it support Kubernetes?
Yes. A Helm chart is provided. See the Installation guide → for details.
Authentication
Which authentication methods are supported?
- Password (email + password)
- OTP (email or SMS)
- Magic Link (passwordless email)
- Mobile Number (phone OTP)
- Social Login (Google, GitHub, etc.)
- Password + OTP (2FA)
How do I enable 2FA?
2FA can be configured per-client or enforced system-wide from the Console under Settings → Authentication Policy. Supported second factors: Email OTP, SMS OTP, TOTP (authenticator app).
Can users log in without a password?
Yes. Enable Magic Link or OTP-only flows from the Console. See:
What happens when a refresh token expires?
The user will need to re-authenticate. You can configure refresh token expiry durations in the Console under Settings → Token Policies.
OAuth & OIDC
Which OAuth 2.0 grant types are supported?
- Authorization Code (with PKCE)
- Client Credentials (machine-to-machine)
- Refresh Token
- Hybrid Flow
- Implicit (legacy, not recommended)
How do I create an OAuth client?
Via the Console: Clients → New Client
Or via the API — see the Client Management APIs guide →
Can I restrict which users can access a specific client?
Yes. Use organization-based access control — configure which organizations or roles are allowed to use each client from the Console.
Multi-Tenancy
Does Fabrixly IDS support multiple organizations/tenants?
Yes. Organizations are a first-class concept. Each organization can have its own members, roles, teams, and custom settings. See the Organization Management guide →.
Can I white-label the login page per tenant?
Yes. Branding (logo, colors, domain) can be configured per-organization or globally via the Console. See the Branding & Theme guide →.
Security
Are tokens signed with RS256 or HS256?
RS256 (asymmetric) by default, using a generated RSA key pair. The public JWKS endpoint is available at /.well-known/jwks.json for token verification by resource servers.
How are passwords stored?
Passwords are hashed using bcrypt with a configurable work factor (default: 12). Plain-text passwords are never stored or logged.
Is there rate limiting on auth endpoints?
Yes. Login, OTP, and token endpoints are rate-limited per IP. Limits are configurable in the system settings.
Still have a question?
Contact support → or browse the full documentation at blog.fabrixly.com →