- 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.
nope, https only. Because pocket id uses web authn which requires encryption
@devaly Ah ok … it looks interesting… I might need to push on with Authentik in the meantime just till I get more of an idea - It might also prove useful when I need to link to LDAP and Azure AD
Pocket-id also supports ldap sync https://pocket-id.org/docs/configuration/ldap
I tried Authentik then moved to Authelia and then to pocket-id. I found the first two unnecessarily complicated for selfhosting unless you want to specifically learn them.
Setting up https is quite straightforward, especially with caddy.