Hi Marvin, I have a problem with logout feature when one CAS Server is connected to farm of ex. four Reverse Proxy servers serving one vhost, ex. site.example.com in active-active architecture.
mod_auth_cas logout is based on erasing COOKIE_file stored somewhere in CASCookiePath on filesystem. When I click "/cas/logout", CAS Server want to connect back to proxy backend and delete COOKIE_file, but it is able to connect to one of that reverse proxy servers based on DNS name or hosts file only. I tried to use GlusterFS for CASCookiePath, but it is not recommended for small files and for a lot of file operations like locking and writing in the same time. / ----- Oryginalna wiadomość ----- Od: "Marvin S. Addison" <[email protected]> Do: [email protected] Wysłane: wtorek, 1 październik 2013 22:07:09 Temat: Re: [cas-user] mod_auth_cas with memcached backend > Hi Guys, what do you think about such feature? It could be very > useful in Reverse proxy cluster with mod_auth_cas working as CAS > client. There are two stores that I'm aware of in mod_auth_cas: assertion data (referred to as cookies) and proxy tickets. I imagine memcached could be used for both, but I'm interested to know what storage facility you need for your particular reverse proxy situation. 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 -- 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
