Re: JAAS Interface to sourceid

Super! We're very happy to have you contributing! ;)

The essence of a browser, from a programmatic standpoint, can be found
in the open-source (Apache-licensed) HTTPClient project at Apache, here:

http://jakarta.apache.org/commons/httpclient/index.html

This will be the basis for a set of system tests we'd like to build out
for SourceID-SSO, which we have not yet begun coding. Interop testing so
far has been through a series of scripted scenarios (run through by
hand), which we had the opportunity to run against 8 other Liberty
implementations last week (all passed, after the long list of bugfixes
you saw in our last release notes).

HTTPClient could also form the basis of a JAAS facade as you have
described.

Lastly, we consciously chose to nail the Servlet/JSP set of use-cases
first, rather than delay delivery by having useful layers of abstraction
which could be invoked outside of a Servlet context. That said (and I
think we've nailed it), it might be time soon to look at design changes
to expose some of the SourceID-SSO functionality to non-servlet
environments. I'd be interested in seeing how you would go about
changing the current SourceID-SSO to allow for some of this.

Our contribution policies/procedures are here:

http://www.sourceid.org/?Contributions

They basically entail agreeing to the contribution terms (which you
already did when downloading the source code in the first place), and
how to "diff" and email these changes to me. Nothing earth-shattering
there.

Thanks again Noah for jumpstarting this discussion group!

(I'll be out of town for the rest of this week and won't be able to
respond to more postings until Monday).

Bryan