8:15 p.m.
Hi Pedro Igor,
I was not clear when we spoke this morning. Sorry about that. Please see
my comments inline below.
Thanks
Sande
On 02/24/2014 12:13 PM, Pedro Igor Silva wrote:
Hi All,
After discussing with Sande about the best way to port the PicketLink Federation
(SAML SSO) Quickstarts [1] to the PicketLink JDF Quickstarts [2], she asked me to open a
thread to collect some more suggestions about the best way of doing it.
Basically, the 'issue' we have is that our federation quickstarts depend on
each other. This is important because users won't get the whole functionality if they
deploy just one of the quickstarts. Those quickstarts demonstrate SSO, so we need an
authentication authority, which we call IdP (Identity Provider), and its relying parties,
which we call SP (Service Provider).
Today we have 5 different IdP applications, and a bunch of SP ones. Each SP relies
on a specific IdP, so in order to get functionality working we need them deployed
together.
Those quickstarts from [1] are not new, users and also customers are very used to
see them this way(as separated WARs which you deploy and test our functionality). Sande
suggested us to think about having a EAR with all related applications, but this goes
against PL real world use cases and gives a very wrong understanding about PL usage. For
us and our users, the best thing is keep each quickstart as a single WAR.
I think
you misunderstood what I was saying :-).
I did not suggest building an EAR. I suggested grouping the dependent
projects in subdirectories under one parent folder, similar to the EAP
inter-app [1] quickstart. That quickstart is similar in that you must
deploy mulitiple WARs that are dependent upon each other.
If you look a the structure for that quickstart:
* There is one top level README file that describes the example and
what each of the 3 modules does.
* The top level parent POM file contains modules for each subproject
and shared resources and builds all the child WARs in one step.
[1]
https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.3.x-devel...
So, given all that, I would like to collect some feedback about the best way to
document those quickstarts in their README files. Can we have a section to reference other
related quickstarts ?
If the related quickstarts are under one folder, they only
need one
README at the top leve that describes everything. If you prefer, you
could keep the individual README files and link to them from the top
level README.
Probably with links to other quickstarts so we can tell users
what they need to do to get the environment properly set ?
Any other suggestion ?
[1] https://github.com/picketlink2/picketlink-quickstarts/tree/master/saml
[2] https://github.com/jboss-developer/jboss-picketlink-quickstarts
Best regards.
Pedro Igor
_______________________________________________
jdf-dev mailing list
jdf-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jdf-dev