HectorMRC/rauth

This system is a Rust-based authentication and user-management service that exposes session and user operations over both gRPC and REST. It supports account signup, email verification, password reset, account deletion, and TOTP two-factor authentication, while persisting users, secrets, and metadata in Postgres and using Redis for token or session state. It also publishes user-created events to RabbitMQ, sends email through SMTP, and is packaged as containerized gRPC and REST processes.

This period was focused on defining the authentication and user-management surface for rauth, adding proto contracts for session login/logout and user signup, reset, deletion, and TOTP operations. It also introduced the Rust dependency manifest for the rauth package, pinning core libraries and optional integrations for gRPC, REST, Postgres, RabbitMQ, and Redis, while many repo-wide changes and fixes touched session-related behavior.

3 changes

This period built the shared Rust library layer for an authenticator, adding modules for cryptography, configuration, email handling, validation, and error handling. It introduced user account management with signup, email verification, password reset, deletion, and TOTP support, along with Postgres-backed metadata and secret storage and a script to assemble database setup files.

5 changes

This period established the core runtime and data model for an authentication service, adding database tables for users, metadata, and immutable secrets along with Redis configuration for bounded token storage. It also introduced container build definitions and separate REST and gRPC server entrypoints, wiring repositories, token storage, an event bus, mailer configuration, and session logic into deployable services.

4 changes

HectorMRC/rauth was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.