Clearance
Keycloak
Clearance | Keycloak | |
---|---|---|
7 | 230 | |
3,671 | 19,946 | |
0.2% | 2.2% | |
6.2 | 10.0 | |
16 days ago | 3 days ago | |
Ruby | Java | |
MIT License | Apache License 2.0 |
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.
Clearance
- Devise 🥳
-
What is used for authentication in Rails nowadays?
https://github.com/thoughtbot/clearance It is simple and good. You can also customize it easily.
-
Devise. love it or hate it?
Clearance has been better for most of my projects. Its got a cleaner implementation that Devise, and comes with a generator that will optionally dump all of the basic routes and views into the standard locations which you can then edit at will.
-
What's going on with Devise for Rails 7 ?!
I tend to suggest Clearance for Rails apps that need a more focused toolset. It may not do everything that Devise does, but it definitely works well with Rails 7. https://rubygems.org/gems/clearance/versions/2.5.0
-
Simple, secure, low maintenance auth that doesn’t rely on Facebook, Google etc?
I've found a much simpler/cleaner authentication gem is Clearance. Devise does just about everything, but Clearance is more opinionated so out of the box it does more of what you normally want.
-
Why am I having such a bad time with Rails?
...because some folks prefer clearance to devise! :-D
-
26 most popular Ruby/Rails repositories on GitHub in July-August 2020
Clearance is a Rails authentication with email & password. It is intended to be small, simple, and well-tested. It has opinionated defaults but is intended to be easy to override. 3,321 stars by now
Keycloak
-
Simplifying Keycloak Configuration with Terraform and Terragrunt
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.
-
Securing Vue Apps with Keycloak
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.
-
User Management and Identity Brokering for On-Prem Apps with Keycloak
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
- Navigating Identity Authentication: From LDAP to Modern Protocols
-
Ask HN: No-code, simple-setup user management
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.
-
Top 6 Open Source Identity and Access Management (IAM) Solutions For Enterprises
KeyCloak is a Cloud Native Computing Foundation (CNCF) project that offers enterprise IAM solutions. Keycloak emphasizes proficient enterprise authorization solutions by providing:
-
Outline: Self hostable, realtime, Markdown compatible knowledge base
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 open redirect: wildcard redirect URIs can be exploited to steal tokens
> 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...
-
What Is OIDC?
> 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...
-
Auth0 increases price by 300%
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.
What are some alternatives?
Devise - Flexible authentication solution for Rails with Warden.
authelia - The Single Sign-On Multi-Factor portal for web apps
Sorcery - Magical Authentication
authentik - The authentication glue you need.
JWT - A ruby implementation of the RFC 7519 OAuth JSON Web Token (JWT) standard.
Apache Shiro - Apache Shiro
Authlogic - A simple ruby authentication solution.
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
Knock - Seamless JWT authentication for Rails API
IdentityServer - The most flexible and standards-compliant OpenID Connect and OAuth 2.x framework for ASP.NET Core
OmniAuth - OmniAuth is a flexible authentication system utilizing Rack middleware.
Spring Security - Spring Security