Problems setting up SSO with Authelia on a Caddy Server

[wooge]

I'm not sure if I need to get into the specifics of how I use Authelia and Caddy but when it came to using "http-headers" as the authentication backend on my LMS, I ran into some problems.

I started by adjusting the setting in my lms.conf, deleting the lms.db file, deleting the LMS docker image/container and ensuring that X-Forwarded-User is in fact added as a header by the authentication redirect.

When attempting to access the address of LMS, I get redirected to Authelia's login page in which I sign in and then get brought back to LMS. That's as expected.
But when I get back, I am greeted with LMS' "Create administrator account"-page which I thought would be skipped as I have signed in through the SSO.

Am I missing a setting in lms.conf perhaps?
Thanks for hopefully helping out and thank you for developing a great music server 😄

[wooge]

Oh! Nevermind I'm stupid 😛
Turned out I hadn't specified the path to my custom configuration when launching the server...
If it helps anyone else, I simply added a command attribute to the service in my docker compose.
command: ["/etc/lms-custom.conf"]

[epoupon]

Glad you figured it out!

[wooge]

Now that we're on the topic, @epoupon, is there a way to make LMS' 'log out' send the user to a url that actually lets them log out?
Currently, when http-headers is the specified auth backend, 'log out' essentially just reloads the page and they are still signed in 🤔

[epoupon]

Ah, this is a good question.
In this mode, users are actually not logged in/out, no state is stored on lms side, as everything is done externally.
Maybe we could just hide the entry...

[wooge]

A fun solution is to reset the configured http-headers-login-field header and reload the page 😎 It would work in my setup but it's a bit hacky and I haven't thought through the implications