Keycloak & Cloudron

[Sam_uk]

Frankly at this point I wouldn't bother. If you want an alternate SSO system I'd set it up on Elest.io

[jdaviescoates]

@Sam_uk why?

Wouldn't it be nice/ good to have it on Cloudron too?

Or are you just tired of waiting for that to happen?

Or are there reasons you'd use Elest.io over Cloudron even if you were starting afresh and it was on Cloudron? If so, what are those reasons?

Thanks!

[Sam_uk]

@jdaviescoates Every time it updates it loses it's email config, so users can't get password resets etc.

I've kind of given up hoping it will be fixed. It just works on Elest.io, it's worth $10/m to me to have reliability.

I accept this is an unofficial package, and that's just how it goes. If I didn't mind being locked into Cloudron it looks like the on-board OIDC works nicely now, but that didn't exist when I set it up & I'd prefer data portability.

[jdaviescoates]

@Sam_uk said in Keycloak & Cloudron:

@jdaviescoates Every time it updates it loses it's email config, so users can't get password resets etc.

I've kind of given up hoping it will be fixed. It just works on Elest.io, it's worth $10/m to me to have reliability.

I accept this is an unofficial package, and that's just how it goes. If I didn't mind being locked into Cloudron it looks like the on-board OIDC works nicely now, but that didn't exist when I set it up & I'd prefer data portability.

Fair enough. Although I guess it it were an official app you likely wouldn't have those issues.

I also read a post on there somewhere (which I've just spent ages trying but failing to find again) where someone was asking about details of Cloudron's OIDC implementation and features, and when I read it I thought of discussion I'd had with you and how it might be appropriate to not have Cloudron as the ultimate source of truth about users.

I'd love to understand more about to what extent having users primarily on Cloudron locks you into using Cloudron