3 ms·
Amazing. 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 w
by kekub 3y ago
Amazing. 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.
- jackson1442 3y agoAccording to the Readme, the client ID should be the domain of the client. So some site https://access.site.com https://access.site.com would have the client ID https://access.site.com https://access.site.com
- camsjams 3y agoI too found this hard to reason, but figured it out: If you're demoing using https://openidconnect.net https://openidconnect.net for example, set your Client ID to https://openidconnect.net 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
- apitman 3y agoSorry, 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. [0]: https://github.com/anderspitman/obligator#running-it https://github.com/anderspitman/obligator#running-it