Platform authentication

Last updated: Apr 13, 2026


Rationale

Authentication flows for Fluid Attacks' platform are handled by Auth0, a third-party identity platform. Auth0 acts as the identity layer, while the platform issues its own JWT tokens for API authorization.

The platform currently supports the following identity providers via Auth0:

  • Google
  • Microsoft Azure AD
  • Bitbucket

The main reasons why we chose Auth0 are:

  • It federates authentication for all users, so we do not store passwords or any other sensitive user information in our database.
  • It allows our clients to easily control employee access via their enterprise Microsoft Azure or Google user directories. Once a client removes one of their employees from their user directory, access to the platform is automatically blocked for that user.
  • Its Terraform provider allows us to manage the entire configuration as code.
  • It has a >99% availability SLA.
  • It supports a wide number of enterprise identity providers, allowing us to support protocols like SAML, OIDC, LDAP, Azure Active Directory, and Google Workspace, among others.
  • It implements protections against bot attacks, brute force attacks, etc.
  • It supports many MFA factors, including push notifications, SMS notifications, one-time passwords, email notifications, and recovery codes, among others.

Alternatives

Below are the other authentication providers we reviewed before choosing Auth0, ordered from most to least interesting based on our specific needs.

Stytch

AWS Cognito

Descope

Kinde

WorkOS

Usage

We use Auth0 for all authentication flows at Fluid Attacks' platform. The tenant configuration is managed as code via Terraform in the integrates/infra directory.

Other dependencies

On this page