Platform authentication

Last updated: Mar 2, 2026


Rationale

Authentication flows for Fluid Attacks' platform are performed by an in-house implementation. Such implementation currently supports:

  • OAuth with Microsoft Azure
  • OAuth with GitLab
  • OAuth with Bitbucket
  • Email-based OTP tokens for two-factor authentication

The main reasons why we chose it over other alternatives are:

  • It allowed us to federate authentication for all users, so we did not have to store passwords or any other sensitive user information in our database.
  • It allowed our clients to easily control employee access via their enterprise GitLab, Microsoft Azure or Bitbucket user directories. Once a client removed one of their employees from their user directory, access to the platform was automatically blocked for that user.
  • Being a basic component of any application, the authentication module started to exist in the early days of our application.
  • Our needs were simple; we did not need a complex authentication provider at the time.
  • It just worked as expected.

Alternatives

As the application evolved, so did our interest in using a third-party SaaS authentication provider. Below are the ones we have reviewed, ordered from most to least interesting based on our specific needs.

Auth0

Stytch

AWS Cognito

Descope

Kinde

WorkOS

Usage

We use an in-house implementation for all authentication flows at Fluid Attacks' platform.

Other in-house dependencies

On this page