AnsweredAssumed Answered

CA SSO : SecureProxyServer :  Customization on SPS Doc Root

Question asked by Hubert Dennis Employee on Sep 29, 2015
Latest reply on May 29, 2018 by Rohit.Kankriya

Could I know if the following customization's are possible on Secure Proxy Server within the remit of the current design.

 

 

The parameter document_root in server.conf currently points to <install_home>/proxy-engine/examples.

 

 

#########################################

Question : If we are using the current doc root?

#########################################

 

 

1. We would like to add their Custom Error Pages under the default Doc Root in Server.conf i.e. under ?examples? folder.

2. We does not want to expose any other pages from current doc root i.e. ../../proxy-engine/example ;

    a. Is it safe to remove all the folders (We are guessing Yes, except login.fcc which is served off forms/login.fcc).

    b. What is the purpose of ?sessionscheme? and ?filters? folder under 'examples' folder? are they just examples and is safe to move these folder elsewhere if only default session scheme would be used in end user transactions?

3. Could we serve .html pages in addition to .fcc pages?

 

 

#########################################

Question : If we are using a different doc root?

#########################################

 

 

1. Could we point the Doc Root in Server.conf to some other folder path?

2. Would we just need to change the document_root parameter in server.conf OR would it need to be changed elsewhere too?

3. Would this have any cascading impact of any other functionality?

4. Could we serve .html pages in addition to .fcc pages?

 

 

 

 

#########################################

Updates from my testing.

#########################################

 

 

I was able to change the "document root" in server.conf to <sps_install_home>/proxy-engine/templates.

1. This folder only had the forms folder and siteminderagent folder.

2. All siteminder credential collector pages were working.

3. ProxyUI login was working.

4. I created a HTML page and JSP page under <sps_install_home>/proxy-engine/templates/sites.

    a. They did not work.

    b. JSP and HTML was handled by proxyrules and being sent to backend.

5. I created a HTML page and JSP page under <sps_install_home>/proxy-engine/Tomcat/webapps/sites.

    a. They did not work.

    b. JSP and HTML was handled by proxyrules and being sent to backend.

 

Is there any way to host a few pages on SPS?

 

 

 

 

The only other alternative is to host the application pages on another Web/App Server on the same SPS machine and proxy it. We would prefer avoiding to do this, as these pages are the custom login pages and error pages. Unless we state that this is absolutely not possible and proxying is the only solution.

 

 

 

 

 

 

Regards

 

 

Hubert

Outcomes