Open source
Authentication should not be rewritten in every project
Login, sessions and a gateway in front of the API are the same work in every new project. We built it once — and in the open.
CentralAuth
Proof of conceptOne authorization server and one BFF (Backend for Frontend) for all projects
Every new project usually writes its own login, session management and API gateway from scratch. CentralAuth turns that around: a new project simply registers, and its frontends and backends are secured from day one.
Authorization server
One place where login is handled for all applications.
Central BFF
The token never reaches the browser. Ever.
Application registration
A new application is one record, not another piece of configuration.
Sessions and permissions
Revoked access takes effect immediately, not when a token expires.
What we build with
.NET / C#ASP.NET CoreTypeScriptReactPostgreSQLMS SQLDockerKubernetesTerraformAWSAzureGitHub ActionsOpenIddictRedisOpenTelemetry.NET / C#ASP.NET CoreTypeScriptReactPostgreSQLMS SQLDockerKubernetesTerraformAWSAzureGitHub ActionsOpenIddictRedisOpenTelemetry
Technologies: .NET / C#, ASP.NET Core, TypeScript, React, PostgreSQL, MS SQL, Docker, Kubernetes, Terraform, AWS, Azure, GitHub Actions, OpenIddict, Redis, OpenTelemetry.