Keycloak & Cloudron

[doodlemania2]

Been following Keycloak for a while but still have meta question - why is this valuable for Cloudron? Isn't CR moving over to a similar auth mechanism? The nerd in me wants to deploy this, but not sure what it gives me beyond what's already provided by CR?

[luckow]

From a technical perspective: Since Cloudron - the platform - is capable of being an OIDC provider, there is no need for Keycloak on Cloudron. From a documentation and integration perspective, Keycloak is widely used in the documentation of various FOSS and proprietary software.
If Cloudron - the company - is able to provide more documentation and integration guidance (perhaps with the help of the community), the gap between Keycloak and Cloudron may be smaller in the future.
From an IAM perspective, I have no idea if Cloudron - the platform and the company - is ready to support more enterprise features.
IMHO: if you are happy with Cloudron's OIDC features, you are well served by Cloudron and don't need any more features from Keycloak.
IMHO: Having Keycloak in a private repo to have it as an app on Cloudron is a quick way to have a development environment for your software development. In this case: Keycloak is just another app on Cloudron among the other 100+ apps to fulfill your needs in projects or your personal digital life.

[BrutalBirdie]

Do we have some Keycloak experts here?
Got some question that need answers that my searches could not.

[BrutalBirdie]

just as a note.
I am using the Keycloak app now in production soooooooo if something breaks on updates I will know it first.

[Sam_uk]

Has anyone successfully applied a theme to their keycloak instance on Cloudron? I've tried the folder & jar approaches without success so far. They don't show up in the Keycloak webui

[BrutalBirdie]

@Sam_uk Yes we did and let me tell you. It's a pain.
I can try to get my sister on here, she did the theming for one of our keycloaks on Cloudron and cursed a lot while doing that

[Sam_uk]

That would be great, thanks. I've done the theme bit, it works on my non-Cloudron installs. The Cloudron instance just seems to ignore the files though.

[Sam_uk]

Do you think Keycloak will ever be added as an official app here? I'm considering just moving my instance to alternative hosting.

[BrutalBirdie]

@Sam_uk
Did you set the following in /app/data/conf/keycloak.conf?

spi-theme-static-max-age = -1
spi-theme-cache-themes = false
spi-theme-cache-templates = false

[girish]

@Sam_uk out of curiousity did elest.io not work out? I thought you already moved keycloak there per your earlier comment?

[Sam_uk]

I moved one to Elest.io and that ones working well. I can update the themes on that one. I'm considering moving a second instance across.

[Sam_uk]

I didn't have those settings @BrutalBirdie but have now added them and restarted and I'm still not seeing them in the keycloak webui

[adisonverlice2]

wait, so how do I use this with 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