JHipster.NET VS Keycloak

I found this post about a highly customisable .NET Application generator which looks promising. It could be indeed very convenient to gather a fast "start template" for any project. Since the latest release, it looks like we can enable the "CQRS design pattern". I never heard about CQRS before, but from what I understood it uses the mediator pattern from MediatR to do a "seggregation" between queries and commands thanks to an "Application layer". I also found some people arguing that MediatR is good and that they're using it to implement CQRS. I also find that those patterns are very close to the DDD approach. What bothers me is that those patterns‏‏‎‏‏‎‏‏‎‏‏‎­seem really difficult to understand/master. If you're curious just like me, you can try to generate a CQRS app from their Github repository. I find this being a good way to discover this "not so well-known" pattern. But anyway, do you think that it's a good design pattern? I never worked on a project using it, and I'm afraid that the beneffits from this pattern aren't worth the trouble.

Well, I happen to be involved in a code generator (https://github.com/jhipster/jhipster-dotnetcore).

If you're curious just like me, you can try to generate a CQRS app from their Github repository. It find this being a good way to discover this "not so well-known" pattern.

This community is based on JHipster.NET, an open-source .NET application generator based on JHipster !

https://github.com/jhipster/jhipster-dotnetcore https://wrapt.dev/

https://github.com/jhipster/jhipster-dotnetcore is quite nice and lets you generate code using their JDL format which is quite easy to use, not really a starter kit though, goes a bit further than the basics

Hi, i'm the maintener of JHipster.NET (https://github.com/jhipster/jhipster-dotnetcore). The advantage of JHipster.NET it's that the code is generated so you can do whatever you want with it. And there's less magic. That's what i like in this project compared to the other libraries.

Keycloak, an open-source identity and access management solution, provides robust authentication and authorization services for modern applications. However, configuring Keycloak instances manually can be tedious and error-prone. In this blog post, we'll explore how to simplify Keycloak configuration using Terraform and Terragrunt, enabling infrastructure as code (IaC) practices for managing Keycloak realms, clients, users, and more.

In this article we'll be using Keycloak to secure a Vue.js Web application. We're going to leverage oidc-client-ts to integrate OIDC authentication with the Vue app. The oidc-client-ts package is a well-maintained and used library. It provides a lot of utilities for building out a fully production app.

Keycloak has been a leader in the Identity and Access Management world since its launch almost 8 years ago. It is an open-source offering under the stewardship of Red Hat

It sounds like what you're looking for is an identity provider.

A popular open source option is https://www.keycloak.org/

This application can manage your users, then you can use standards like OpenID or SAML to plug it into your application, of which there are usually many plugins to accomplish this depending on your tech stack.

KeyCloak is a Cloud Native Computing Foundation (CNCF) project that offers enterprise IAM solutions. Keycloak emphasizes proficient enterprise authorization solutions by providing:

Outline only uses SSO for authentication. The solution when self hosting is use a private keycloak server [1]. This allows you to do email based auth.

[1] https://www.keycloak.org/

> Keycloak was good but has too much legacy for 10+ years.

I got curious, actually seems to check out and explains why it's so well documented (but also complex and oftentimes confusing):

> The first production release of Keycloak was in September 2014, with development having started about a year earlier.

https://en.wikipedia.org/wiki/Keycloak

https://github.com/keycloak/keycloak/releases/tag/1.0.0.Fina...

> Don't outsource either your authentication or authorization. Run it in-house.

This is hard to do, though. I hope people here will drop a lot of combinations that work for them!

Personally, for a small/medium scale project, I went with:

Keycloak: https://www.keycloak.org/

It supports various backing RDBMSes (like PostgreSQL, MariaDB/MySQL and others), allows both users that you persist in your own DB, as well as various external sources, like social login across various platforms, is an absolute pain to configure and sometimes acts in stupid ways behind a reverse proxy, but has most of the features that you might ever want, which sadly comes coupled with some complexity and an enterprise feeling.

I quite like that it offers the login/registration views that you need with redirects, as well as user management, storing roles/permissions and other custom attributes. It's on par with what you'd expect and should serve you nicely.

mod_auth_openidc: https://github.com/OpenIDC/mod_auth_openidc

This one's a certified OpenID Connect Relying Party implementation for... Apache2/httpd.

Some might worry about the performance and there are other options out there (like a module for OpenResty, which is built on top of Nginx), but when coupled with mod_md Apache makes for a great reverse proxy/ingress for my personal needs.

The benefit here is that I don't need 10 different implementations for each service/back end language that's used, I can outsource the heavy lifting to mod_auth_openidc (protected paths, needed roles/permissions, redirect URLs, token renewal and other things) and just read a few trusted headers behind the reverse proxy if further checks are needed, which is easy in all technologies.

That said, the configuration there is also hard and annoying to do, as is working with OpenID Connect in general, even though you can kind of understand why that complexity is inherent. Here's a link with some certified implementations, by the way: https://openid.net/developers/certified-openid-connect-imple...

You couldn't pay me to use their bullshit...if you need an identity server/provider go with Keycloak. Open source, free, and standards based, works better and scales better too.