Potential CAS BOFs at Jasig 2011

BoF: CAS and Shibboleth

Who:

Adopters of both CAS and Shibboleth in concert
Adopters of CAS with SAML2 and Federation aspirations
Adopters of Shibboleth with CAS flexible, pluggable, campus-local SSO experience goodness aspirations
CAS steering committee (or representatives thereof)
CAS developers
Anyone else who wants to be at this BoF

What:

Share and discuss who is doing what using CAS and Shibboleth in concert how and why
Gather requirements and expressions of interest from adopters of zero or one of these solutions with interest in adopting both in concert
CAS steerers and developers learn more about what is working, what is not working, and what is desired

Who:

Anyone ready to admit that he or she has locally modified CAS
CAS steerers and developers eager to learn about how CAS adopters have locally modified CAS
Anyone else who wants to be at this BoF

What:

Sharing of use cases, examples, demonstrations, ideally even source code of what modifications CAS adopters have performed locally
Feedback about the suitability of CAS designed-in extension points, how to improve these, what works, what doesn't
If we get bored or time allows, diving into CAS trunk interfaces to look at and have reactions to extension points and APIs
Coffee, donuts, and name tags suitable for conveying first names only may be available

Who:

Anyone who maintains a local CAS deployment
Anyone who would like to learn more about how others maintain a local CAS deployment
CAS steerers
CAS developers
Anyone else who wants to be at this BoF

What:

Discussion of what works, what's hard, what's problematic, in succeeding at running and maintaining a CAS deployment, including
- Effective use of Source Control
- How's that Maven Overlay approach working out?
- Environments and Migration of Change Between Environments
- Upgrades
- Branding and Skinning
CAS steerers and developers soaking up feedback and experiences of how CAS is working in practice