On Aug 22, 2016, at 8:44 AM, Andrig Miller <anmiller@redhat.com> wrote:

On Mon, Aug 22, 2016 at 7:39 AM, Jason Greene <jason.greene@redhat.com> wrote:

> On Aug 19, 2016, at 9:03 AM, Pedro Igor Silva <psilva@redhat.com> wrote:
>
> Hi,
>
> On the last few days I've been discussing with Tomaz about the possibility to remove PL from WFLY.
>
> The reasons for that are:
>
> - PicketLink was deprecated in favor of Keycloak. See [1] and [2].
> - Fixes are only being done to product version by GSS/SEG teams.
> - Most PL IdM and Federation capabilities such as SAML (plus a plenty of other things) are now available from Keycloak.
>
> I think we can still provide an installer (we already have that) that could be used to enable PL to a WFLY installation. That would help people using PL to continue with their designs. But for PL Federation and Subsystem, Keycloak should be the best way to go.
>
> Any comments ?

When the provisioning infrastructure for WildFly exists we could relocate it to an optional module that is not included in the default feature pack.

As it is now though, the best we can do is just not put it in our default config, which is already the case.

We could remove it from WF11, but there are two major negatives:

1. Might break users that rely on it

Of course it is deprecated, and this has been the case since EAP 6.4. I wonder what PM thinks on this. EAP 7.1, would be two releases past the deprecation. Maybe its early, but perhaps not.

That’s a good point. Perhaps its better even if we keep it in 7.1 to drop it from community even if we have to add it back again because they could always manually include it, and it would perhaps encourage earlier feedback on keycloak migrations.

2. Since it’s necessary in EAP 7.1 we would have to add it back in again.

Is this a hard requirement for EAP 7.1, that we continue to have the deprecated components?