[keycloak-dev] Community extensions and examples

Liam Maruff liam.maruff at gmail.com
Thu Jun 29 02:15:58 EDT 2017

This is a worthwhile discussion, and one I've been thinking about starting.

I'm working with Keycloak on two different projects at the moment. While
doing so, I've written mechanisms for:

1. A REST based storage provider
2. A client-certificate authentication provider, where SSL is terminated at
a reverse proxy and the certificate is provided in a user header. This
differs from the X/509 Validate Username Provider in that it supports an
'optional' mode whereby a user can still login without having provided a
certificate, but is not MFA'ed, and is prompted using a 'required action'.
3. A backup-codes mechanism (integrated with a lot of LDAP stuff that's
organisation specific, but my design have been well received by end users)
4. extensions to the profile application for (2) and (3)

Now, the problem is, in addition to my usual work, I don't have the time to
get involved in the Keycloak project and re-engineer these components so
that they are suitable for inclusion in the main project. However, feedback
from within my organisation and from our customers has led me to conclude
that my ideas are sound.

With a little work from an experienced contributor, I suspect that part of
these providers could be included in the main project. It would be great to
have some place to put these up where they could be given some exposure
and, potentially, scheduled for further work and inclusion by those of you
close to the project.



On Wed, Jun 28, 2017 at 4:34 PM, Stian Thorgersen <sthorger at redhat.com>

> At times there are extensions and examples that we don't want to include in
> the main repository. This could be for several reasons, including:
> * We don't have the resources to maintain and support it
> * We don't believe it's generic enough
> * Examples that are to complex
> However, these can still be useful for some people. So I'm thinking about
> how we can provide community maintained extensions and examples.
> A very simple idea would be to add a page on our website that links to the
> relevant repository and documentation. To contribute you would setup your
> own Github repository, documentation and also a download if you want. Then
> you'd send a PR to the website to add your extension or example.
> Thoughts?
> _______________________________________________
> 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