1 Reply Latest reply on May 22, 2013 4:53 PM by Anil Saldanha

    Picketlink 2.5 or 3.0 roadmap

    Esteve Aviles Newbie

      Hi.

       

      I am starting a new project and I would like to know whether or not I can count on Picketlink as a security provider solution.

       

      I was following 3.0.0 version evolution and now it has been re-versioned to 2.5.X. What does it mean?

       

      What is the future of the Picketbox project in relation to Picketlink?

       

      Will Picketlink roadmap be updated in relation to 2.5 or 3.0 roadmap is still valid?

       

      We need social login module, will 2.5 version include the extensions package?

       

      What about the knew site? Will it be updated?

       

      In our project we need IDM and REST based authentication with social login, is picketlink a good candidate or do we need to look for another alternative?

       

      Will Picketlink keep on depending on Deltaspike project?

       

      Sorry for all these questions, but we have been following picketlink project for a while and we are not able to foresee enought stabilty to use it in our projects despite we are very interested in.

       

      Please let us know if we can provide some  help in any way.

       

      Regards,

       

      Esteve

        • 1. Re: Picketlink 2.5 or 3.0 roadmap
          Anil Saldanha Master

          Esteve Aviles wrote:

           

          Hi.

           

          I am starting a new project and I would like to know whether or not I can count on Picketlink as a security provider solution.

          Definitely.

           

          I was following 3.0.0 version evolution and now it has been re-versioned to 2.5.X. What does it mean?

           

          Basically we renamed the 3.0 version to 2.5  No other changes made.  This is because of the following reasons:

          a) IDM component was released 1.x.  It never saw 2.x. Hence no point in releasing it as 3.x

          b) Federation component was released as 2.x and what we were planning in 3.0 is compatible with 2.x.  That is why we are moving PL3 as 2.5

          c) All the other components are just additions to the 2.1 series.

           

          This is also to keep it in line with the PicketLink 2.1.x series currently supported in JBoss EAP.  An upgrade of PicketLink will be minimally challenging to our customers, if we have the version at 2.5.

          We do not want to add in a lot of confusion to our users and customers.

           

          So functionalitywise PicketLink 3.0 is the same as proposed 2.5