Paperless VS authentik

Paperless-ngx is the successor to the original Paperless & Paperless-ng projects, both of which are now in public archive. The original projects are not dead, but rather, continued through the open source community!

There's this:

https://github.com/the-paperless-project/paperless/issues/20

I don't know if it made it's way into this fork.

Paperless: https://github.com/the-paperless-project/paperless

Agreed. It's difficult to beat paperless* for single-user systems. It does have some rudimentary user management from Django, but it's an admin party and there's no way to give users separate repositories. They've been looking into it for years, going back as far as the original paperless project. I imagine such a feature is difficult to add on as an afterthought because it touches everything, so it should be built in from the very beginning. And it seems they're looking for a perfect implementation, which may or may not exist. Thus, years later, paperless* remains effectively a single-user app.

If I understand this correctly, the original Paperless was archived (Archival notice)[https://github.com/the-paperless-project/paperless/commit/9b...], so Paperless-NG was created.

Now that Paperless-NG seems to be going unmaintained (last commit on 15th Sep 2021), Paperless-NGX has been created with a focus on an org, so that the continuity of the project can be maintained with a simple path for the original creators to join back if they want to.

I don't think the community could have handled this better!

As many of you know "Paperless-ng" was a very popular fork of the document management system "Paperless". The initial author of -ng, Jonas Winkler, created an amazing project that was eventually designated as the 'official' successor. He maintained a furious development pace for some time but as of this post hasn't been heard from in months. A group of folks dedicated to the software (myself included) decided to try and revive the project and hopefully set it up for a long future. Yes, a similar thing happened with the original Paperless, we are hoping to avoid some of the same mistakes. See jonaswinkler/paperless-ng#1599, jonaswinkler/paperless-ng#1632 and historically the-paperless-project/paperless#711 if you are curious for more about all of this.

yes, I know that project. Paperless-ng is actually a fork of paperless project. I borrowed many great ideas from both projects. Unfortunately both projects are now archived (paperless-ng is not officially archived, but in last 6 months there was no development, as it looks to me that main developer lost interest in the project).

I have a Brother ADS-1700W, works fine, a little fiddly to set up the profiles for one touch scanning but once it's done it's fine. I set up a workflow with https://github.com/the-paperless-project/paperless that lets me scan straight into OCR. https://github.com/jonaswinkler/paperless-ng is the fork that I'm going to upgrade to in my CFT.

If you're looking for a system that has more features, is user friendly, a nice admin ui and easy deployments compared to Keycloak. Please give https://goauthentik.io/ a shot. Not affiliated in any way, just a very happy user.

It has

-an admin UI

- Supports (LDAP, SAML, OAUTH, social logins)

- MFA, Passkeys

- Application access based on user groups etc

Hey, for authentik this is actually something we're actively working on: https://github.com/goauthentik/authentik/pull/8330, and this will be included in our next feature release in April!

(Disclaimer, I am founder and CTO of authentik)

See here for the fix, which both implements the workaround suggested in the issue and also a much more standard-compliant method: https://github.com/goauthentik/authentik/pull/8471

Ask in the correct places for support: https://github.com/goauthentik/authentik/discussions and https://github.com/caddyserver/caddy/issues

I've been searching around for a while now, and struggling with getting Authentik setup on my NAS. I'd like to deploy via Portainer, but getting lost in the documentation just to deploy.

Personally I went with Keycloak, because it's fairly well documented and also has Docker images available: https://www.keycloak.org/getting-started/getting-started-doc... although the fact that they want you to create an "optimized" image yourself and have a long build/setup process on startup instead is slightly annoying: https://www.keycloak.org/server/containers

Regardless, with something like mod_auth_openidc or another Relying Party implementation, all of the sudden authn/authz becomes easier to manage (you can literally get user information including roles in headers that are passed from your gateway/relying party to apps behind the reverse proxy), regardless of what you have actually running in your APIs: https://github.com/OpenIDC/mod_auth_openidc (there are other options, of course, but I went with that because I already use mod_md).

It's actually cool that there are plentiful options in the space, since OIDC is pretty complex in of itself and attempts at creating something pleasant to actually use are always welcome, I've also heard good things about Authentik: https://goauthentik.io/

Hello ! I am hosting a server under NixOS with multiple services, and to simply the identity management, I use authentik (https://goauthentik.io/) which can be compared to keycloak. Everything works fine until I try to enable mastodon to host an instance : authentik returns an error 400 and nothing changes this but disabling mastodon. Does anyone have an idea of what could be the cause of this ?

For Authentik, it looks like they are not interested to write how to configure HAProxy with it https://github.com/goauthentik/authentik/issues/5768