Re: [wildfly-dev] Remove PL from WFLY
On Aug 19, 2016, at 9:03 AM, Pedro Igor Silva
<psilva(a)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
2. Since it’s necessary in EAP 7.1 we would have to add it back in again.
It seems easier to just leave it be for now.
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat