Hi, I don't think you can. At least not without heavy refactoring. You can though override org.soulwing.confluence.cas.filter.logoutUrl and change implementation to resolve it's hostname based on client request. It may impact security if you don't pay attention on what hostname declares client or ip class it is from. I would suggest changing network configuration: the same domain for CAS, but two different networks: external and internal. you can configure your domain resolver to resolve CAS domain different IP based on network client asks from. Hope it helps. Best regards, Augustyn
On 7 October 2014 at 06:25, Thach Le <thachpor...@gmail.com> wrote: > Dear all, > > I want to deploy CAS for my web app on Tomcat. > The my web app be accessed from internet by http://mydomain1/mywebapp and > http://mydomain2/mywebapp. > There is no problem about configuration of Apache (support virtual host) and > Tomcat (use jk_mod) > > About CAS deployment, as guideline at > https://wiki.jasig.org/display/CASC/Confluence+as+CAS+Client, section > "Configuring web.xml", I found the domain must be fixed > > .... > <param-name>org.soulwing.confluence.cas.filter.logoutUrl</param-name> > <param-value>https://YOUR_CAS_SERVER/logout</param-value> > .... > > Some other settings are fixed also. > > How I can configure dynamic domain such as below? > --- > <param-value>https://{YOUR_CAS_SERVER}/logout</param-value> > --- > > Thach Le > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > augustynw...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
