I moved away from authentik for void-auth: https://github.com/voidauth/voidauth

Life is so much better...

Any particular reason for Authentik? I found it very resource hungry and slow. PocketId on the other hand, is super lightweight and fast

I have self hosted for years using Authentik and have 50 + services. Postiz has been one of the most challenging to spin up and maintain. The documentation is not up to date, the software is constantly changing and I had to tweak lots to get it to work. Even now, it seems to crash after a few days and haven't had the chance to investigate. All these posts I set up didn't go through and now if I turn it back on, it'll release them all in one go before I can get in to stop it, or have to revert to a fresh install...

The vast majority of services and not like this so don't get disheartened! Try some other ones first them come back to this when more experienced. I recommend Bento PDF, ConvertX, outline wiki, vikunja and immich (if you have the storage space).

At first, try to stick to software on Authentik's guides (https://integrations.goauthentik.io/). Once you do a few OIDC and forward proxy services you'll get the hang of it.

When I get a chance I'll share my docker compose SSO settings and authentik redirect uri that worked for me with the caveat that the software crashes for some reason.

https://integrations.goauthentik.io/applications/

https://youtube.com/playlist?list=PLH73rprBo7vSkDq-hAuXOoXx2es-1ExOP

Everything you need is there. Authentik is fantastic.

If you are getting the authentik login screen and being redirected, it's either the redirect url not being right or the app itself not being configured for authentik.

Source: my limited knowledge with authentik and other apps.

So an update. It turns out that all the issues were actually to do with Postiz rather than Authentic. - I tried installing a few other apps and linking them to Authentik but I ran into a few issues. Then I took Postiz and tried turning off the Atuthentik authentication and then just getting it to work with native user accounts. This initially didn't work - it turned out that there were a few issues.1. The startup procedure for Poztiz actually left the backend API service not running properly. I had to run the docker compose, get all the other services running and then stop the postiz container specifically wait a bit more and then restart just that container. That got the API service running.2. Because I was just running it internally I didn't have SSL certificates configured and was just using http - consequently I had to introduce NOT_SECURED: "true" into the environment section of the Postiz service in the compose file and then repeat the process above. This resolved a silent error in my browser where cookies used to manage the authenticated browser session were discarded because I wasn't using SSL.So success at least getting Postiz running. I am now going to step back, reconfigure it for Authentic retry.I am going to guess that these issues might be relevant if you are running Postiz behind a reverse proxy (I'm not sure if this is being done with the docker compose set-up). I possibly also need to look at how much memory and CPU I have on my test VM.I've posted similar details in Postiz Discord. If anyone else is using #Postiz and would like to exchange notes - please do drop me a mention. Always good to have other people to talk to about these things and share notes.