[keycloak-dev] Implementation of OAuth 2.0 Device Authorization Grant

Pedro Igor Silva psilva at redhat.com
Tue Mar 19 08:29:16 EDT 2019


This can also be useful in the future if we decide to improve our IoT story
and a future ACE [1] implementation.

[1] https://tools.ietf.org/html/draft-ietf-ace-oauth-authz-22

On Tue, Mar 19, 2019 at 9:18 AM Stian Thorgersen <sthorger at redhat.com>
wrote:

> In general I would welcome a contribution for this specification. I would
> suggest starting with a design proposal [1] so we can discuss how it would
> look like for Keycloak. As we don't have any plans on the immediate roadmap
> for this a contribution would have to be a complete implementation of the
> specification, include sufficient level of documentation and testing.
>
> [1] https://github.com/keycloak/keycloak-community/tree/master/design
>
> On Tue, 19 Mar 2019 at 10:59, Hiroyuki Wada <h2-wada at nri.co.jp> wrote:
>
> > Hello,
> >
> > I'm interested in implementing OAuth 2.0 Device Authorization Grant [1]
> > into Keycloak.
> > I found KEYCLOAK-7675 as the feature request, is there anyone already
> > working? Also, is the pull request welcome?
> >
> > The spec is still draft, but many IdPs such as Goolgle, MS, Facebook,
> > Salesforce have already implemented it.
> > I believe supporting the spec will further extend the Keycloak use-case.
> >
> > - [1] https://tools.ietf.org/html/draft-ietf-oauth-device-flow-15
> >
> > Best regards,
> >
> > --
> > Hiroyuki Wada (@wadahiro)
> > Nomura Research Institute, Ltd.
> > h2-wada at nri.co.jp
> >
> >
> > _______________________________________________
> > keycloak-dev mailing list
> > keycloak-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/keycloak-dev
> >
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev
>


More information about the keycloak-dev mailing list