Show HN: Obligator – An OpenID Connect server for self-hosters
1–10 of 134 posts
Re: Show HN: Obligator – An OpenID Connect server for self-hosters
#2[deleted]
Re: Show HN: Obligator – An OpenID Connect server for self-hosters
#3Ohh, looks extremely promising, I've been after something with a bit more flexibility than Dex while not being Keycloak/Java etc, an LDAP backend would be awesome as well though (another thing thats lacking is a simple ldap server, perhaps with sql as db, openldap is excessive and glauth isn't there)
Re: Show HN: Obligator – An OpenID Connect server for self-hosters
#4Ohh, looks extremely promising, I've been after something with a bit more flexibility than Dex while not being Keycloak/Java etc, an LDAP backend would be awesome as well though (another thing thats lacking is a simple ldap server, perhaps with sql as db, openldap is excessive and glauth isn't there)
Have you had a look at Authentik? It might fit your needs.
Re: Show HN: Obligator – An OpenID Connect server for self-hosters
#5Amazing. I was looking for something like this about a year ago. Looks very promising and may be a good drop in replacement for some simple Auth0 use-cases as well as homelab setups.
I was not able to get past „ redirect_uri must be on the same domain as client_id“. Maybe you can give an example of a valid client id for your demo instance.
Re: Show HN: Obligator – An OpenID Connect server for self-hosters
#6Amazing. I was looking for something like this about a year ago. Looks very promising and may be a good drop in replacement for some simple Auth0 use-cases as well as homelab setups. I was not able to get past „ redirect_uri must be on the same domain as client_id“. Maybe you can give an example of a valid client id for your demo instance.
According to the Readme, the client ID should be the domain of the client. So some site https://access.site.com would have the client ID https://access.site.com
Re: Show HN: Obligator – An OpenID Connect server for self-hosters
#7Amazing. I was looking for something like this about a year ago. Looks very promising and may be a good drop in replacement for some simple Auth0 use-cases as well as homelab setups. I was not able to get past „ redirect_uri must be on the same domain as client_id“. Maybe you can give an example of a valid client id for your demo instance.
I too found this hard to reason, but figured it out:
If you're demoing using https://openidconnect.net for example, set your Client ID to https://openidconnect.net
Likewise, your ClientID should match the url of the website you are using this to connect with.
This was mentioned in the GitHub readme too but didn't click until trying the demo
Re: Show HN: Obligator – An OpenID Connect server for self-hosters
#8Can someone explain which services this is supposed to be an IdP for? As far as I know, services need to have the OIDC service registered (ie I can't just auth with this to Google or whatever).
Re: Show HN: Obligator – An OpenID Connect server for self-hosters
#9Ohh, looks extremely promising, I've been after something with a bit more flexibility than Dex while not being Keycloak/Java etc, an LDAP backend would be awesome as well though (another thing thats lacking is a simple ldap server, perhaps with sql as db, openldap is excessive and glauth isn't there)
What's wrong with glauth? I forked it so I could build in the /etc/passwd support and it's been working great.
Re: Show HN: Obligator – An OpenID Connect server for self-hosters
#10Amazing. I was looking for something like this about a year ago. Looks very promising and may be a good drop in replacement for some simple Auth0 use-cases as well as homelab setups. I was not able to get past „ redirect_uri must be on the same domain as client_id“. Maybe you can give an example of a valid client id for your demo instance.
Sorry, this is indeed not very clear. Others already answered well, but if you look at the example[0] config you can see how you would use your own instance of obligator as a client to the instance running at lastlogin.io. This is a bit meta, but applies equally to any client application.