[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [higgins-dev] RP code checked in
|
Duane, not sure what your intent was behind the note, we did had "open" discussions about the direction of the Java RP at the Higgins F2F Last week and even the F2F prior to that. Most all functionality is "light" on content on first drop, much like the evolution that IdAS has gone through. So I suggest you look over the classes/code and provide feedback and what is there now.
Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
![Inactive hide details for "Duane Buss" <DBuss@xxxxxxxxxx>]()
"Duane Buss" <DBuss@xxxxxxxxxx>
"Duane Buss" <DBuss@xxxxxxxxxx>
Sent by: higgins-dev-bounces@xxxxxxxxxxx
07/02/2007 02:23 PM
Please respond to
"Higgins \(Trust Framework\) Project developer discussions" <higgins-dev@xxxxxxxxxxx> |
|
|
I hadn't encountered the term Relying Parity Service before, is that the improved version of a Relying Party Service? (grin)
I have read the pages and downloaded the projects and I agree with Jeffrey, they are currently 'a bit light.' From the wiki I know where RSSE and the other RP components fit in but the actual internal architecture and functionality are vague. Can we make this a focus on the mailing lists and conference calls to have open discussion about the direction, architecture, structure of these components?
-Duane
>>>
Yes. See http://wiki.eclipse.org/RP_Enablement. It probably makes sense to have a separate Eclipse Bugzilla component for each “Relying Parity Service” component/language combination. If folks agree, I’ll set this up.
-Paul
Yes, the RPE is one of the key items Higgins needs to focus on, so this will need to cover Java, PHP, Ruby, etc. So we may divide RP components up into these categories, much like we have the IAs today with H1, H2 and H3
Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
"Broberg, Jeffrey C" <Jeffrey.Broberg@xxxxxx>
"Broberg, Jeffrey C" <Jeffrey.Broberg@xxxxxx>
Sent by: higgins-dev-bounces@xxxxxxxxxxx
07/02/2007 09:51 AM
Please respond to
"Higgins \(Trust Framework\) Project developer discussions" <higgins-dev@xxxxxxxxxxx> |
|
|
I took a look at those projects and they were a bit light right now. Do
we still believe that higgins should deal with RPE ?
Jeffrey C. Broberg
CA
Director, Senior Architect
Security Systems
Advanced Technology Group
Tel: +1-508-628-8490
Jeffrey.Broberg@xxxxxx
=jeff.broberg
http://jyte.com/widget/claim/cardspace-will-be-a-success
> -----Original Message-----
> From: higgins-dev-bounces@xxxxxxxxxxx
> [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Michael McIntosh
> Sent: Friday, June 29, 2007 1:16 PM
> To: Higgins (Trust Framework) Project developer discussions
> Cc: Higgins (Trust Framework) Project developer discussions;
> higgins-dev-bounces@xxxxxxxxxxx
> Subject: Re: [higgins-dev] RP code checked in
>
> Please note that MSFT is funding several opensource projects
> to build RP Enablement for different languages, unfortunately
> these are currently licensed under BSD:
> http://www.codeplex.com/Project/ProjectDirectory.aspx?ProjectS
earchText=CardSpace
>
> Thanks,
> Mike
>
> higgins-dev-bounces@xxxxxxxxxxx wrote on 06/29/2007 12:50:33 PM:
>
> > Jeff, now that I understand the code a little better, I think I can
> > answer some of your questions:
> > What parts of the Demo can be reused as parts of the RPE ( Relying
> > Party Enablement ) ?
> >
> > The demo is an example of how to use an authentication filter and
> > servlets. The RelyingPartyDemo project is the filter, and the
> > RelyingPartyDemoApp is an example of using the filter. I
> think both
> > parts are relevant to RPE. If you like, I can add rows to the RPE
> > Component table for these.
> >
> > What mechanism/tool was used to generate the object tag ?
> >
> > Don't know -- Bruce will have to answer this one.
> >
> > What mechanism/tool was used for token disassembly ?
> >
> > The relevant parts of the code (I think) are org.eclipse.higgins.rp.
> > server.impl.Login.java and org.eclipse.higgins.tp.token.identity.
> > DigitalIdentity.java. The first one (Login.java) finds the
> SAML token
> > in the request, decrypts it, and verifies its signature
> (using Apache
> > XML Security). It then creates a DigitalIdentity from the token,
> > using DigitalIdentity.fromXML(), which retrieves the
> attributes from
> > inside the token. (The XML parsing is done using Apache Axiom.)
> >
> > What other pieces of functionality may be relevant for RPE ?
> >
> >
> > The filter (AuthNFilter.java), the Logout servlet
> (Logout.java), the
> > web pages in ReplyingPartyDemoApp/WebContent, and the configuration
> > file that specifies the filter --
> > ReplyingPartyDemoApp/WebContent/WEB-INF/web.xml.
> >
> > ...Greg
> >
> > _______________________________________________
> > higgins-dev mailing list
> > higgins-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/higgins-dev
>
> _______________________________________________
> higgins-dev mailing list
> higgins-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/higgins-dev
>
>
_______________________________________________
higgins-dev mailing list
higgins-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins-dev_______________________________________________
higgins-dev mailing list
higgins-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins-dev
