Re: [keycloak-dev] Features for 1.1
I'm happy with that ordering, although I'd say Open ID Connect interoperability
should be amongst the top 3.
Also, I was wondering if we should base our adapters on existing OAuth2/OpenID Connect
adapters instead of writing them from scratch?
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Tuesday, 2 September, 2014 5:36:34 PM
Subject: Re: [keycloak-dev] Features for 1.1
Forgot one.
On 9/2/2014 11:34 AM, Bill Burke wrote:
> I put them in my opinion of priority order
>
> * Clustering
> * SAML
> * Uberfire Integration (BRMS)
> * Fuse FSW
> * JIRA Integration (for potential sso.jboss.org deployment).
> * SPNEGO Kerberos, so we can integration with OpenIPA (also an
> sso.jboss.org deployment requirement too) .
> * Open ID Connect interoperability
> * Tomcat Adapter
> * Jetty Adapter
> * Pure servlet adapter
> * Node.js Adapter
> * Internationalization
* Improved claim support. Custom claim definition and entry.
> * TOTP improvements - we need a SPI to be able to add more multifactor
> authentication mechanisms, as well as support for admins to register
> totp tokens on behalf of users (hardware tokens)
> * IP filtering, fail2ban features.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev