A detailed guide to SSO on Kubernetes
talkingquickly.co.uk
A detailed guide to SSO on Kubernetes
1–10 of 33 posts
Re: A detailed guide to SSO on Kubernetes
#2Does 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
Re: A detailed guide to SSO on Kubernetes
#3Does 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
The thing with Keycloak is: when you know what you are looking for, it's all self descriptive. Server administration documentation is awesome: https://www.keycloak.org/docs/latest/server_admin/index.html
I've written more about Authorization Services: https://gruchalski.com/posts/2020-09-05-introduction-to-keyc...
And can recommend these resources: https://www.janua.fr/tag/technical-blog/
Re: A detailed guide to SSO on Kubernetes
#4Does 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
Keycloak is designed to be super flexible and support almost every combination of auth methods out there. A lot of companies don't need this kind of complexity though, which is where something like Dex may be more appropriate--it's quite a bit simpler.
Re: A detailed guide to SSO on Kubernetes
#5My 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 develop it anyway and then worry about customers later?
Re: A detailed guide to SSO on Kubernetes
#6I've leveraged nginx-ingress's OAuth annotations to great success: https://kubernetes.github.io/ingress-nginx/examples/auth/oau...
Re: A detailed guide to SSO on Kubernetes
#7I've leveraged nginx-ingress's OAuth annotations to great success: https://kubernetes.github.io/ingress-nginx/examples/auth/oau...
Yup agree, that's exactly what's being used here, along with some tweaks to make it easier to do things like passing the auth JWT's back to the underlying app etc
Re: A detailed guide to SSO on Kubernetes
#8My 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…
There is already Keycloak and various vendor solutions. I feel you'll struggle to break through.
Re: A detailed guide to SSO on Kubernetes
#9My 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?
If you think you've got a good idea and a unique proposition - and your technical skills are up to scratch - then don't worry about starting out from your basement.
Have a look at Thawte Consulting - a certificate authority founded by Mark Shuttleworth in his parents' garage - which he later sold to Verisign for $575 million dollars:
https://en.wikipedia.org/wiki/Thawte
Starting a "high trust" business from one's basement is perfectly fine.
That being said, a far more important point is testing / validating the existence of an actual market for your product.
Whether you build your solution out of your basement or a lavish penthouse office is irrelevant.
The best and brightest team working out of swank office space will still fail if the market for their product doesn't exist.
Hope that helps :-)
Re: A detailed guide to SSO on Kubernetes
#10My 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…
Personally, I think the answer has to come from your customers. If the pain you're solving is great enough that they want it, but the only showstopper is future-proofing, then you might be able to work with them to find a solution.
It might be a case that you deploy into their infrastructure and give them a licence to use the source code should you shut down.