Right now, Hydra allows to connect to different providers by supplying a provider param to the authorize url: hydra/oauth2/auth?provider=dropbox&cliend_id=123&...
At this point in time, only Dropbox and Login are shipped but this is going to change with #33 . The Login provider acts as a fallback and basically redirects the user to a url and expects that endpoint to redirect the user back to hydra, providing a "login token" (you might already see the unintentional similarity to OpenID Connector) which the Login provider then validates and exchanges for an authorize code.
I have seen a similar approach at Auth0.com but I would really like to find a spec for this and implement it instead of shipping my own solution.
So here's the question: Is there a standard way to specify a (thirdparty) ID provider like Dropbox, Google or some other IdP? I would appreciate any help :)
Right now, Hydra allows to connect to different providers by supplying a provider param to the authorize url:
hydra/oauth2/auth?provider=dropbox&cliend_id=123&...At this point in time, only Dropbox and Login are shipped but this is going to change with #33 . The Login provider acts as a fallback and basically redirects the user to a url and expects that endpoint to redirect the user back to hydra, providing a "login token" (you might already see the unintentional similarity to OpenID Connector) which the Login provider then validates and exchanges for an authorize code.
I have seen a similar approach at Auth0.com but I would really like to find a spec for this and implement it instead of shipping my own solution.
So here's the question: Is there a standard way to specify a (thirdparty) ID provider like Dropbox, Google or some other IdP? I would appreciate any help :)