configuring authentication cookie expiration

Kilroy

I've added the section on pg 45 from the control hub UI customization guide to my application_custom.xml file to make the authentication cookie expire, but it appears to have no effect...

I note there are 4 copies of the file in question:

G:\Interwoven\CPS\ControlHub\httpd\webapps\content_center\WEB-INF\conf\customer
G:\Interwoven\CPS\ControlHub\local\config\lib\content_center\customer_samples_src\etc\conf\customer_samples
G:\Interwoven\CPS\ControlHub\local\config\lib\content_center\customer_src\etc\conf\customer
G:\Interwoven\CPS\ControlHub\local\config\lib\content_center\customer_src_new\etc\conf\customer


1. Which path do I want to use?
2. Does this require recompiling the GUI and/or resetting the hub and/or stopping and restarting the hub?

Kilroy

Sri

Hi,

G:\Interwoven\CPS\ControlHub\local\config\lib\content_center\customer_src\etc\conf\customer\application_custom.xml is the file that you need to edit to configure expiration of the ControlHub authentication cookie. Once you've modified the application_custom.xml, please follow the instructions on page 23 of the UI Customization guide that details the steps to push these customizations to ControlHub web application.

If you are interested in what the other three directories that listed in your post do:
G:\Interwoven\CPS\ControlHub\local\config\lib\content_center\customer_samples_src\etc\conf\customer_samples,
G:\Interwoven\CPS\ControlHub\local\config\lib\content_center\customer_src_new\etc\conf\customer
The above directories have sample customizations.

The directory G:\Interwoven\CPS\ControlHub\httpd\webapps\content_center\WEB-INF\conf\customer is something internal to the ControlHub. You should not be modifying anything here.

Let me know how it works out.

Thanks
Sri