Le 27/09/2012 17:05, jleleu a écrit :
Hi,
Yes, indeed, it's necessary to require that all clients ignore unknown
attributes, it will usefull for next protocol revision.
For this protocol revision, we can accomodate none breaking changes with Java
and PHP clients. I think it's the vast majority of our clients so it's a good
news.
But what about others ? mod_auth_cas ? DotNet ? Ruby ?
For approximately two years we used a modified JSP for service
validation in order to provide attributes through standard CAS 2.0
answer (name-value scheme). It worked very well with phpCAS (with a
little issue due to EL), and it didn't break anything with mod_auth_cas.
Rgds.
--
You are currently subscribed to cas-dev@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-dev
