There's a few more key features that we'll need asap:
* TOTP SPI - including support for admins to register hardware tokens with users
* Internationalization - login and account, admin can come later (if at all?)
* Clustering
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Monday, 1 September, 2014 7:20:43 PM
Subject: Re: [keycloak-dev] Federating AWS Login at Netflix with OneLogin
All this integration needs to be the focus for 1.1. NO more cool
features. Time to do the nasty work.
On 9/1/2014 9:43 AM, Stian Thorgersen wrote:
> Interesting article on using SAML with AWS:
>
>
http://www.onelogin.com/blog/amazon-aws-iam-identity-management-saml-fede...
>
> Made me think that when we add SAML we should make sure it works with some
> external cloud services. Same goes for OpenID Connect, we need to make
> sure we're compliant enough that it works with 3rd party services and
> client libraries.
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>
--
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