We’ve set October 12th for our Alpha delivery. By the 12th the ClientLib will be cutting a critical path from bootstrapping a disco epr, through discovery, and interacting with a simple service. We’ve been working with Conor Cahill’s Server Toolkit as our test harness, and scraping queries from his Client.

So far so good! You can download what we have and watch the magic happen - the latest versions of OpenSAML’s java libraries are required (specifically java-opensaml2, java-xmltooling, and java-openws). All of the other required jars are shipped with the OpenSAML code.

There will be a great deal more progress over the next several days, but feel free to take a look.

Prateek Mishra has contributed a new further reading section to the IGF Wiki. Check it out here.

The ID-WSF 2.0 ClienLib developer team has been joined by Todd Guion. He brings excellent experience and energy to the project.

Todd obtained a Ph.D. from Stanford University in 1987 with a degree in Biophysical Chemistry. After starting a biotech company in 1989, Todd started software consulting in San Jose CA. For the next seven years, Todd consulted on several projects in medical imaging using C++ and worked with Apple Inc. writing localization tools. Todd started middleware and java programming in 1995, and started an online auction company etreasure.com in 1997. Todd has been using WebObjects and Java since 1995, and currently lives near Harrisburg PA where he has been consulting for a number of companies, including Motorola and Zenn New Media.

Todd has already been checking in some substantial code.

This marks my first post, and the start of the IGF Project at openLiberty.

The Identity Governance Framework (IGF) is now the second project at openLiberty.org. IGF will help you enable your identity-consuming applications to bind governance policies (consent and constraints) to the identity data you receive and ensure those policies are enforced whenever any other IGF-enabled application tries to access that data at a later time.

From today’s press release…

“Consisting of nearly 50 subscribers with leadership and representation from HP, Intel, Internet2/Shibboleth and OpenSAML, openLiberty.org is an open source community open to everyone interested in advancing open source Liberty Web Services and now IGF implementations. openLiberty.org will develop a set of open source libraries and technologies based on the Apache 2.0 license that developers and vendors can use to build products that consume, provide and manage identity-related information based on the IGF protocols. Developers, individuals and organizations can get more information and join the openLiberty.org IGF community here.”

A brief overview of the market requirements use case document is available here.

For those of you wanting to follow updates to the IGF project, keep an eye on this blog. I will also continue to post more general articles over at the IdentityPrivacy blog.

I also want to thank all of the Liberty member organizations who have contributed to getting the Market Requirements Document done. Their contributions have really begun to crystalize the IGF requirements. Now we all have to work hard to make IGF “real” through actual implementation and standards definition!

Other sites of interest:

• Liberty Alliance - IGF Strategic Initiative
• Oracle Technology Network - IGF Draft Specifications & Overview

…/Phil

The value of a good editor!

Last night we checked in the first lines of code for the project on our project site on sourceforge! The code is primarily the ID-WSF EndpointReference modeled with XML Tooling. It requires three projects from OpenSAML, java-xmltooling, java-opensaml2, and java-openws. The great thing is that the saml2 assertion and the soap envelope came for free from the OpenSAML libs.

My spouse pointed out the text on the back of the boat pictured to the left. It was too good not to send your way. Imagine, ruining a perfectly good boat!

The meeting was held on Wednesday 23-May-07 in a very nice conference facility in the same Georgetown University building that houses Chad’s office. We got started at 10:00AM.

We covered a lot of ground. Topics included OpenID bootstrap, OpenSAML XML Tooling, Conor Cahill’s ID-WSF client, and code generation. It was maintained that the SAML bootstrap is top and first priority, but that the requirements for OpenID bootstrapping would be very much the same as far as the ID-WSF Client is concerned.

XML TOOLING NOTE

OpenSAML’s XML Tooling creates a complete object graph based on the element structure of the XML. Unmarshalling and Marshalling are used to go from DOM based XML to Java Objects and back. The design technique that is used by OpenSAML is to break down every single element into a set of classes/objects that handle the various details of each. This can get extremely detailed. Take this XML:

<house>
  <floors>
    <floor name=”basement”>
      <room squarefeet=”40″ doors=”" windows=”" type=”bathroom” />
      <room squarefeet=”120″ doors=”" windows=”" type=”closet” />
    </floor>
    <floor name=”first floor”>
      <room squarefeet=”40″ doors=”" windows=”" type=”bathroom” />
      <room squarefeet=”120″ doors=”" windows=”" type=”kitchen” />
    </floor>
  </floors>
</house>

The code above would be supported by 5 classes for each of the following elements: house, floors, floor, and room. For example, you might take “House” and create:

HouseXMLObject.java (The object created for the element “house”)
HouseXMLObjectBuilder.java (builds the XMLObject)
HouseXMLObjectValidator.java (any validation done here)
HouseXMLObjectUnmarshaller.java (DOM element “house” to java object)
HouseXMLObjectMarshaller.java (facilitates java object to DOM element)

Each of these is registered in a config document which will identify the role that each class plays to the underlying xml tooling engine. One concern the development group had was that this level of detail might not be great for performance. Chad agreed that we might look into not building classes for some subelements.

The full notes are posted here on the wiki:
May 23rd Washington Face to Face Notes

Riggs National Bank, Georgetown
by techrose

As anyone on the developer list already knows we’re planning a face to face meeting in Georgetown this Wednesday the 23rd. We’ll be meeting at 10am and ending around 4pm. I will post an update to the list soon with any more info that I have.

Thanks to Chad we have an excellent meeting room:

Room 2005 (Second floor in Suite 2000), 3300 Whitehaven St., NW, Washington, DC 20007

Chad says: “If you’re taking a cab from somewhere be sure to mention the Northwest part of the 3300 Whitehaven St. or you’ll end up on the other side of the navy observatory. If you’re coming in via train or plane you might consider taking the metro to Dupont and taking a cab from there (it’s cheaper).”

Lunch will be catered, coffee and snacks will be available all day.

Contact me with any questions: asa dot openliberty (at) zenn dot net

A Fine Carpet, by true2source

 
I’m pleased to announce that the first draft of the architecture document that we will be using for the development of the ClientLib is available!

We hope to get lots of comments which you can send to ( asa dot openliberty at zenn dot net ) or can send via our discussion list, please subscribe.

It is interesting to note that the architecture document has been drafted entirely inside of an open wiki. Anyone can contribute and the process has been entirely visible during writing.

Hungry Goat,
by spdl_n1

Well, we’ve been cranking away on developing descriptions of the various service client classes that we will be implementing in the library. Please take a look and send in some feedback. Most recently we’ve finished the initial outline of the People Service Client.

We’re also talking about making a video to illustrate ID-WSF interactions for the uninitiated. Would this be too silly?

Make sure to start checking out the Architecture Document and send some feedback. The Consolidated Requirements doc is something else we could use your eyes on. It is on the wiki. Also, the wsf-dev mailing list has been down for a few days, we expect it will be up again soon. Looks like a mail server problem.

One thing we’re looking for is id-wsf use cases, please send them my way at asa (at) openliberty (dot) zenn (dot) net.

And finally, Spring seems to have arrived in Massachusetts! until later…