...
- Steven Githens, Northwestern
- Dr. Chuck Severance, Sakai
- Vishal Goenka, SunGard SCT
- Eric Dalquist, Unicon
- Michael Ivanov, Unicon
- Peter Kharchenko, Unicon
- Andrew Petro, Yale
Integration steps
(See also entry on Chuck's blog).
Sakai and uPortal 3 in Same Tomcat
...
A Sakai GAP Group Store implementation vending groups of Sakai users. This should be done in a nice hierarchical fashion Sakai->Sites->Pages->Tools using the hierarchy available in the GAPS and CHannel Channel Subscribe.
Sakai Tools as portlets configurable via the Portlet API
...
- Sakai filter to assert that request presents localhost / expected IP address as remote address .– Completed 10/21/05
- HTTP Basic authentication as a quick win that covers most of the need .– Completed 10/21/05
- HTTPS Client SSL certificate authentication as a possibility.
- WS-Security Username, Token profile
- Could present a traditional username, password pair that Sakai could authenticate as if a login
- Could present a username, CAS proxy ticket pair.
- How the "password" is validated should be easily replacable Sakai side; not the hard part.
- SAML using WS-Security SAML profile. Has nice features as an eventual solution, not realistic near them.
We decided that the highest priority was to do the address filtering, followed by Basic Authentication, followed by WS-Security profiles - we need to look into getting Axis to do the heavy Authorization lifting.
Outstanding Issues
- Getting the CSS pulled up from the fragments to the top page - can be done ad hoc for a while
- Delivery of events - may want to hold off until uPortal does some XMLHttpRequest stuff - some of the AJAX ideas.
Go forward plans
Andrew will start working in earnest on the tasks soon and Chuck will help as well.