On 9/17/2014 3:07 AM, Stian Thorgersen wrote:
----- Original Message -----
> From: "Bill Burke" <bburke(a)redhat.com>
> To: "Stian Thorgersen" <stian(a)redhat.com>
> Cc: keycloak-dev(a)lists.jboss.org
> Sent: Tuesday, 16 September, 2014 3:54:50 PM
> Subject: Re: [keycloak-dev] Adapters
>
>
>
> On 9/16/2014 9:15 AM, Stian Thorgersen wrote:
>>
>>
>> ----- Original Message -----
>>> From: "Bill Burke" <bburke(a)redhat.com>
>>> To: "Stian Thorgersen" <stian(a)redhat.com>
>>> Cc: keycloak-dev(a)lists.jboss.org
>>> Sent: Tuesday, 16 September, 2014 3:10:20 PM
>>> Subject: Re: [keycloak-dev] Adapters
>>>
>>> I disagree. We need to expand our adapters everywhere. Tomcat, Jetty,
>>> node.js, Rails, etc. Pure servlet, pure Java, pure openid connect
>>> libraries are only a fallback plan.
>>
>> Who is going to implement and maintain all those adapters? I just can't see
>> us having enough man-power to do that. Especially if we start venturing
>> into non-java land.
>>
>
> You're starting to sound like a whiny product manager instead of
> somebody that wants a successful keycloak project. :)
You're wrong, I'm a whiny developer ;)
I give in, but we'll have to automate testing of all these adapters. I'm going to
sink into depression if I have to manually test all of this for every release...
Hey, I feel your pain. I'm already manually testing on Chrome, FF, and
IE, Wildfly and EAP 6.3 prior to releasing. I"m not worried about the
Java stuff. Our Wildfly adapter is already integrated into our
testsuite. Really any Java-based adapter should be integratable with
our testsuite.
I might need to brush up on these specs, and now I'm also going
to have to read about SAML
Hey, at least you're only reading about SAML. I actually have to
integrate with it. :(
Bill
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com