You can write your own TicketIdGenerator which uses the artifact type 1 and then just override the configuration for which id generators to use:
https://www.ja-sig.org/svn/cas3/trunk/cas-server-webapp/src/main/webapp/WEB-INF/spring-configuration/uniqueIdGenerators.xml That *should* do what you need. We do have an open issue to fix this for 3.3.6: http://www.ja-sig.org/issues/browse/CAS-817 Apparently (probably when working with Google Apps), we changed the version. Cheers, Scott On Thu, Jan 28, 2010 at 9:02 AM, JvdK <[email protected]> wrote: > > Yes you are right. I was too quick in concluding that was the problem > (which > it isn't, that's clear). Problem lies in the artifact type 2 usage, which > isn't SAML 1.1. So I need to use one where type 1 is implemented into the > class. > > It's the last day to get this right unfortunately, so that's why I was a > bit > hasty in posting the previous message, sorry. > -- > View this message in context: > http://n4.nabble.com/Howto-use-SAML-samlValidate-tp1290187p1373223.html > Sent from the CAS Users mailing list archive at Nabble.com. > > -- > 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 > -- 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
