Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A detailed guide to SSO on Kubernetes

talkingquickly.co.uk

Post reply on HN
Print view View original

11–20 of 33 posts

Re: A detailed guide to SSO on Kubernetes

#11

Post by 3np »

varispeed wrote: post #5

My dream is to one day create an SSO solution for companies. I've been doing research for a time being, but I am worried that I wouldn't find any clients, because who would trust an SSO created by one guy in his basement? I think the first step to overcome that would be having a completely Open Source solution, but how to avoid other companies grabbing it and selling as their own? Or do you think it is better to deve…

The current business players in the space all range across the spectrum of closed blackbox Saas (Auth0) to open core / open source (HC Boundary, arguably)

Before you can answer that - how do you differentiate from the existing competition? What's your target customer?

Re: A detailed guide to SSO on Kubernetes

#12

Post by streetcat1 »

gsjjsjsbsb wrote: post #2

Does anybody have a good, comprehensive guide to Keycloak? I looked at it a while back and it seemed like a giant web UI with a million poorly documented knobs, but I keep seeing people who claim to be using it. I've used Auth0, Okta, Dex, and ORY and none of them seemed quite as incomprehensible

I think that keycloak is based on JBoss, which is GPL? Hence I am not sure that you want it for commercial projects. But I might be wrong.

Re: A detailed guide to SSO on Kubernetes

#13

Post by nurgasemetey »

streetcat1 wrote: post #12
gsjjsjsbsb wrote: post #2

Does anybody have a good, comprehensive guide to Keycloak? I looked at it a while back and it seemed like a giant web UI with a million poorly documented knobs, but I keep seeing people who claim to be using it. I've used Auth0, Okta, Dex, and ORY and none of them seemed quite as incomprehensible

I think that keycloak is based on JBoss, which is GPL? Hence I am not sure that you want it for commercial projects. But I might be wrong.

There are many commercial projects using Keycloak as I know. Are they in danger?

Re: A detailed guide to SSO on Kubernetes

#14

Post by candiddevmike »

varispeed wrote: post #5

My dream is to one day create an SSO solution for companies. I've been doing research for a time being, but I am worried that I wouldn't find any clients, because who would trust an SSO created by one guy in his basement? I think the first step to overcome that would be having a completely Open Source solution, but how to avoid other companies grabbing it and selling as their own? Or do you think it is better to deve…

Would love to hear more about this, I've got a couple of design diagrams and thoughts on my "ideal SSO setup". My contact info is in my profile.

Re: A detailed guide to SSO on Kubernetes

#15

Post by traverseda »

varispeed wrote: post #5

My dream is to one day create an SSO solution for companies. I've been doing research for a time being, but I am worried that I wouldn't find any clients, because who would trust an SSO created by one guy in his basement? I think the first step to overcome that would be having a completely Open Source solution, but how to avoid other companies grabbing it and selling as their own? Or do you think it is better to deve…

The smaller scale homelab/selfhosting people really need a better solution. I think open source developers do as well.

What we really need is a small easy to set up solution that provides a clear way for us to integrate our app into it.

My ideal would be something that

* Supports ldap and OIDC

* Can be deployed to docker using one compose file

* Only needs to support hundreds of users (keep it simple, easy to deploy, and able to run on a raspberry pi)

* Provides basic user management, I want to be able to put users into groups and (if the app supports it) use those groups for in-app ACL.

If that service worked well in my homelab (a single-pc docker swarm that runs a few private web services like jellyfin) I'd very likely end up deploying it on my employers infrastructure. My employer is a small business with maybe ~30 users.

I'm not sure how to convert something like that into sales though. Still, starting with an open-source solution that solves problems for the little guys often has a "trickle up" effect.

Right now I'm looking towards https://github.com/sonicnkt/glauth-ui/ to solve that problem, but it's definitely not anywhere near there yet.

Re: A detailed guide to SSO on Kubernetes

#16

Post by jeroenhd »

nurgasemetey wrote: post #13
streetcat1 wrote: post #12

Earlier quoted context omitted.

I think that keycloak is based on JBoss, which is GPL? Hence I am not sure that you want it for commercial projects. But I might be wrong.

There are many commercial projects using Keycloak as I know. Are they in danger?

Edit: Keycloak is licensed with the Apache 2.0 license, so none of this is relevant for Keycloak.

GPL is only a problem if you import or change the source code. If you just run it in the backend, as a service, you're most likely fine.

If you customise Keycloak through code, you're probably in GPL violation territory. With the customisability of Keycloak, I doubt that this is something many projects will ever run into.

Re: A detailed guide to SSO on Kubernetes

#17

Post by jabiko »

streetcat1 wrote: post #12
gsjjsjsbsb wrote: post #2

Does anybody have a good, comprehensive guide to Keycloak? I looked at it a while back and it seemed like a giant web UI with a million poorly documented knobs, but I keep seeing people who claim to be using it. I've used Auth0, Okta, Dex, and ORY and none of them seemed quite as incomprehensible

I think that keycloak is based on JBoss, which is GPL? Hence I am not sure that you want it for commercial projects. But I might be wrong.

Keycloak is licensed under Apache 2.0

Re: A detailed guide to SSO on Kubernetes

#18

Post by Hitton »

varispeed wrote: post #5

My dream is to one day create an SSO solution for companies. I've been doing research for a time being, but I am worried that I wouldn't find any clients, because who would trust an SSO created by one guy in his basement? I think the first step to overcome that would be having a completely Open Source solution, but how to avoid other companies grabbing it and selling as their own? Or do you think it is better to deve…

>because who would trust an SSO created by one guy in his basement

You don't have to tell everyone that you are one person company operating from basement. Why not use phrases like "our company", "our clients", have different email addresses like support@, sales@, hr@ subtly insinuating there are more of you, use picture from photobank when listing address of your company's headquarters(basement) etc.. You won't be first nor last person doing this.

And Open Source/Proprietary doesn't need to be either/or problem. You can dual license it as AGPL/Proprietary and make contributors sign CLA.

Re: A detailed guide to SSO on Kubernetes

#20

Post by pricechild »

jeroenhd wrote: post #16
nurgasemetey wrote: post #13

Earlier quoted context omitted.

There are many commercial projects using Keycloak as I know. Are they in danger?

Edit: Keycloak is licensed with the Apache 2.0 license, so none of this is relevant for Keycloak. GPL is only a problem if you import or change the source code. If you just run it in the backend, as a service, you're most likely fine. If you customise Keycloak through code, you're probably in GPL violation territory. With the customisability of Keycloak, I doubt that this is something many projects will ever run into…

I don't think this is true.

The GPL allows you to copy & modify code for your own desires very generously.

The limitations you fear apply if you distribute the code (in source or other forms) or modifications yourself.

Post reply on HN