Skip to content

UltimateAuth — .NET Foundation Project Application #562

Open

Description

@mckaragoz

Community Readiness Self-Check (optional, for your own reflection)

  • My project has at least one merged pull request from someone other than me or an automated bot.
  • My project has been public for at least 3 months.
  • My project has organic GitHub stars, forks, or package downloads that I can't attribute to my own testing or CI activity.
  • I already have a presence in the .NET Foundation Discord and/or other .NET community spaces.

Project Name

UltimateAuth

License

Apache-2.0

Contributor

mckaragoz (Mehmet Can Karagöz)

Existing OSS Project?

Yes

Source Code URL

https://github.com/CodeBeamOrg/UltimateAuth

Project Homepage URL

https://ultimateauth.com/

Project Transfer Signatories

Description

A unified authentication and authorization framework for modern .NET applications, with first-class Blazor/MAUI integration.

What are you hoping from the foundation

Authentication is a security-critical part of modern applications, and we believe .NET developers deserve solutions that combine strong security with an excellent developer experience.

With UltimateAuth, we aim not only to simplify existing authentication patterns but also to explore new architectural approaches that can contribute to the evolution of authentication in the .NET ecosystem.

Through the .NET Foundation, we hope to build greater trust through transparency and community review, collaborate with experienced maintainers and contributors, and accelerate UltimateAuth's development without compromising quality or security.

Our goal is to establish UltimateAuth as a sustainable, community-driven framework that brings simpler integration and fresh architectural approaches to the .NET ecosystem, particularly Blazor and .NET MAUI.

Name

Mehmet Can Karagöz

Email

av.mcankaragoz@gmail.com

GitHub Profile URL

https://github.com/mckaragoz

