I haven't touched CAS before, so I am grasping at straws here, but lets start 
by making the assumption that you edited ./share/html/NoAuth/Logout.html (I 
think best practises would dictate that you edit a local copy in 
local/html/NoAuth/Logout.html, but I do not believe it is a necessity). I would 
be really surprised if you were not seeing any changes after modifying that 
file, but I have been got by all of these before, and they seem possible:

-Have you cleared your mason cache? (you'll need to rm -rf 
/your_rt_directory/var/mason_data/obj/*)
-Have you restarted your web server? (if it's apache, sudo service apache2 
restart)
-Have you cleared your browser cache?

These are the first places I'd look if applied changes are not being reflected.

Regards



Regards

Chris O'Kelly
Systems & Web Administrator

Minecorp Australia
P: 07 3723 1000

M: 0450 586 190


Minecorp Australia
37 Murdoch Circuit
Acacia Ridge QLD 4110
Australia
www.minecorp.com.au
Sent Via a Mobile Device.


-----Original Message-----
From: rt-users-boun...@lists.bestpractical.com 
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Duncan Napier
Sent: Friday, 12 July 2013 2:36 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] How to customize/redirect default Logout Page?

Hi,

I Run RT 4.0.8 using CAS Authentication and when an authenticated user selects 
the Logout item on the Settings/Logout menu, the web server forwards briefly to 
the share/html/NoAuth/Logout.html and then re-logs CAS Authenticated users back 
in. I would like to Logout.html to forward to a URL on the CAS server that 
causes the browser to clear the CAS login tokens/cookies, and effectively log 
out authenticated CAS users.

I tried editing Logout.html to redirect to the CAS logout page, but changing 
the contents of Logout.html has no effect on the Logout page as Logout.html 
seems to be defined somewhere else. Is there a .po file or something for 
replacing the RT default with a custom or forwarded logout page?

                                 Regards,

                                 Duncan.

Reply via email to