Authentication Configuration

[nebulon]

Unfortunately there is no smooth upgrade path from an app installed without user directory integration to start using it. Mostly this is because the user-mappings are hard to do in an automated way.

Currently, the only option is to install a fresh app instance with Cloudron user management and then migrate the data (database export/import...) and potentially do the user-mapping manually.

[kahrpatrick]

Alright, thank you for the explanation. I'll reinstall the app then.

[andreasdueren]

@nebulon I just spun up a new installation but OICD doesn't work. Says User not found

[fbartels]

@andreasdueren i don't know if this is the only way, but when I encountered this error message i manually created a user with the same username as my cloudron user. Afterwards i could use oidc for login.

[andreasdueren]

@fbartels That's a workaround I'd like to avoid and have people onboard automatically instead

[joseph]

@andreasdueren https://github.com/knadh/listmonk/issues/2119 . Listmonk does not have automatic user creation yet.

[andreasdueren]

@Joseph Oh I see it's an upstream issue. Apologies I thought there was something wrong with the current implementation.

[avatar1024]

Anyone know if there is there a way to customize the OIDC login button for Listmonk? Currently for me it says "Login with .org.uk" instead of my domain or organisation name which is rather unhelpful. Thanks!

[joseph]

@avatar1024 We reported this upstream at https://github.com/knadh/listmonk/issues/2211 . But the issue is that listmonk wants to just to take two dots before the URL . https://github.com/knadh/listmonk/blob/master/cmd/auth.go#L213 "Get the last two h for the root domain" .

Unfortunately, I think nothing can be done without fixing the code upstream.

[jdaviescoates]

@joseph said in Authentication Configuration:

But the issue is that listmonk wants to just to take two dots before the URL . https://github.com/knadh/listmonk/blob/master/cmd/auth.go#L213 "Get the last two h for the root domain" .

Unfortunately, I think nothing can be done without fixing the code upstream.

Given there are loads of TLD with .something.something that is a bizarre bit of code and is clearly a bug too, is there already an issue for that one as well?

[joseph]

@jdaviescoates oidc feature was fairly new , but I didn't find a issue about this specific issue.

[jdaviescoates]

@joseph I've just commented on that existing issue for now https://github.com/knadh/listmonk/issues/2211#issuecomment-2751989442

[jdaviescoates]

And they've replied:

Indeed. That's a glaring brain-fart on my part for sure. We can add a provision to specify a custom label for the OIDC provider button in the upcoming release.