Hi,
I have been facing the same issue today and have been playing around a bit to see if I could overcome this issue.
I have three custom html-files I need to be able to show to users which are not authorized to log into Clarity.
What I did to come around this is that I edited the "Clarity Content Filter" in the Web.xml file (you find it under /clarity/webroot/WEB-INF)
I have added "auth_error.html", "logged_out.html" and "maintenance.html" to the <param-value> below:
<filter id="Clarity Content Filter">
<filter-name>Clarity Content Filter</filter-name>
<filter-class>com.niku.union.web.filter.ClarityContentFilter</filter-class>
<init-param>
<param-name>allowedList</param-name>
<param-value>DefaultPrint.css,FeaturePrint.css,pagebutton-center.png,Login.gif,ajax-impls.js,ajax.js,lookupManagement.js,DefaultScreen.css,DocMgrScreen.css,LinkActions.js,common.js,Theme.css,FeatureScreen.css,Feature.css,smallFont.css,spacer.gif,WdgError.gif,Spacer.gif,/timesheet,spacer.png,blue.gif,eMailLogo.gif,workspace.png,BOServerStatus.jsp,monitor.jsp,monitor_lite.jsp,common.png,/login,/logoff,min.js,min.css,shortcut.ico,favicon.ico,s.gif,_header.gif,cache.js,gantt.js,hook.js,/nu,/app,.cache.html,hosted.html,pie.htc,/odata*,/odata.v2*,/soap,/sched,/xog,/proxool*,/wsdl*,/test.html,blue.gif,spacer.png,eMailLogo.gif,auth_error.html,logged_out.html,maintenance.html,/</param-value>
</init-param>
</filter>
Before editing the Web.xml I recommend creating a copy of the original file, just in case.
After changing the Web.xml file, you need to stop and start the app-service. If you have a cluster, make sure you do the same update on every server in the cluster.
The custom html-files are placed under /clarity/webroot/-folder.
Remember to give read/write access rights for the html-files to the service account running Clarity.
This is probably "not supported". I haven't tested this much, so it would be nice to hear if anyone else have any experience with editing the content filter.
Knut