How do you integrate this with your existing API? Do you need to proxy requests through Hydra or do you just need to read and trust Hydra-signed tokens on every request? Is there any overlap with https://getkong.org/ ?
You have to query token validation endpoint to have your reference token validated. That's how oauth2 works. With OpenId connect you get JWT which can be validated without a call to the identity provider.
Show HN: Run your own OAuth2/OpenID Connect provider
31–40 of 52 posts
Re: Show HN: Run your own OAuth2/OpenID Connect provider
#32Earlier quoted context omitted.
You have to query token validation endpoint to have your reference token validated. That's how oauth2 works. With OpenId connect you get JWT which can be validated without a call to the identity provider.
One thing I've not quite got my head around with JWT is not authenticating tokens with the server on each request - am I really just meant to assume a token is trusted until it's expiry time? What if a user signs out all their sessions in the meantime, or an employee is fired and needs access revoking? As far as I can tell I do just have to use short-lived tokens and renew them frequently but that comes with its own…
Re: Show HN: Run your own OAuth2/OpenID Connect provider
#33Earlier quoted context omitted.
You have to query token validation endpoint to have your reference token validated. That's how oauth2 works. With OpenId connect you get JWT which can be validated without a call to the identity provider.
One thing I've not quite got my head around with JWT is not authenticating tokens with the server on each request - am I really just meant to assume a token is trusted until it's expiry time? What if a user signs out all their sessions in the meantime, or an employee is fired and needs access revoking? As far as I can tell I do just have to use short-lived tokens and renew them frequently but that comes with its own…
Re: Show HN: Run your own OAuth2/OpenID Connect provider
#34Nice! Lowering barriers to the use of technologies like these is important. Would anyone else be interested in hosting Mozilla Persona? https://developer.mozilla.org/en-US/Persona
Check out Let's Auth: https://github.com/letsauth/letsauth.github.io It's a successor to Mozilla Persona in development. Details in the readme and on freenode #letsauth (mirrored to gitter.im/letsauth/letsauth).
Re: Show HN: Run your own OAuth2/OpenID Connect provider
#35Earlier quoted context omitted.
Check out Let's Auth: https://github.com/letsauth/letsauth.github.io It's a successor to Mozilla Persona in development. Details in the readme and on freenode #letsauth (mirrored to gitter.im/letsauth/letsauth).
why is it written in python? why not something that compiles and runs well on all platforms?
> Let's Auth 1.0 will ship as a single, statically compiled binary. Pre-1.0, we will use a variety of dynamic languages for prototyping.
Re: Show HN: Run your own OAuth2/OpenID Connect provider
#36Earlier quoted context omitted.
why is it written in python? why not something that compiles and runs well on all platforms?
From the readme: > Let's Auth 1.0 will ship as a single, statically compiled binary. Pre-1.0, we will use a variety of dynamic languages for prototyping.
Re: Show HN: Run your own OAuth2/OpenID Connect provider
#37I know it's in the title but I don't see any OpenID capabilities here. Looks like Oauth2 spec implementation. Am i missing something?
Re: Show HN: Run your own OAuth2/OpenID Connect provider
#38Would this or coreos/dex replace something like Auth0?
Re: Show HN: Run your own OAuth2/OpenID Connect provider
#39Re: Show HN: Run your own OAuth2/OpenID Connect provider
#40I know it's in the title but I don't see any OpenID capabilities here. Looks like Oauth2 spec implementation. Am i missing something?
* http://openid.net/specs/openid-connect-core-1_0.html * http://openid.net/connect/faq/