...
- 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
Sakai and uPortal 3 in Same Tomcat
...
Sakai Tools as portlets configurable via the Portlet API
...
WSRP
Securing Sakai WSRP
Need to secure Sakai WSRP production to at least authenticate the WSRP consumer communicating with it. Should update uPortal WSRP consumer apace with the WSRP producer (make it able to authenticate in the way Sakai comes to require).
- Sakai filter to assert that request presents localhost / expected IP address as remote address.
- HTTP Basic authentication as a quick win that covers most of the need.
- 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.