I’d like to do the same, but atm I use nginx to serve all the web interfaces… And keycloak support is either a plus subscription feature or made to work with hacky Lua scripts.
So for now it’s security through obscurity, I got a wildcard cert and the pages are accessed based on subdomain. So afaik nobody has a clue unless they start iterating common subdomain names. (At some point™️ I’m adding proper auth though)
just_another_person@lemmy.world 1 month ago
That’s really up to the software again. If you’re not technically inclined enough to run through the code, that’s fine, but you have to trust that other people are.
Go and search GitHub issues or this project by name for what you’re concerned about.
Authentication is also not security, btw. It’s just access. If you can be more specific about your concerns in your post, you may get more direct answers.
tofubl@discuss.tchncs.de 5 weeks ago
“authentication is not security,” can you elaborate on that?
Your statement doesn’t really overlap with my understanding of security, as “just access” seems critically relevant to how secure user data is, for example. Am I missing something?
just_another_person@lemmy.world 5 weeks ago
Authentication is simply identifying a user.
Authorization is securing access to assets.
You can find a lot of reading about this if the distinction is confusing.
tofubl@discuss.tchncs.de 5 weeks ago
Right, thanks.