On Jun 6, 2007, at 6:45 PM, Andrew Petro wrote: > Drew, > > The change you propose seems harmless. As you note, request > attributes are server-side read only. > > -1 for ternary operators. Write out the if statement so mortal > developers like me can understand what's going on, please.
+1 > My proposal is to embed a CAS server in uPortal, which *is* > designed to support all sorts of authentication strategies, has a > plugin architecture, etc. How many different LDAP authentication > provider implementations should JA-SIG be maintaining? If we > standardize on CAS as the API for this and LDAP-authentication- > enable uPortal by LDAP-authentication-enabling an embedded CAS > server, then there's only one such API to maintain and only one > configuration language to document. +1 with care to ensure the integration is black-box enough that it doesn't turn off adopters using other SSO solutions -- I think the real focus and "marketing" push is on leveraging CAS as an authentication system, with SSO being an optionally enabled (drop dead easy) benefit, and a commitment to continue to support other SSO systems as first class citizens. Andrew -- you had previously proposed cutting 2.7 in a separate branch. This kind of work seems a prime candidate for an exploratory branch. Any takers? Jason -- Jason Shao Application Developer Rutgers University, Office of Instructional & Research Technology v. 732-445-8726 | f. 732-445-5539 | [EMAIL PROTECTED] | http:// jay.shao.org -- Join your friends and colleagues at JA-SIG with Altitude: June 24-27, 2007 in Denver, CO USA. Featuring keynotes by: Phil Windley, Matt Raible, Matt Asay Sessions on topics including: CAS, uPortal, Portlets, Sakai, Identity Management, and Open Source For more information & registration visit: http://www.ja-sig.org/conferences/07summer/index.html --- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
