[security-dev] PicketLink workspace proposal

Pedro Igor Silva psilva at redhat.com
Thu Oct 4 14:00:30 EDT 2012

----- Original Message -----
From: "Anil Saldhana" <Anil.Saldhana at redhat.com>
To: security-dev at lists.jboss.org
Sent: Thursday, October 4, 2012 12:24:09 PM
Subject: [security-dev] PicketLink workspace proposal

>Hi all,
>    here is what Shane and I have been discussing in the last 10 days 
>that we can come to an agreement in this thread. Please provide your 
>feedback and insights as we move forward with the PicketLink main workspace.

>PicketLink main workspace will have the following modules:
>a) core :  will contain the CDI based security code that Shane has been 

+1. I'm also think that *cdi* is a better name.

>b) idm:  will contain the idm api and impl submodules.  This is low 
>dependency JavaSE library for Identity Management functionality (CRUD of 
>users/roles/groups). This module is ultra critical to all projects.


>c) federation: will contain the core SAML (and maybe WS-Trust) code 
>without any EE container dependencies. Mainly parsing, writing and model 


>d) social: will contain social login code that allows signin using 
>facebook, google/openid, twitter.


>Last major release of PL has been with 2.1.5 
>So definitely we can release above with 3.x


>Since we may need some container binding code with AS, Tomcat etc, we 
>have two possibilities:
>a) Create another workspace in PicketLink github organization for the 
>container binding. (My preference)


>b) Create a separate github organization that will host all the 
>container bindings, integration testing workspaces etc. We can call it 


security-dev mailing list
security-dev at lists.jboss.org

More information about the security-dev mailing list