Bifrost Auth

Warning

This application is still in early Alpha, it is not ready for production usage!

Currently the backend is still in development, frontend development has yet to begin. A production ready release for v0.1.0 is aimed for around January but timelines may change

An EVE Online authentication platform for coaltions, alliances, and corporations. Built by The Order of Autumn, a corporation part of Black Rose alliance & Phoenix Coalition.

The goal is to create an authentication platform written for high performance, large-scale, and support for multiple corporations & alliances to exist within the same instance or to link their own instance with minimal hassle. Flexibility should be offered for corporations & alliances to have their own group configurations and discords within an auth instance as determined by the administrators.

Roadmap

Subject to change, this is a rough draft of goal modules

0.1.0 - Core Functionality (January 2026)

• OAuth2 with EVE Online (Completed)
• Job scheduler and worker (In progress, needs metrics dashboard)
• Groups (Multi-tenant groups owned by auth, other groups, alliances, and corporations)
• Admin & permissions (Admin login & controls)
• Communications - Discord (Support for multiple Discord instances)

0.2.0 - Audit & Recruitment (Quarter 1 2026)

• Character Audit (ESI check assets, mails, wallet etc)
• Corporation Audit (ESI check assets, wallet, structures)
• Recruitment (List corporations accepting applications, create applications to corporations)

0.3.0 - Fleet Tools (Quarter 2 2026)

• Timerboard
• Doctrines
• SRP
• Communications - Mumble (Including temp links)

0.4.0 Economy & Industry (Quarter 2 2026)

• Buyback
• Logistics
• Moon mining
• Market

0.5.0 - Dev API & Instance Linking (Quarter 3 2026)

• Developer API (Provide API endpoints similar to ESI to access Bifrost information for 3rd party apps)
• Syncing (Link bifrost instances together so members don't need to login to multiple auths)

3rd party extensions to the auth may or may not be possible as Rust is harder than Python/PHP to dynamically modify the code but it has been done. This will be lowest in development priority, we'll aim to provide first-party support for all of the most utilized features for auth platforms and investigate plugins later as demand necessitates it.

Deployment

Prerequisites

Install Dependencies

• Docker
• git

Clone the repository

git clone https://github.com/autumn-order/bifrost

Create EVE Online Developer Application

Create a developer application at https://developers.eveonline.com/applications

• Set callback URL to https://your.domain.com/api/auth/callback
• Enable ALL scopes for the application

Configure Environment Variables

cp .env.example .env

Set the following in .env:

• DOMAIN (Set to your domain, e.g. bifrost.autumn-order.com)
• CONTACT_EMAIL (Email for EVE developers to contact you if any issues occur)
• ESI_CLIENT_ID (Get from https://developers.eveonline.com/applications)
• ESI_CLIENT_SECRET(Get from from https://developers.eveonline.com/applications)
• ESI_CALLBACK_URL (This will be what you set in your dev application https://your.domain.com/api/auth/callback)
• POSTGRES_PASSWORD (Set to a secure password)

Running for Production

1. Start traefik proxy instance

sudo docker network create traefik

sudo docker compose -f docker-compose.traefik.yml up -d

2. Run Bifrost

sudo docker compose up -d

This will take a few minutes to build depending on server resources, this will only occur on first startup or after updating

Updating

1. Pull repository changes

git pull

2. Rebuild the application with the --build flag

sudo docker compose up -d --build

Development

Prerequisites

Install Dependencies

• BunJS
• Rust
• Dioxus
• Docker

Install the tailwindcss dependencies with:

bun i

Create EVE Online Developer Application

Create a developer application at https://developers.eveonline.com/applications

• For development set callback URL to http://localhost:8080/api/auth/callback
• Enable all scopes for the application

Configure Environment Variables

cp .env.example .env

Set the following in .env:

• DOMAIN (Unnecessary for testing on localhost, ignore it)
• CONTACT_EMAIL (Email for EVE developers to contact you if any issues occur)
• ESI_CLIENT_ID (Get from https://developers.eveonline.com/applications)
• ESI_CLIENT_SECRET(Get from from https://developers.eveonline.com/applications)
• ESI_CALLBACK_URL (For development, this will be http://localhost:8080/api/auth/callback)
• POSTGRES_PASSWORD (Set to a secure password)
• DATABASE_URL (Replace the POSTGRES_PASSWORD within the DATABASE_URL to the password you set)

Running for Development

1. Start the development Postgres instance with:

docker compose -f docker-compose.dev.yml up -d

2. Run tailwindcss

bunx @tailwindcss/cli -i ./tailwind.css -o ./assets/tailwind.css --watch

3. Start the dioxus application in a separate terminal

dx serve

The application can now be found at http://localhost:8080

Database Migrations

Ensure the development postgres instance is running first:

docker compose -f docker-compose.dev.yml up -d

1. Apply migrations to the database

sea-orm-cli migrate

2. Generate entities based upon database tables applied by the migration

sea-orm-cli generate entity -o ./entity/src/entities/ --date-time-crate chrono

You can then find the API docs at http://localhost:8080/api/docs

Additionally Useful DB Commands

Drop all tables & reapply migrations

• Use this if you modified migrations and need a fresh start

sea-orm-cli fresh

Rollback all applied migrations & reapply them

• Use this to ensure both your up & down methods of your migrations work

sea-orm-cli migrate refresh

Testing

Run tests for the server with:

cargo test --features server

For tests which include redis

Redis-Related Tests

Redis-related tests include anything involving the worker or scheduler. Including redis-related tests will increase test execution time by about 5 seconds & requires an active redis instance, hence why it is feature-gated.

1. Start development docker compose which contains a redis instance

docker compose -f docker-compose.dev.yml up -d

2. Run tests including redis

cargo test --features redis-test

Code Coverage Report

Generate code coverage report with cargo-llvm-cov:

• Use redis-test feature to include redis-related tests as well

cargo llvm-cov --open --features server --ignore-filename-regex "client\/|entity\/|migration\/|bifrost-test-utils\/"