Hi all, I think the SSO is a big issue when we suggest clients to adopt Seam. I try the CAS SSO and rewrite Authenticator and Pages classes according to CAS wiki but it does not work properly. Even I can use SSO in two Seam applications, the seam application does not work same as before. The reason seems that Seam can not handle navigation(pages.xml/x.page.xml) correctly any more. For example, when I login a simple CRUD Seam application and create a new entity, after I click save button, the entity is created successfully but I am not navigated to the Entity.xhtml and stayed at the same edit page. When I click list page, and click View/Edit link of the entity, the entity's information is not shown at the corresponding fields. They are all empty. In fact, the CAS SSO adds some filters in web.xml. Does them affect Seam's navigation? After I remove CAS SSO configuration, all works fine. SSO is a common requirement of many clients. Can somebody help to figure out what happened? Thanks. -- Sean Wu JBoss Solution Architect RedHat Service Center, P.R.China Email: seanwu(a)redhat-service.com.cn Mobile: 13911868610