> I can't seem to get anything else out of it but the generic Succes message.
Success is paradoxically a failure; that confused error message has been fixed in 3.3.5, http://www.ja-sig.org/issues/browse/CAS-808. > And all I can find about that is that it's most likely the difference in > systemtimes on the client and the server. Note that the Java CAS client has a tolerance parameter, http://www.ja-sig.org/wiki/display/CASC/Configuring+the+JA-SIG+CAS+Client+for+Java+in+the+web.xml, to accommodate for clock drift. Clock drift is the most common source of problems we've seen on the list w/r/t SAML. Also, the CAS server is _very_ particular about the format of incoming SAML requests, which will come into play if you're trying to use standard SAML tools or roll your own SAML integration. M -- 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
