Developer of VoidAuth here; if you decide to give it a try let me know if you run into any issues during setup, or have any feedback!

It is configured mostly through UI. The separation (in my opinion) is VoidAuth configuration happens mostly through environment variables and Client/Users/Domain configuration happens in the Web UI. You can try it out and switch if you like it and think the effort of switching is worth it

Well that is not good! It looks to be working for me on iOS and Windows Firefox (librefox), I don’t have a way to test on Android 😕 If you don’t mind opening a GitHub issue that would be helpful, and I will add some extra debug logging that may help narrow down the issue.

Thanks, I think I fixed it

I think technically you might actually not need https termination anymore, it was required when the session cookies were set secure manually but now they should be set automatically if the request protocol was https. You can give it a try just using http or self-signed certs, if you do let me know if it works!

You should be aware though that if you are not using https your password and other secrets will be transmitted unencrypted on that layer, so make sure that your setup is secured/encrypted in some other way like wireguard/vpn tunneling.

There is no direct feature comparison between VoidAuth and pocket-id (‘comparison is the thief of joy’ after all). At least one major difference is that pocket-id does not allow users to sign in with a password since passkey-only accounts are one of their design decisions, and VoidAuth does not support LDAP integration while pocket-id does. My main motivation in creating VoidAuth was to fill gaps in my own user experience while using SSO, previously I ran Authelia+LLDAP (which is still an excellent combo) but found the setup lacking in some common use-cases and devoid of an Admin Interface.

I am glad you like the interface and logo, it is inspired by my own black cat who right at this very moment is yelling for pets 😹

I would recommend checking out the Getting Started page in the docs, which I realize can be a lot! Once you have an initial instance running (you can always change environment variables later to suite your needs) and have logged in with the initial admin username and password that appear in the logs on first start, you can check out the Admin Guides section in the docs sidebar. There you should be able to see pages relating to OIDC Setup (including for specific apps) and other topics. If you set up OIDC on a new app that doesn’t yet have documentation, PRs with updates to the documentation are welcome! If you have any questions you can feel free to ask in the repo issues/discussions and I will try to help out 😊

You can try VoidAuth, it is kinda similar to Authelia+lldap. I am the developer and I created it because I wasn’t satisfied with Authelia’s user management. If you decide you want to try it and run into any issues or questions I will try to help :)

I will make an issue for adding SQLite support, it has been on my mind for the same reasons. I would say don’t let the Postgres requirement stop you from trying it out. Modern hardware really doesn’t mind having multiple containerized postgresdb instances running, it can be very lightweight when idle.

I do agree. I have been thinking about adding a SQLite option which should be somewhat easy since knex (the database package that VoidAuth uses) supports it. Before releasing that I would want to create some way to migrate your data from one database type to another. If you want to use VoidAuth feel free to make an issue for this!

My previous setup was with Authelia and lldap, and VoidAuth is heavily inspired by a combination of both. I think the advantages VoidAuth has are simple user management, supporting user registration/invitation, more branding customization, and a better end-user UI (imo).

There are other great selfhosted auth solutions such as Authelia and lldap, and also Authentik, Keycloak, pocket-id, and Rauthy. I would encourage anyone looking for a selfhosted auth solution to shop around!