I want to refactor the Builders I wrote so they can be user consumable.
What I want to have is a SAML SPI in which the SPI interface is passed
a Builder. Then the SPI plugin can modify the document however they
want. We'll need something similar for OIDC.
On 2/16/2015 6:48 AM, Pedro Igor Silva wrote:
----- Original Message -----
> From: "Bill Burke" <bburke(a)redhat.com>
> To: keycloak-dev(a)lists.jboss.org
> Sent: Sunday, February 15, 2015 2:38:08 PM
> Subject: [keycloak-dev] From 1.2->2.0
>
> I think we still have a few major features to implement for 1.2 and
> maybe 1.3. After this I'd like to focus on Keycloak 2.0 things like:
>
> * Improving and nailing down our SPIs
> * Splitting up code into private and public models so we can restrict
> what APIs/SPIs we want to commercially support
> * Pulling in and refactoring PL Federation
I've an issue [1] in the SAML parsers that needs a fix. I don't know what are
your plans for this, but I think we can start moving PL SAML types and parsers to KC ? Do
you want/need a refactoring for them ?
Or the refactoring you always talk about is around the SAML processing logic ? Such as
handlers, etc ...
[1]
https://issues.jboss.org/browse/KEYCLOAK-883
> * Consolidating and improving our admin console UI
>
> Really starting improving the core of Keycloak knowing that Keycloak 2.0
> is what we're going to be supporting commercially for years and years
> going forward.
> --
> 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
>
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com