Show HN: Keratin AuthN – Accounts and Auth Microservice in Go
1–10 of 57 posts
Re: Show HN: Keratin AuthN – Accounts and Auth Microservice in Go
#2Re: Show HN: Keratin AuthN – Accounts and Auth Microservice in Go
#3Re: Show HN: Keratin AuthN – Accounts and Auth Microservice in Go
#4Re: Show HN: Keratin AuthN – Accounts and Auth Microservice in Go
#5How does it compare to Hydra/Dex? What I'm missing is a page that tells me where it sits in the ecosystem. A versus page if you will.
Re: Show HN: Keratin AuthN – Accounts and Auth Microservice in Go
#6How does it compare to Hydra/Dex? What I'm missing is a page that tells me where it sits in the ecosystem. A versus page if you will.
"Dex is NOT a user-management system, but acts as a portal to other identity providers through "connectors." This lets dex defer authentication to LDAP servers, SAML providers, or established identity providers like GitHub, Google, and Active Directory."
It seems like AuthN IS a user management system. So that's a big difference right there.
Re: Show HN: Keratin AuthN – Accounts and Auth Microservice in Go
#7How does it compare to Hydra/Dex? What I'm missing is a page that tells me where it sits in the ecosystem. A versus page if you will.
I'd love to fill that in! If anyone would like a comparison, please add links in this thread and I'll reply. Later, I can collect it into a published page.
Re: Show HN: Keratin AuthN – Accounts and Auth Microservice in Go
#8How does it compare to Hydra/Dex? What I'm missing is a page that tells me where it sits in the ecosystem. A versus page if you will.
I'd love to fill that in! If anyone would like a comparison, please add links in this thread and I'll reply. Later, I can collect it into a published page.
I've just started dabbling on a small project and would be interested to understand how features overlap and differences in license/distribution model.
Re: Show HN: Keratin AuthN – Accounts and Auth Microservice in Go
#9Is SAML supported and if not is it planned in the near future ?
Re: Show HN: Keratin AuthN – Accounts and Auth Microservice in Go
#10We evaluated Traefik and Kong. Decision was for Kong, since we need more features like auth, logging, rate limit.