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 ? Regards. Pedro Igor [1] http://picketlink.org/news/2015/03/10/PicketLink-and- Keycloak-project-merge/ [2] http://picketlink.org/keycloak-merge-faq/ _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

IMO after seven years in existence - all software needs to be rewritten or adapted or retired. Time to retire PicketBox and PicketLink from WildFly. Better alternatives exist hopefully. On Aug 19, 2016, at 9:11 AM, Tomaž Cerar <tomaz.cerar(a)gmail.com&gt; wrote: There have also be complains from community why we downgraded the PicketLink in WF10 and now there is a migration problem from WF9 --> 10. [1] If we remove it, we would just keep the mgmt stub so we can still manage mixed-domain with older versions. Similarly as we did with osgi & friends back in the day. It was already deprecated in 10, so we could remove it in 11 or later. -- tomaz [1] https://issues.jboss.org/browse/WFLY-5196 On Fri, Aug 19, 2016 at 4:03 PM, Pedro Igor Silva <psilva(a)redhat.com&gt; 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 ? > > Regards. > Pedro Igor > > [1] http://picketlink.org/news/2015/03/10/PicketLink-and-Keycloa > k-project-merge/ > [2] http://picketlink.org/keycloak-merge-faq/ > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

On Aug 19, 2016, at 9:11 AM, Tomaž Cerar <tomaz.cerar(a)gmail.com&gt; wrote: There have also be complains from community why we downgraded the PicketLink in WF10 and now there is a migration problem from WF9 --> 10. [1] If we remove it, we would just keep the mgmt stub so we can still manage mixed-domain with older versions. Similarly as we did with osgi & friends back in the day. It was already deprecated in 10, so we could remove it in 11 or later. -- tomaz [1] https://issues.jboss.org/browse/WFLY-5196 This is a pretty strong reason to remove it, if on top of deprecation, most of its users in community want a different version -- Jason T. Greene WildFly Lead / JBoss EAP Platform Architect JBoss, a division of Red Hat

On Aug 19, 2016, at 9:03 AM, Pedro Igor Silva <psilva(a)redhat.com&gt; 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 ?

On Aug 22, 2016, at 8:44 AM, Andrig Miller <anmiller(a)redhat.com&gt; wrote: On Mon, Aug 22, 2016 at 7:39 AM, Jason Greene <jason.greene(a)redhat.com <mailto:jason.greene@redhat.com>> wrote: > On Aug 19, 2016, at 9:03 AM, Pedro Igor Silva <psilva(a)redhat.com <mailto: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.

​ 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?