silicon VS Keycloak

It's nowhere near as featureful as Outline, but I wrote my own Markdown knowledge base thingy in Python. It is web-based and geared toward single-user (or _very_ small team use) but it's Apache licensed and has no commercial tie-ins. Super easy to deploy as long as you know how to layer some rudimentary authentication on top of it.

https://github.com/cu/silicon

I wrote my own note-keeping system[0] and very much wanted all of the notes to just be markdown files on the disk. It turns out that there are trade-offs to this. If you want plaintext markdown files on disk AND want fancy features like file versioning, a search index, tags, etc then you need to store all of that metadata somewhere and you're down writing a half-assed implementation of a DBMS.

Now, you can certainly bite the bullet and full-ass the implementation like Dokuwiki did, but that is really quite a lot of work and effort against simply `import sqlite` and writing a couple of tutorial-level queries. And it turns out that exporting all of your documents to plaintext, if you should so choose, is a one-line command away.

[0]: https://github.com/cu/silicon

I wrote my own. It's a web app but one of its features is that it doesn't have many features. https://github.com/cu/silicon

It doesn't have folders and tags, but if that's not a deal-breaker you could check out https://github.com/cu/silicon

Not sure which features you're looking for, but you could try this thing I wrote: https://github.com/cu/silicon

3. Very occasionally, I will click on a link on one page to go to another page.

And what would be the point of categorizing all my notes? Every single time I go to my wiki, it's to either write down something specific or search for something specific. I have _never_ wanted to see a list of all of my pages about programming languages for example. Or every page tagged "bash".

I think as software engineers building our own tools, we sometimes build features because they sound interesting and we know how to do it, or because the project doesn't "feel" complete without them. Not because we'll ever actually use them.

When I _do_ want to break up a large subject (e.g. Python) into multiple pages, I just create one "Python" page and link to all of the others from that page.

The one concession I've made to categorization/organization is that I've added a feature where two pages can be marked as "related" to one another. This is mainly to avoid having a manually-edited "See Also" section on pages that touch upon topics covered on other pages.

[1]: https://github.com/cu/silicon

In this article we'll be using Keycloak to quickly augment an application with user management and SSO. We will demonstrate the integration by securing a page for logged-in users. This quickly provides a jump-off point to more complex integrations.

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...