Matt,

I noticed this email and have forwarded it to cas-steer for discussion of what the CAS Steering Committee would consider. :)

Without that discussion having happened, I'm not prepared to speak authoritatively to what additional strategic effort, coordination, calories the CAS Steering Committee might be willing to consider applying.

I will however note that in some ways this is less a question of whom Jasig and cas-steer would consider working with, and more a matter of who would consider working with the CAS community. CAS is free and open source software with a simple, well-documented protocol, an extensible modular implementation, and most importantly, a community of developers and participants with a justly-earned reputation for friendliness. When providers of SSO-as-a-service apply effort and engage with the CAS community to enhance the CAS support of their products and services, I'd expect they'd get supportive responses on the lists and elsewhere as most other comers have, and I'd expect they could be quite successful in CAS-integrating their products.

I appreciate that's not quite what you asked, though. Your question seems to go more to the strategic value to Jasig and to CAS in instigating this kind of support for the CAS protocol in these products and services. It's a worthwhile strategic question, one I'll take up with the CAS Steering Committee, which doesn't preclude further discussion here as well.

Thanks for bringing it up.

Andrew



On 03/29/2011 08:22 AM, Smith, Matthew J. wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Would JASIG or the CAS Steering Committee (or whomever is appropriate)
consider working with an existing authentication provider like
http://www.protectnetwork.org/ to offer the CAS protocol as an
additional authentication service?  ProtectNetwork today advertises
"Open standards compliant: Shibboleth, SAML, OpenID", so they are
already multi-protocol.

- -Matt

On 03/28/2011 03:55 PM, Marvin Addison wrote:
I was thinking if we can start CAS on Cloud then it would very
easier for any developer to test and learn CAS.
Sounds great except "cloud" is far too vague in terms of both
provisioning and consumption. Practically speaking, who would
host this offering?

What features should this cloud offering provide? (I assume the
cloud offering is strictly for demonstration and evaluation). The
most common features needed by deployers:

- Username/password authentication with LDAP backend -
JpaTicketRegistry for ticket storage/registered services
(Memcached comes in second by my very unofficial scorekeeping)

Anything else?

M


- -- Matthew J. Smith
University of Connecticut UITS
[email protected]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2RzyIACgkQGER0Au6g8xBUiACg5WVE+P09Cy25jPi5gIct2kW9
1q0AoLKHCMaMprn2QWtKudbfP9zkDFoJ
=Ou5b
-----END PGP SIGNATURE-----




--
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

Reply via email to