10:24 a.m.
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.
Proposal:
PicketLink main workspace will have the following modules:
a) core : will contain the CDI based security code that Shane has been
driving.
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
code.
d) social: will contain social login code that allows signin using
facebook, google/openid, twitter.
Versioning:
Last major release of PL has been with 2.1.5
(https://docs.jboss.org/author/display/PLINK/v2.1.5.Final)
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
picketlinkbindings.
Regards,
Anil
12:25 p.m.
On 4 Oct 2012, at 08:24, Anil Saldhana wrote:
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.
Proposal:
PicketLink main workspace will have the following modules:
a) core : will contain the CDI based security code that Shane has been
driving.
I'm still concerned about calling this core. But...
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.
+1
c) federation: will contain the core SAML (and maybe WS-Trust) code
without any EE container dependencies. Mainly parsing, writing and model
code.
+1
d) social: will contain social login code that allows signin using
facebook, google/openid, twitter.
Have you talked to Antoine @ Agorava at all here. Agorava is the social solution we will
want to be promoting as part of the JBoss stack.
Versioning:
Last major release of PL has been with 2.1.5
(https://docs.jboss.org/author/display/PLINK/v2.1.5.Final)
So definitely we can release above with 3.x
+1
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)
+1
b) Create a separate github organization that will host all the
container bindings, integration testing workspaces etc. We can call it
picketlinkbindings.
Regards,
Anil
_______________________________________________
security-dev mailing list
security-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/security-dev
12:29 p.m.
On 10/04/2012 12:25 PM, Pete Muir wrote:
On 4 Oct 2012, at 08:24, Anil Saldhana wrote:
> 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.
>
> Proposal:
> PicketLink main workspace will have the following modules:
> a) core : will contain the CDI based security code that Shane has been
> driving.
I'm still concerned about calling this core. But...
I agree with Pete, and furthermore I think that "core" should be the
name of the missing link that should form the core of the AS security
infrastructure. Maybe "cdi" is a better name for this module.
> 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.
+1
> c) federation: will contain the core SAML (and maybe WS-Trust) code
> without any EE container dependencies. Mainly parsing, writing and model
> code.
+1
> d) social: will contain social login code that allows signin using
> facebook, google/openid, twitter.
Have you talked to Antoine @ Agorava at all here. Agorava is the social solution we will
want to be promoting as part of the JBoss stack.
>
> Versioning:
> Last major release of PL has been with 2.1.5
> (https://docs.jboss.org/author/display/PLINK/v2.1.5.Final)
> So definitely we can release above with 3.x
+1
>
> 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)
+1
> b) Create a separate github organization that will host all the
> container bindings, integration testing workspaces etc. We can call it
> picketlinkbindings.
>
> Regards,
> Anil
> _______________________________________________
> security-dev mailing list
> security-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/security-dev
_______________________________________________
security-dev mailing list
security-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/security-dev
--
- DML
12:32 p.m.
On 4 Oct 2012, at 10:29, David M. Lloyd wrote:
On 10/04/2012 12:25 PM, Pete Muir wrote:
>
> On 4 Oct 2012, at 08:24, Anil Saldhana wrote:
>
>> 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.
>>
>> Proposal:
>> PicketLink main workspace will have the following modules:
>> a) core : will contain the CDI based security code that Shane has been
>> driving.
>
> I'm still concerned about calling this core. But...
I agree with Pete, and furthermore I think that "core" should be the name of
the missing link that should form the core of the AS security infrastructure. Maybe
"cdi" is a better name for this module.
For PicketLink, I think (and Anil can correct me if I'm wrong), we want the focus to
be on application security, and security libraries that can be used to build something
like whatever security we need built in to the AS.
Or perhaps David/Darran, you could link/describe what "core of the AS security
infrastructure" is in terms I can understand ;-)
>> 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.
>
> +1
>
>> c) federation: will contain the core SAML (and maybe WS-Trust) code
>> without any EE container dependencies. Mainly parsing, writing and model
>> code.
>
> +1
>
>> d) social: will contain social login code that allows signin using
>> facebook, google/openid, twitter.
>
> Have you talked to Antoine @ Agorava at all here. Agorava is the social solution we
will want to be promoting as part of the JBoss stack.
>
>>
>> Versioning:
>> Last major release of PL has been with 2.1.5
>> (https://docs.jboss.org/author/display/PLINK/v2.1.5.Final)
>> So definitely we can release above with 3.x
>
> +1
>
>>
>> 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)
>
> +1
>
>> b) Create a separate github organization that will host all the
>> container bindings, integration testing workspaces etc. We can call it
>> picketlinkbindings.
>>
>> Regards,
>> Anil
>> _______________________________________________
>> security-dev mailing list
>> security-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/security-dev
>
>
> _______________________________________________
> security-dev mailing list
> security-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/security-dev
>
--
- DML
12:35 p.m.
On 10/04/2012 12:32 PM, Pete Muir wrote:
On 4 Oct 2012, at 10:29, David M. Lloyd wrote:
> On 10/04/2012 12:25 PM, Pete Muir wrote:
>> On 4 Oct 2012, at 08:24, Anil Saldhana wrote:
>>
>>> 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.
>>>
>>> Proposal:
>>> PicketLink main workspace will have the following modules:
>>> a) core : will contain the CDI based security code that Shane has been
>>> driving.
>> I'm still concerned about calling this core. But...
> I agree with Pete, and furthermore I think that "core" should be the name
of the missing link that should form the core of the AS security infrastructure. Maybe
"cdi" is a better name for this module.
For PicketLink, I think (and Anil can correct me if I'm wrong), we want the focus to
be on application security, and security libraries that can be used to build something
like whatever security we need built in to the AS.
Yeah - for application security
that we will market via JDF, PicketLink
will be the project given that JDF will be pitching CDI.
Or perhaps David/Darran, you could link/describe what "core of the AS security
infrastructure" is in terms I can understand ;-)
I think David is referring to
a pure security code that does not have
any CDI dependencies. Something like PicketBox core.
https://github.com/picketbox/picketbox-core
>>> 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.
>> +1
>>
>>> c) federation: will contain the core SAML (and maybe WS-Trust) code
>>> without any EE container dependencies. Mainly parsing, writing and model
>>> code.
>> +1
>>
>>> d) social: will contain social login code that allows signin using
>>> facebook, google/openid, twitter.
>> Have you talked to Antoine @ Agorava at all here. Agorava is the social solution
we will want to be promoting as part of the JBoss stack.
>>
>>> Versioning:
>>> Last major release of PL has been with 2.1.5
>>> (https://docs.jboss.org/author/display/PLINK/v2.1.5.Final)
>>> So definitely we can release above with 3.x
>> +1
>>
>>> 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)
>> +1
>>
>>> b) Create a separate github organization that will host all the
>>> container bindings, integration testing workspaces etc. We can call it
>>> picketlinkbindings.
>>>
>>> Regards,
>>> Anil
12:48 p.m.
On Thursday, October 4, 2012 at 12:24 PM, Anil Saldhana wrote:
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.
Proposal:
PicketLink main workspace will have the following modules:
a) core : will contain the CDI based security code that Shane has been
driving.
Maybe as already suggested, split into core and CDI, could be a good idea.
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
c) federation: will contain the core SAML (and maybe WS-Trust) code
without any EE container dependencies. Mainly parsing, writing and model
code.
d) social: will contain social login code that allows signin using
facebook, google/openid, twitter.
+1
Versioning:
Last major release of PL has been with 2.1.5
(https://docs.jboss.org/author/display/PLINK/v2.1.5.Final)
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)
+1
b) Create a separate github organization that will host all the
container bindings, integration testing workspaces etc. We can call it
picketlinkbindings.
-1
Regards,
Anil
_______________________________________________
security-dev mailing list
security-dev(a)lists.jboss.org (mailto:security-dev@lists.jboss.org)
https://lists.jboss.org/mailman/listinfo/security-dev
1:37 p.m.
On 4 Oct 2012, at 10:48, Bruno Oliveira wrote:
On Thursday, October 4, 2012 at 12:24 PM, Anil Saldhana wrote:
> 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.
>
> Proposal:
> PicketLink main workspace will have the following modules:
> a) core : will contain the CDI based security code that Shane has been
> driving.
Maybe as already suggested, split into core and CDI, could be a good idea.
And if PicketBox is really the "core", then perhaps that becomes PicketBox
core?
> 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
> c) federation: will contain the core SAML (and maybe WS-Trust) code
> without any EE container dependencies. Mainly parsing, writing and model
> code.
> d) social: will contain social login code that allows signin using
> facebook, google/openid, twitter.
+1
>
> Versioning:
> Last major release of PL has been with 2.1.5
> (https://docs.jboss.org/author/display/PLINK/v2.1.5.Final)
> 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)
+1
> b) Create a separate github organization that will host all the
> container bindings, integration testing workspaces etc. We can call it
> picketlinkbindings.
-1
>
> Regards,
> Anil
> _______________________________________________
> security-dev mailing list
> security-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/security-dev
_______________________________________________
security-dev mailing list
security-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/security-dev
10:38 a.m.
On 10/04/2012 01:37 PM, Pete Muir wrote:
On 4 Oct 2012, at 10:48, Bruno Oliveira wrote:
> On Thursday, October 4, 2012 at 12:24 PM, Anil Saldhana wrote:
>> 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.
>>
>> Proposal:
>> PicketLink main workspace will have the following modules:
>> a) core : will contain the CDI based security code that Shane has been
>> driving.
> Maybe as already suggested, split into core and CDI, could be a good idea.
And if PicketBox is really the "core", then perhaps that becomes PicketBox
core?
Right - from application developer perspective, using CDI and its
associated security makes perfect sense. That is why the PL module
needs to be called CDI. But for many framework developers (such as in
AS and other JBoss Community projects) that do not want to have CDI
dependency but regular SE based security, then PicketBox core is the
right answer.
>> 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
>> c) federation: will contain the core SAML (and maybe WS-Trust) code
>> without any EE container dependencies. Mainly parsing, writing and model
>> code.
>> d) social: will contain social login code that allows signin using
>> facebook, google/openid, twitter.
> +1
>> Versioning:
>> Last major release of PL has been with 2.1.5
>> (https://docs.jboss.org/author/display/PLINK/v2.1.5.Final)
>> 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)
> +1
>> b) Create a separate github organization that will host all the
>> container bindings, integration testing workspaces etc. We can call it
>> picketlinkbindings.
> -1
>> Regards,
>> Anil
10:09 p.m.
On 8 Oct 2012, at 08:38, Anil Saldhana wrote:
On 10/04/2012 01:37 PM, Pete Muir wrote:
> On 4 Oct 2012, at 10:48, Bruno Oliveira wrote:
>
>> On Thursday, October 4, 2012 at 12:24 PM, Anil Saldhana wrote:
>>> 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.
>>>
>>> Proposal:
>>> PicketLink main workspace will have the following modules:
>>> a) core : will contain the CDI based security code that Shane has been
>>> driving.
>> Maybe as already suggested, split into core and CDI, could be a good idea.
> And if PicketBox is really the "core", then perhaps that becomes PicketBox
core?
Right - from application developer perspective, using CDI and its
associated security makes perfect sense. That is why the PL module
needs to be called CDI. But for many framework developers (such as in
AS and other JBoss Community projects) that do not want to have CDI
dependency but regular SE based security, then PicketBox core is the
right answer.
So, I go back to my original gripe, why call it Picket*Box* not PicketLink?
>
>>> 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
>>> c) federation: will contain the core SAML (and maybe WS-Trust) code
>>> without any EE container dependencies. Mainly parsing, writing and model
>>> code.
>>> d) social: will contain social login code that allows signin using
>>> facebook, google/openid, twitter.
>> +1
>>> Versioning:
>>> Last major release of PL has been with 2.1.5
>>> (https://docs.jboss.org/author/display/PLINK/v2.1.5.Final)
>>> 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)
>> +1
>>> b) Create a separate github organization that will host all the
>>> container bindings, integration testing workspaces etc. We can call it
>>> picketlinkbindings.
>> -1
>>> Regards,
>>> Anil
_______________________________________________
security-dev mailing list
security-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/security-dev
1 p.m.
----- Original Message -----
From: "Anil Saldhana" <Anil.Saldhana(a)redhat.com>
To: security-dev(a)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.
Proposal:
PicketLink main workspace will have the following modules:
a) core : will contain the CDI based security code that Shane has been
driving.
+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.
+1
c) federation: will contain the core SAML (and maybe WS-Trust) code
without any EE container dependencies. Mainly parsing, writing and model
code.
+1
d) social: will contain social login code that allows signin using
facebook, google/openid, twitter.
+1
Versioning:
Last major release of PL has been with 2.1.5
(https://docs.jboss.org/author/display/PLINK/v2.1.5.Final)
So definitely we can release above with 3.x
+1
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)
+1
b) Create a separate github organization that will host all the
container bindings, integration testing workspaces etc. We can call it
picketlinkbindings.
-1
Regards,
Anil
_______________________________________________
security-dev mailing list
security-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/security-dev
1:43 a.m.
Same from me
On Oct 4, 2012, at 8:00 PM, Pedro Igor Silva <psilva(a)redhat.com> wrote:
----- Original Message -----
From: "Anil Saldhana" <Anil.Saldhana(a)redhat.com>
To: security-dev(a)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.
> Proposal:
> PicketLink main workspace will have the following modules:
> a) core : will contain the CDI based security code that Shane has been
> driving.
+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.
+1
> c) federation: will contain the core SAML (and maybe WS-Trust) code
> without any EE container dependencies. Mainly parsing, writing and model
> code.
+1
> d) social: will contain social login code that allows signin using
> facebook, google/openid, twitter.
+1
> Versioning:
> Last major release of PL has been with 2.1.5
> (https://docs.jboss.org/author/display/PLINK/v2.1.5.Final)
> So definitely we can release above with 3.x
+1
> 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)
+1
> b) Create a separate github organization that will host all the
> container bindings, integration testing workspaces etc. We can call it
> picketlinkbindings.
-1
> Regards,
> Anil
_______________________________________________
security-dev mailing list
security-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/security-dev
_______________________________________________
security-dev mailing list
security-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/security-dev
4233
days inactive
4239
days old
10 comments
6 participants
participants (6)
-
Anil Saldhana -
Boleslaw Dawidowicz -
Bruno Oliveira -
David M. Lloyd -
Pedro Igor Silva -
Pete Muir