Culprit is SURELY the SingleSignOutValve ... commenting it out everything works perfectly
On Tuesday, January 19, 2016 at 12:53:53 PM UTC+1, luca wrote: > > Hi all. > > I have a webapp (running in tomcat7) which I configured for SSON with cas > using tomcat valves as in: > > <Valve > className="org.jasig.cas.client.tomcat.v7.Cas20CasAuthenticator" > encoding="UTF-8" > casServerLoginUrl="...." > casServerUrlPrefix="....." > serverName="...." > /> > > <!-- Single sign-out support --> > <Valve > className="org.jasig.cas.client.tomcat.v7.SingleSignOutValve" > artifactParameterName="SAMLart" > /> > > Now, a number of forms get the wrong encoding ... data posted with > accented letters get saved with mangled chars. > > Underlying mysql is UTF8, connector UTF8 as well and the webapp already > has a filter forcing UTF8 .. > Apparently someone else found problems with encoding (see e.g. > https://wiki.jasig.org/display/CASC/Configuring+Single+Sign+Out) > however here i configured cas through a valve and not trough a web filter > so i'm stuck .. any idea? > > -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.
