If dotCMS is relying on the request.getRemoteUser() you should be able to swap the configuration per our existing Jasig CAS Client 3 example.
If its relying on specific features of the Yale client, that would be more difficult. On Thu, Mar 15, 2012 at 5:52 AM, Bill Scully <[email protected]> wrote: > Hi, > > Thanks in advance for taking the time to read this and for any help you > can offer. > > I’m wondering if anyone is running dotCMS 1.9.x CASified with the JASIG > 3.x client? Out of the box, dotCMS (www.dotcms.org), only works with the > Yale CAS Client and the config in their web.xml looks like this: > > <!-- CAS servlet --> > <servlet> > <servlet-name>casproxy</servlet-name> > > <servlet-class>edu.yale.its.tp.cas.proxy.ProxyTicketReceptor</servlet-class> > </servlet> > <!-- END CAS servlet --> > > <context-param> > <param-name>edu.yale.its.tp.cas.proxyUrl</param-name> > <param-value>https://hostname/cas/proxy</param-value> > </context-param> > > <!-- CAS filters --> > <filter> > <filter-name>CAS Filter</filter-name> > > <filter-class>edu.yale.its.tp.cas.client.filter.CASFilter</filter-class> > <init-param> > > <param-name>edu.yale.its.tp.cas.client.filter.loginUrl</param-name> > <param-value>https://hostname/cas/login > </param-value> > </init-param> > <init-param> > > <param-name>edu.yale.its.tp.cas.client.filter.validateUrl</param-name> > <param-value>https://hostname/cas/serviceValidate > </param-value> > </init-param> > <init-param> > > <param-name>edu.yale.its.tp.cas.client.filter.WrapRequest</param-name> > <param-value>true</param-value> > </init-param> > <init-param> > > <param-name>edu.yale.its.tp.cas.client.filter.serverName</param-name> > <param-value>hostname</param-value> > </init-param> > </filter> > <!-- End of CAS filters --> > > <!--CAS FILTER-MAPPINGS--> > <filter-mapping> > <filter-name>CAS Filter</filter-name> > <url-pattern>/c/portal/login</url-pattern> > </filter-mapping> > <filter-mapping> > <filter-name>CAS Filter</filter-name> > <url-pattern>/dotCMS/login</url-pattern> > </filter-mapping> > <filter-mapping> > <filter-name>AutoLoginFilter</filter-name> > <url-pattern>/c/portal/login</url-pattern> > </filter-mapping> > <filter-mapping> > <filter-name>AutoLoginFilter</filter-name> > <url-pattern>/dotCMS/login</url-pattern> > </filter-mapping> > <!--CAS FILTER-MAPPINGS--> > > <!-- CAS servlet --> > <servlet> > <servlet-name>casproxy</servlet-name> > > <servlet-class>edu.yale.its.tp.cas.proxy.ProxyTicketReceptor</servlet-class> > </servlet> > <!-- END CAS servlet --> > > <servlet-mapping> > <servlet-name>casproxy</servlet-name> > <url-pattern>/casProxy/*</url-pattern> > </servlet-mapping> > > > We really need to be able pull the LDAP groupMembership attributes through > CAS and my understanding is that only the JASIG CAS Client can do this. > Has anyone successfully CASified dotCMS using the JASIG CAS Client? If > so, would you mind sharing how? > > Thanks a ton. > > Bill > > -- > 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
