Barycenter

An OpenID Connect Identity Provider (IdP) implementing OAuth 2.0 Authorization Code flow with PKCE.

Overview

Barycenter is a lightweight, standards-compliant OpenID Connect Identity Provider written in Rust. It implements the OAuth 2.0 Authorization Code flow with Proof Key for Code Exchange (PKCE), making it suitable for modern web and mobile applications.

Features

• OAuth 2.0 Authorization Code Flow with PKCE (S256)
• Dynamic Client Registration - RFC 7591 compliant
• Token Endpoint - Multiple authentication methods (client_secret_basic, client_secret_post)
• ID Token Signing - RS256 with proper at_hash and nonce support
• UserInfo Endpoint - Bearer token authentication
• Discovery - OpenID Connect Discovery and JWKS publication
• Property Storage - Simple key-value storage for user properties

Technology Stack

• Language: Rust
• Web Framework: axum
• Database: SQLite via SeaORM
• Cryptography: josekit for JOSE/JWT operations
• Configuration: config-rs with TOML support

Quick Start

Prerequisites

• Rust 1.70 or later
• SQLite 3

Installation

# Clone the repository
git clone https://github.com/CloudNebulaProject/barycenter.git
cd barycenter

# Build the project
cargo build --release

Configuration

Create a config.toml file (see config.toml for example):

[server]
host = "127.0.0.1"
port = 8080
public_base_url = "http://localhost:8080"

[database]
connection_string = "sqlite://barycenter.db?mode=rwc"

[keys]
jwks_path = "data/jwks.json"
private_key_path = "data/private_key.pem"
signing_algorithm = "RS256"

Running

# Run with default config
cargo run

# Run with custom config
cargo run -- --config path/to/config.toml

# Run with debug logging
RUST_LOG=debug cargo run

Development

Building

# Debug build
cargo build

# Release build
cargo build --release

# Check without building
cargo check

Testing

This project uses cargo-nextest for running tests.

# Install nextest (one-time setup)
cargo install cargo-nextest

# Run all tests
cargo nextest run

# Run tests with logging
RUST_LOG=debug cargo nextest run

Logging

Set the RUST_LOG environment variable to control logging levels:

# Debug level for all modules
RUST_LOG=debug cargo run

# Trace level for barycenter only
RUST_LOG=barycenter=trace cargo run

API Endpoints

Discovery

• GET /.well-known/openid-configuration - OpenID Provider metadata
• GET /.well-known/jwks.json - Public signing keys

OAuth/OIDC

• GET /authorize - Authorization endpoint
• POST /token - Token endpoint
• GET /userinfo - UserInfo endpoint
• POST /connect/register - Dynamic client registration

Properties (Non-standard)

• GET /properties/:owner/:key - Get property value
• PUT /properties/:owner/:key - Set property value

Project Status

This is an early-stage implementation. See docs/next-iteration-plan.md for planned features and docs/oidc-conformance.md for OpenID Connect compliance details.

Currently Implemented:

• Authorization Code flow with PKCE (S256)
• Dynamic client registration
• Token issuance and validation
• ID Token generation with RS256 signing
• UserInfo endpoint

Pending Implementation:

• User authentication and session management
• Consent flow
• Refresh tokens
• Token revocation and introspection
• OpenID Federation support

Deployment

Barycenter supports multiple deployment platforms:

• Docker: Pre-built images available at ghcr.io/[owner]/barycenter
• Kubernetes: Helm chart with Ingress and Gateway API support
• Linux: systemd service with security hardening
• FreeBSD: rc.d init script
• illumos/Solaris: SMF manifest

See DEPLOYMENT.md for detailed installation instructions for each platform.

Quick Start with Docker

docker pull ghcr.io/[owner]/barycenter:latest
docker run -p 8080:8080 -v barycenter-data:/app/data ghcr.io/[owner]/barycenter:latest

Quick Start with Helm

helm install barycenter ./deploy/helm/barycenter \
  --namespace barycenter \
  --create-namespace

Releases

For maintainers: see RELEASE.md for the release process.

To create a new release:

cargo install cargo-release
cargo release minor --execute  # Bumps version and creates release

Contributing

Please read CONTRIBUTING.md for details on our code of conduct, development workflow, and the process for submitting pull requests.

License

[Add your license here]

Acknowledgments

Built with support from the OpenID Connect and OAuth 2.0 communities.