I haven't had a deep dive into OpenID Connect Client initiated Backchannel
Authentication Flow yet, but it raises a question if we should support
both, or just one of these specifications as they seem to be targetting
mostly the same use-cases.
On Tue, 19 Mar 2019 at 13:08, Stian Thorgersen <sthorger(a)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(a)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(a)nri.co.jp
>
>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>