fusionauth-issues VS ASP.NET Core

Compare fusionauth-issues vs ASP.NET Core and see what are their differences.

fusionauth-issues

FusionAuth issue submission project (by FusionAuth)

ASP.NET Core

ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux. (by dotnet)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
fusionauth-issues ASP.NET Core
22 1629
86 34,175
- 1.8%
7.0 9.9
about 1 month ago 4 days ago
C#
- MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

fusionauth-issues

Posts with mentions or reviews of fusionauth-issues. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-22.
  • Show HN: Auth0 OSS alternative Ory Kratos now with passwordless and SMS support
    4 projects | news.ycombinator.com | 22 Feb 2024
    Gotcha. We definitely don't have fine granularity around when MFA is required (open issue here: https://github.com/FusionAuth/fusionauth-issues/issues/2285 ).

    Other than that I'd suggest putting a page in front of our login pages with the domain logic, and modeling each set of emails as either an application, organization or tenant, depending on the specific features you need.

    Either way, hope you find the right solution for your needs!

  • Keycloak SSO with Docker Compose and Nginx
    21 projects | news.ycombinator.com | 11 Feb 2024
    Great question. Appreciate the interest.

    I can only speak from my perspective as an employee, not the whole company. It is something I've thought about. I will also ask the CEO/founder or other leaders to weigh in.

    Many devs care about open source when they are evaluating a solution, but many really want "free as in beer". They want to try a product without getting out the credit card or engaging with sales. We cater to the latter category, which wants to understand the product quality without talking to any sales people.

    Some of these folks use our community product for their production needs, which is perfectly fine. We have people running FusionAuth in production with 1000s of tenants or 10000+ applications. (I always say they "pay" us by filing bug reports, giving feedback and voting on feature requests.)

    But some decide they want to pay us for hosting, support or advanced features. Those choices help us build a business.

    Devs, and especially buyers, are interested in sustainability of a product they are going to integrate into their system. An auth provider isn't a javascript widget that you can easily drop in or remove from your system. It embeds in your system, even if you stick to a standard like OIDC, and is difficult to switch from, especially at scale. You want to be sure the company and product is going to stick around. (If you want to make sure you can run the product even if everyone at FusionAuth wins the lottery, we do offer source code escrow for a price, but haven't had anyone take us up on it.)

    FusionAuth is a profitable company (we did recently raise a round to accelerate growth, you can read more about that here [0]). Open source companies often have a hard time meeting the profit goals of the market or investors. This is a known issue and often results in relicensing or changing the rules, as we've seen with Hashicorp[1] and Elastic[2]. This switcheroo can cause issues, confusion, and ill-will; FusionAuth's licensing avoids that.

    FusionAuth also develops in the open[3]. This open development process gives us another common benefit people get from OSS--community feedback.

    Also, I don't want to throw shade at Ory and Zitadel, since I have no idea about their finances (apart from a brief look at Crunchbase, which shows they've raised 22.5M[4] and 2.5M[5] respectively). I hope they're building sustainable businesses, but selling closed source software is a sure route to a profitable business that has built many big companies (including in the auth space, such as Okta or Auth0). Again, this is not FUD (or at least I don't intend it to be!), just an honest assessment at the difficulties of making money in open source dev tools [6].

    We also compete on features, support and documentation. Again, I can't speak to Ory or Zitadel; they look nice, but I haven't built anything with them, so it is hard for me to know how good they are. I do know that we have had many clients appreciate of those aspects of our product.

    To sum up:

    * FusionAuth has a free option, which helps reduce friction and gives some of the benefits of OSS. The open process and escrow also give some of the benefits of OSS.

    * Some devs and buyers care about business sustainability, especially when integrating a tool deeply into their application. FusionAuth will never have to worry about relicensing a version because AWS is eating our SaaS revenue stream, for example.

    * We offer great support, documentation and intricate auth features at a reasonable price.

    Hope this helps.

    0: https://fusionauth.io/blog/fusionauth-and-updata

    1: https://www.hashicorp.com/license-faq

    2: https://www.elastic.co/pricing/faq/licensing

    3: https://github.com/FusionAuth/fusionauth-issues/issues/

    4: https://www.crunchbase.com/organization/ory/company_overview...

    5: https://www.crunchbase.com/organization/zitadel

    6: I wrote about this a few years ago on my personal blog: https://www.mooreds.com/wordpress/archives/3438

  • Show HN: Kinde – auth, feature flags and billing (Q3) in one integration
    4 projects | news.ycombinator.com | 18 Apr 2023
    Disclosure, I work for FusionAuth.

    > Multi-tenant (each of my customers gets a fully separate directory, with access to all tenants for our admins)

    Yup.

    > SAML and OAuth (customers can set up SAML themselves via the SaaS interface, or we set the SP up for them)

    You'd have to build an interface using our APIs for this. Not available out of the box, but we do have it in the general roadmap (https://github.com/fusionauth/fusionauth-issues/issues/91 is the tracking issue).

    > Rule based group assignment based on SAML attribute evaluation (e.g. assign users to this group if the attribute X = Y)

    You could do this with Lambda HTTP Connect (a paid feature) or webhooks (a free feature. https://fusionauth.io/docs/v1/tech/lambdas/#using-lambda-htt... has more

    > APIs to manage users, groups, organisations (tenants)

    Yup.

  • Ask HN: Lightweight Authentication
    4 projects | news.ycombinator.com | 29 Dec 2022
    My employer (FusionAuth) has the same feature in our community edition and it's quite popular: https://fusionauth.io/docs/v1/tech/passwordless/magic-links

    It is glorious from the user perspective, but there are actually some subtleties from the implementation perspective that caused us some grief.

    First of all, you have email configuration and deliverability. The answer is to outsource it to a provider like Sendgrid, SES, or Mailgun.

    Then, there's anti phishing email software which can expire one time tokens as it probes to prevent phishing attacks. More on how we built around that here: https://github.com/FusionAuth/fusionauth-issues/issues/629

  • Tell HN: Stytch Login SaaS Unicorn has common auth vulnerabilities
    6 projects | news.ycombinator.com | 11 Oct 2022
    > just invalidate them after use

    I can't speak for Stytch, but I know at $CURJOB, we have run into issues with this where corporate phishing protection software invalidates one time use codes. I believe it does that because it retrieves links in emails before the user clicks on them. This was an issue several of our customers have raised. So it isn't as straightforward as you might think.

    There's more details, including the workaround we ended up using, on the GH issue: https://github.com/FusionAuth/fusionauth-issues/issues/629

    PS I agree they should absolutely have guidance around link lifetime as well as safe defaults. Converting the links to one-time use seems like a good start.

  • Tell HN: Somebody implemented something I wrote a blog about
    5 projects | news.ycombinator.com | 20 Sep 2022
    Such a great idea! I filed a feature request on our GH issues list to implement this: https://github.com/FusionAuth/fusionauth-issues/issues/1888
  • Are Magic Links Outdated?
    4 projects | news.ycombinator.com | 13 Jul 2022
    Another issue that I don't see covered here is that some email clients (looking at you, Outlook) pre-fetch links to see if they are security risks. If you build a magic link system which handles plain old GETs, the one time code gets used up before the user can actually log in.

    We ran into this at FusionAuth and had to do implement some workarounds, documented here: https://github.com/FusionAuth/fusionauth-issues/issues/629#i...

    Edit: https://news.ycombinator.com/item?id=32081192 mentions some other issues.

  • Ask HN: Anyone use GitHub Issues at their company?
    3 projects | news.ycombinator.com | 29 Mar 2022
    We do, extensively, both internally and externally. In fact, we don't have any other explicit way to order engineering work. (There's always the "inside the CTO's head" priority list, but we strive to get that into GH issues.)

    https://github.com/fusionauth/fusionauth-issues/issues is our main external facing repo. We use it:

    * to track issues. Every code change should tie back to an issue in this repo.

    * to get feedback from the community. People can upvote issues that are important to them.

    * to take input from the community. If someone wants a feature added or a bug fixed, we ask them to file an issue. This is a desired bit of friction (if you can't be bothered to file an issue, then you probably don't care that much).

    * to expose the near term roadmap to customers and community members (we do this using milestones)

    * to expose our decision making and prioritization process. We've had customers say they loved that about our product. The product is not open source, but the development process is as transparent as we can make it (see https://github.com/FusionAuth/fusionauth-issues/issues/1577 for example).

    It's great for all those things. On to your concerns:

    * bug reporting: yes, but make sure you use templates

    * sprint/epic management: okay for that. Not easy to tie bugs together in any structured way (we use a 'related bugs' section of the issue description, but that depends on frail humans to keep it up to date)

    * release management (from development, to code review, to QE verification, to release): less familiar with this, I know there is a kanban view that we've used. Milestones are useful here.

    * integration with non-engineering teams (ie, letting customer support/customer success tag issues that customers have brought up): as long as they are GH knowledgeable, it'll work.

    From my limited jira experience, it's much more powerful when you have teams of teams and need reporting and customization. But for a team our size (<10 engineers), GH issues has been great.

  • AWS is playing chess, Cloudflare is playing Go
    8 projects | news.ycombinator.com | 18 Oct 2021
    This is our major need right now:

    https://github.com/FusionAuth/fusionauth-issues/issues/1393

    Basically, providing a static IP to some EC2 instance traffic so that folks can add an IP to their firewall.

  • Kanidm: A simple, secure and fast identity management platform
    6 projects | news.ycombinator.com | 16 Oct 2021
    Interesting that they are choosing to provide an integrated solution including user management and OAuth IdP ( https://github.com/kanidm/kanidm/pull/485 ) rather than plug into existing open source or even commercial offerings.

    Here's a design doc about their OAuth choices: https://github.com/kanidm/kanidm/blob/master/designs/oauth.r...

    It would seem simpler to go with the Ory approach of "best in breed" for, say network management tooling (most of which they already have implemented), and then integrate with Keycloak, Okta, FusionAuth, the Ory suite, etc for user management. Maybe they didn't want to do that because there are synergies with integrated user management? I dunno, seems like there are a lot of user management tools out there.

    I also find it interesting that they explicitly disallow a goal of building a better LDAP server. I think there's a lot of room to run in that. My employer has had users show a fair bit of interest in a modern experience with LDAP layered on top ( https://github.com/FusionAuth/fusionauth-issues/issues/954 ) and I talked to someone at a conference that had built a whole business out of virtual LDAP: https://www.radiantlogic.com . They were working with companies with multiple LDAP based auth systems, and providing a way to have apps see one view of the user.

    Maybe kanidm isn't that project, but it seems like a modern OSS LDAP implementation would be welcomed by the software community.

    Disclosure: I work at FusionAuth.

ASP.NET Core

Posts with mentions or reviews of ASP.NET Core. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-18.
  • The Mechanics of Silicon Valley Pump and Dump Schemes
    8 projects | dev.to | 18 Feb 2024
    Even if you look at Microsoft’s by far most popular GitHub project, they’re still only half as big as SupaBase. If you believe “the SupaBase story”, SupaBase grew and became twice as large as Microsoft in 3 years. Below is their likes over time if you’re curious, together with a couple of additional “too good to be true” Silicon Valley projects.
  • Evolutive and robust password hashing using PBKDF2 in .NET
    3 projects | dev.to | 26 Dec 2023
    To achieve these objectives, we will take inspiration from ASP.NET Core Identity's PasswordHasher class. It incorporates a concept of hash versioning, allowing only the number of iterations to be modified.
  • I'm not a Java dev but I'm using it in AoC this year
    2 projects | /r/java | 6 Dec 2023
    Visual Studio is far superior to Intellj and the library is different. In Java you 500 json parsers. In C# its built in the language and otherwise Newtonsoft is the main standard. You don't need 500 web app frameworks, ASP.NET Core has everything you need and EF and Dapper solves your database needs. The tech stack in dotnet is pretty standardised.
  • Is anyone using a dotnet static site generator.
    6 projects | /r/dotnet | 5 Dec 2023
    This got me thinking whether there is a decent dotnet static site generator. With blazor able to generate text without entering into the asp.net pipeline it could be done with a console app.
  • Microsoft.NET.Publish.targets Illegal Character in Path
    2 projects | /r/dotnet | 23 Nov 2023
    I created VS solution with an asp.net core backend and React frontend as separate projects following this tutorial/template. It's an old GitHub link because I created the project before the official page was updated.
  • ASP.NET Core Blazor
    5 projects | news.ycombinator.com | 6 Oct 2023
    I don't understand why this is seemingly not given more priority at MS: https://github.com/dotnet/aspnetcore/issues/41909 My prediction is that this will kill off the technology if they don't find a solution.
  • The state of modern Web development and perspectives on improvements
    5 projects | dev.to | 24 Aug 2023
    First is the size. Writing a server-side and client-side program is possible with Rust, and the resulting WASM package will be small enough. At the same time, Microsoft Blazor converts C# code to WASM, but the client delivery has to include the reduced .NET runtime, taking several megabytes for a script. The same is true for GoLang, even with an attempt to reduce the runtime delivery in TinyGo WASM. Developers want to work with their favorite languages, whether it is Java, Kotlin, Dart, C#, F#, Swift, Ruby, Python, C, C++, GoLang, or Rust. These languages produce groups of runtimes. For example, JVM and .NET have many common parts, Ruby and Python are dynamically interpreted at runtime, and all mentioned depend on automatic garbage collection. For smaller WASM packages, browser vendors can include extended runtime implementations, for example, by delivering a general garbage collector as part of WASM. Garbage collection support by WASM is currently in progress: WASM GC, .NET WASM Notes.
  • ASP.NET Core VS Code_behind - a user suggested alternative
    2 projects | 4 Aug 2023
    2 projects | 23 Jul 2023
  • I am learning C#, and ASP.NET MVC from Kudvenkat so Is there any issue?
    2 projects | /r/dotnet | 9 Jul 2023
    hey, I am a beginner and am learning c# and asp.net MVC from Kudvenkat so any issues mean Kudvenkat`s videos are 10 years old so any problem? and if there are jobs on .NET and they want skills like c#,asp.net MVC then If I learn c# and asp.net MVC from kudvenkat then any issues?

What are some alternatives?

When comparing fusionauth-issues and ASP.NET Core you can also consider the following projects:

Blazor.WebRTC

Introducing .NET Multi-platform App UI (MAUI) - .NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.

deno - A modern runtime for JavaScript and TypeScript.

inertia-laravel - The Laravel adapter for Inertia.js.

PuppeteerSharp - Headless Chrome .NET API

CefSharp - .NET (WPF and Windows Forms) bindings for the Chromium Embedded Framework

Giraffe - A native functional ASP.NET Core web framework for F# developers.

.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.

LocalStorage - A library to provide access to local storage in Blazor applications

Microsoft.Maui.Graphics - An experimental cross-platform native graphics library.

eShopOnContainers - Cross-platform .NET sample microservices and container based application that runs on Linux Windows and macOS. Powered by .NET 7, Docker Containers and Azure Kubernetes Services. Supports Visual Studio, VS for Mac and CLI based environments with Docker CLI, dotnet CLI, VS Code or any other code editor. Moved to https://github.com/dotnet/eShop.

CodeBehind Framework - CodeBehind library is a modern backend framework. This library is a programming model based on the MVC structure, which provides the possibility of creating dynamic aspx files in .NET Core and has high serverside independence.