Shibboleth Developers

Phone #:  (800) 541-1710
Pin #:  0142203

(For the next period of time, a significant portion of each call will 
be spent discussing design issues. A portion of each call will be 
reserved to discuss current programming -related issues. However, I'd 
like to try to limit this to 15 minutes or so each week.)

Last monday, we spent some time discussing use cases and requirements 
for a java-based target implementation. Following up on that 
conversation, Walter is continuing to contact people, in order to 
obtain more detailed  information. We'll return to that topic during 
a future call. As always, please send questions and  new info  on 
this topic to the list.

Agenda:

1) Intellectual Property Rights Awareness

2) Current programming issues/questions

3)  Design issues, "use of Shib/SAML in non-browser, non-web 
applications" (discussion of use cases)

The current Shib implementation supports the web environment. Users 
use Web Browsers; the target side implementation is a set of web 
server plugins. That's probably OK as a starting point. However, 
there are non-web based applications out there. The SAML model that 
Shib uses is not limited to the web ( see 
http://www.oasis-open.org/committees/security/docs/draft-sstc-use-domain-05.pdf 
for the SAML Domain model).

I'd like to start collecting use cases for Shib in non-browser, 
non-web applications. Please email them to the list before monday's 
call. They should reference how the authentication assertion is 
obtained, and how assertions are transported and used.

For the time being, I'd  like to keep this discussion separate from a 
discussion of the use of SAML assertions in n-tier environments. 
We'll  get to that one  soon enough.

------------------------------------------------------mace-shib-design-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at 

   http://archives.internet2.edu/

------------------------------------------------------mace-shib-design--