From: "Marek Posolda" <mposolda(a)redhat.com>
To: "Stian Thorgersen" <stian(a)redhat.com>, "Stan Silvert"
<ssilvert(a)redhat.com>
Cc: keycloak-dev(a)lists.jboss.org
Sent: Thursday, 4 December, 2014 2:12:45 PM
Subject: Re: [keycloak-dev] AS7 subsystem problems Re: release? Stan?
On 4.12.2014 13:48, Stian Thorgersen wrote:
>
> ----- Original Message -----
>> From: "Stan Silvert" <ssilvert(a)redhat.com>
>> To: "Stian Thorgersen" <stian(a)redhat.com>
>> Cc: keycloak-dev(a)lists.jboss.org
>> Sent: Thursday, 4 December, 2014 1:39:09 PM
>> Subject: Re: [keycloak-dev] AS7 subsystem problems Re: release? Stan?
>>
>> On 12/4/2014 7:32 AM, Stian Thorgersen wrote:
>>> ----- Original Message -----
>>>> From: "Stan Silvert" <ssilvert(a)redhat.com>
>>>> To: keycloak-dev(a)lists.jboss.org
>>>> Sent: Thursday, 4 December, 2014 1:27:11 PM
>>>> Subject: Re: [keycloak-dev] AS7 subsystem problems Re: release? Stan?
>>>>
>>>> On 12/4/2014 2:54 AM, Stian Thorgersen wrote:
>>>>> ----- Original Message -----
>>>>>> From: "Bill Burke" <bburke(a)redhat.com>
>>>>>> To: keycloak-dev(a)lists.jboss.org
>>>>>> Sent: Wednesday, 3 December, 2014 8:23:55 PM
>>>>>> Subject: Re: [keycloak-dev] AS7 subsystem problems Re:
release?
>>>>>> Stan?
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 12/3/2014 12:30 PM, Stan Silvert wrote:
>>>>>>> 1) Bring back the old code for the AS7 subsystem.
>>>>>> Bring it back. If you don't, let me know and I'll do
it.
>>>>> Why? I don't get why we keep trying to get AS7 to work.
We've already
>>>>> wasted a fair bit of time on this.
>>>> To me, it's not really a matter of getting it to work. I've
restored
>>>> the old code and I just need to test everything out today. There is no
>>>> reason to think it won't work as before.
>>>>
>>>> The only question in my mind is whether or not anyone will want to use
>>>> it. I guess there is not that much incremental cost in maintaining the
>>>> old code. As I understand it, Bill's overriding strategy is to
support
>>>> every platform possible.
>>>>
>>>> I've already changed course on this a couple of times, so I'd
like to
>>>> just finish and move on.
>>> Sure, I just want a reason to continue supporting AS7 though as it does
>>> come back to haunt us every once in a while.
>>>
>>> JPA issues, web-services issues, sub-system issues, etc.. By now we've
>>> probably spent a few days at least this year on an outdated platform.
>> Perhaps dropping auth server support will help with that? What I'm
>> doing now only affects AS7 client apps.
> Yes, IMO we should definitively drop auth server support on AS7.
>
> With regards to client support, IMO we should drop support for AS7
> completely, but at very least the subsystem and just require including the
> adapter in the WAR like we do for Tomcat, Jetty, etc...
I wonder if we should provide something like download with "generic"
auth-server.war, which will be able to run on all servers like AS7,
Tomcat or Jetty. It seems to me that having auth-server running on
Tomcat or Jetty won't be so much headache. It may just be about bundling
all required deps like resteasy, jackson etc in
auth-server.war/WEB-INF/lib/ .
Having auth-server available on Tomcat or Jetty might be useful as we
have adapters for them already, so people won't need to use separate
Tomcat/Jetty server with their apps and separate Wildfly/EAP6 with
auth-server, but they can have everything on single server. It may be
also useful for Fuse integration (it's still unclear to me how deep
should be fuse integration and if keycloak integration/adapters is
enabled just on demand or by default, but having possibility to have
auth-server deployed in fuse might be helpful with the decision as then
fuse won't require separate KC server running on WF or EAP)
Hopefully we will be able to have same auth-server.war running on AS7/
JEtty and Tomcat with all dependencies inside and without
jboss-deployment-structure.xml (we already have some needed changes in
jboss-deployment-structure.xml for AS7 -
http://docs.jboss.org/keycloak/docs/1.1.0.Beta1/userguide/html/server-ins...
. So having separate WAR without jboss-deployment-structure.xml may help
to avoid this and have AS7 integration even simpler)
Tomcat and Jetty are actually much simpler, just chuck all deps into WEB-INF/lib and away
you go. Problem with AS7 is that it adds all sorts of conflicting dependencies
automatically and it doesn't have an easy way to exclude them as exclude-subsystem in
jboss-deployment-structure.xml isn't available on AS7, which results in finding
workarounds for all sorts of problems.
Marek
>
>>>>>> --
>>>>>> 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
>>>>>>
>>>>> _______________________________________________
>>>>> keycloak-dev mailing list
>>>>> keycloak-dev(a)lists.jboss.org
>>>>>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>>> _______________________________________________
>>>> keycloak-dev mailing list
>>>> keycloak-dev(a)lists.jboss.org
>>>>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>>>
>>
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/keycloak-dev