- I’m new to #Authentik - I’ve just spun up a test instance and tried to connect my first application (#Postiz) but I’m kind of stuck.

I’ve installed both Postiz and Authentik using Docker Compose - as provided by the relevant apps.

As far as #Authentik goes it looks like its approving authentication requests (its showing successes in the GUI) but the application just returns to the login screen without progressing.

One thing that I found was that within the configuration of the Application and Provider one URL provided by Authentik is the /application/o/postiz/.well-known/openid-configuration which lists several URLs used by the application - one is /application/o/authorize/ but unlike all the others this returns a 404 error when I try to load it via the browser.

I am struggling to work out if - this URL should 404 should occur and also how to diagnose what the problem is.

I’ve popped messages in their relevant Discord forums but any ideas or input would be greatly appreciated - I’m figuring getting Authentik is going to be key to getting other applications going.

    • Starfighter@discuss.tchncs.deEnglish
      1·
      9 hours ago

      If you don’t mind me asking, what made you go with VoidAuth vs Authelia or something else entirely?

      I’m in a similar boat as OP and while VoidAuth looks very promising I’m put off a little by the young age and size of the project.

      • CHOPSTEEQ@lemmy.mlEnglish
        3·
        7 hours ago

        I tried literally every mature option and they all were ridiculously complicated or just straight didn’t work for me. Voidauth just works. One container. Does everything you need to offer SSO for your users, and secures apps that don’t use SSO just as easily with proxyauth.