Committers

  • Mehmet Can Karagöz
    • GitHub: [@mckaragoz](https://github.com/mckaragoz)
    • Role: Project founder, lead maintainer, and committer
    • Employer: Independent open-source contributor (not contributing on behalf of an employer)

Currently, the project is maintained by its founder. Additional committers may be appointed as the contributor community grows.

Discord Ids

mckaragoz - 863883683827417139

Governance Model

UltimateAuth follows a maintainer-led, community-driven governance model.

Contributions are proposed through GitHub issues, discussions, and pull requests, normally targeting the dev branch. Maintainers review changes for security, correctness, architectural consistency, developer experience, compatibility, and maintainability. Automated CI checks and relevant tests support the review process.

Significant changes, particularly those affecting public APIs, authentication behavior, or security boundaries, are encouraged to undergo prior technical discussion. Final decisions are made by authorized maintainers, informed by community feedback and technical evidence.

New committers and maintainers may be appointed by existing maintainers based on sustained contributions, demonstrated technical judgment, trustworthiness, and alignment with the project's principles. Commit access is not granted automatically based on contribution count.

The governance model is documented in GOVERNANCE.md and contribution guidelines in CONTRIBUTING.md.

CLA

  • If already an OSS project, was a Contribution License Agreement in place for contributions accepted?

How does the project check who has signed one?

The project does not currently operate a separate CLA signing or verification process.

Contributions are submitted under the Apache License 2.0 license, as described in CONTRIBUTING.md. We intend to adopt the .NET Foundation CLA process and its automated verification upon acceptance into the Foundation.

CLA Notification Alias

av.mcankaragoz@gmail.com

Select the Project Transfer Agreement model

Contribution

Repository Layout

No major repository restructuring is currently planned.

UltimateAuth is developed in its public GitHub repository under the CodeBeamOrg organization. The dev branch serves as the primary development branch, while master and lab are used for production deployments.

Both maintainers and external contributors follow the same pull request workflow.

We intend to retain the existing repository structure and are open to adopting any recommended changes required by the .NET Foundation during onboarding.

Eligibility Criteria

  • The project is built on the .NET platform and/or creates value within the .NET ecosystem.
  • The project produces source code for distribution to the public at no charge.
  • The project's code is easily discoverable and publicly accessible (preferably on GitHub).
  • The project contains a build script that can produce deployable artifacts that are identical to the official deployable artifacts, with the exception of code signing (Exception may be granted for strong name keys, though strongly encouraged to be committed. Exception relies on OSS signing being in the build script for public builds).
  • When applicable, project must use reproducible build settings in its toolchain.
  • The project uses Source Link.
  • The project uses either embedded PDBs or publish symbol packages to NuGet (if applicable).
  • The project code signs their artifacts as appropriate.
  • The project organization has 2FA enabled. Requiring 2FA must be done as part of onboarding if not already enabled.
  • Libraries that are mandatory dependencies of the project are offered under a standard, permissive open source license which has been approved by the .NET Foundation (exceptions include a dependency that is required by the target platform where no alternative open source dependency is available such as the .NET Framework or a hardware specific library).
  • Committers are bound by a Contributor License Agreement (CLA) and/or are willing to embrace the .NET Foundation's CLA when the project becomes a Member.
  • The copyright ownership of everything that the project produces is clearly defined and documented.
  • The project has a public issue tracker where the status of any defect can be easily obtained.
  • The project has a published Security Policy.
  • The project has a home page which provides high level information about its status and purpose.
  • The project has a public communication channel where community members can engage with maintainers.
  • The project has a publicly available location where members can review and contribute to documentation.

Describe why you are applying for Project Membership.

UltimateAuth was created with an ambitious vision: to make authentication and authorization in modern .NET applications simpler, more unified, and more developer-friendly, without compromising security or architectural flexibility.

We believe UltimateAuth has the potential to become a lasting and widely adopted solution for the .NET ecosystem, particularly for Blazor and .NET MAUI. Its name reflects this ambition: not to claim that authentication is a solved problem, but to continuously pursue a more complete, intuitive, and reliable approach.

We are applying to the .NET Foundation because we believe a project with this ambition deserves strong community involvement, transparent governance, independent technical feedback, and long-term stewardship. Our goal is to grow UltimateAuth beyond its original maintainer and, over time, establish it as one of the Foundation's most valued open-source projects.

Infrastructure Requirements Summary

UltimateAuth currently operates its own development, release, and hosting infrastructure. No immediate infrastructure migration is required.

  • Build and CI/CD: GitHub Actions handles automated builds, tests, compatibility checks, and NuGet package publishing.
  • Package distribution: Official packages are published to NuGet.org using automated release workflows and Trusted Publishing.
  • Web hosting: The project website and documentation are hosted at https://ultimateauth.com/, using existing self-managed infrastructure with Cloudflare and HTTPS.
  • Identity Lab: Our interactive demonstration environment is hosted separately at https://lab.ultimateauth.com/ and uses ASP.NET Core, Blazor Server, PostgreSQL and MudBlazor.
  • Samples: Example applications are maintained in the public repository and can be built and run independently.
  • Signing and certificates: HTTPS certificates are managed through the existing hosting infrastructure. We would welcome guidance on any additional artifact signing requirements recommended by the Foundation.

We intend to maintain our existing infrastructure initially and would appreciate guidance on Foundation-supported services and best practices as the project grows.

Additional Notes

UltimateAuth is a modular, extensible authentication and authorization framework built specifically for the modern .NET ecosystem. Its architecture aims to simplify application development while providing explicit control over authentication flows, sessions, security boundaries, and integration choices.

Architectural Approach

Unlike traditional authentication approaches that primarily revolve around user identity, cookies, or individual tokens, UltimateAuth introduces a unified Root–Chain–Session model. This model represents authentication relationships and session lineage explicitly, providing a consistent foundation for session lifecycle management, revocation, and multi-device scenarios.

Authentication is organized around flow-based operations, allowing different authentication scenarios to share a coherent architectural model rather than relying on disconnected, application-specific implementations.

Modularity and Extensibility

UltimateAuth separates its core authentication responsibilities from optional capabilities through a Plugin Domains architecture.

Domains such as Users, Credentials, Authorization, and Policies provide additional functionality without requiring every application to adopt the entire framework surface.

Extensibility is a fundamental design principle:

  • Authentication modes: Different approaches to session and token delivery can be supported within a unified architecture.
  • Persistence independence: In-memory and Entity Framework Core implementations provide interchangeable storage options.
  • Authorization extensibility: Applications can define custom access policies and integrate authorization decisions with their own domain requirements.
  • Client integration: A unified client API and dedicated Blazor components simplify authentication state, navigation, and protected UI experiences.
  • Architectural separation: Core contracts, reference implementations, and integration packages allow developers to customize individual responsibilities without replacing the entire system.

Developer Experience and Practical Validation

A major focus of UltimateAuth is making authentication feel natural within modern .NET application architectures, particularly Blazor Server, Blazor WebAssembly, and centralized authentication scenarios.

The project includes practical resources demonstrating these capabilities:

  • Identity Lab: A publicly accessible, interactive Blazor application demonstrating authentication, session lifecycle management, credentials, authorization, and administrative operations.
  • Sample applications: Working examples covering multiple Blazor hosting models and client integration patterns.
  • Documentation: Architecture specifications, getting-started guides, migration guidance, and practical integration tutorials.
  • Automated validation: Unit and integration tests, security regression tests, and CI compatibility checks across supported .NET versions.

Position Within the .NET Ecosystem

UltimateAuth operates in an ecosystem with established solutions such as ASP.NET Core Identity, OpenIddict, and Duende IdentityServer. It does not seek to duplicate every capability of these projects. Instead, it explores a different architectural approach emphasizing unified authentication lifecycle management, modularity, extensibility, and developer experience.

The project is publicly available through GitHub and NuGet and is actively developed, although its external contributor community is still emerging.

We believe UltimateAuth has the potential to become a significant long-term contribution to the .NET ecosystem. Through the .NET Foundation, we hope to strengthen community participation, encourage independent architectural and security review, and establish sustainable governance as the project grows.

Project resources:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

project applicationproject supportUse this label to request support for an existing .NET Foundation project

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions