There's an issue with X509 auth as it relies on a method [1] that has been
renamed in Bouncycastle 1.52 to 1.56. Both EAP 7.1 and WF11 use BC 1.56,
while WF10 use 1.52.
I can't merge it to master until we bump to WF11.
[1]
https://github.com/keycloak/keycloak/commit/a62213137c942580b6b8980585da4...
On 8 May 2017 at 08:29, Stian Thorgersen <sthorger(a)redhat.com> wrote:
Not sure, but you can already build KC server with WF11 Alpha1 by
running:
mvn clean install -Pwf11 -Pdistribution
At least the feature pack is there.
On 5 May 2017 at 16:56, Pedro Igor Silva <psilva(a)redhat.com> wrote:
> Are all dependencies available ? Didn't find wildfly-core dependencies in
> Maven central .... But only wildfly-dist.
>
> On Fri, May 5, 2017 at 6:06 AM, Stian Thorgersen <sthorger(a)redhat.com>
> wrote:
>
>> WildFly 11 is due to be released before we are releasing Keycloak 3.2.
>>
>> I would like to upgrade to WildFly 11 Alpha11 now so we can see if we
>> find
>> any issues with the plan that we will upgrade to WildFly 11 Final before
>> we
>> release Keycloak 3.2.0.Final.
>>
>> There's a slight chance that it would be delayed, but in that case we can
>> simply delay 3.2.
>>
>> Any objections? Or can I go ahead and upgrade master?
>> _______________________________________________
>> keycloak-dev mailing list
>> keycloak-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
>>
>
>