Layer7 Access Management

Expand all | Collapse all

CA SiteMinder 12.7 Proxyui error 500

Jump to Best Answer
  • 1.  CA SiteMinder 12.7 Proxyui error 500

    Posted 12-17-2018 07:52 AM

    Hi dear CA Community,

     

    We have installed the SiteMinder SPS 12.7 according to the documentation. After the installation process, when we try to access to the proxyui administrative UI we got the following error message "Server Error. The server was unable to process your request".

    Regarding the documentation, we have to add the user directory in the Domain and policy domain. We have done this action. The problem is we cannot get the login.fcc page.

    Someone could help ?

    Additionnally in the SPS trace.log file I have the following Tomcat HTTP 500 error message that correspond to my browser request:

    [12/17/2018][13:30:36][7288][7552][5733z991-a5e6d5f8-612792fd-dbc34f5e-0e5eet5a-777][CSmCredentialManager::GatherAdvancedAuthCredentials][SM_WAF_HTTP_PLUGIN->ProcessAdvancedAuthCredentials returned SmNoAction.]
    [12/17/2018][13:30:36][7288][7552][5733z991-a5e6d5f8-612792fd-dbc34f5e-0e5eet5a-777][CSmCredentialManager::GatherAdvancedAuthCredentials][Calling SM_WAF_AG_PLUGIN->ProcessAdvancedAuthCredentials.]
    [12/17/2018][13:30:36][7288][7552][5733z991-a5e6d5f8-612792fd-dbc34f5e-0e5eet5a-777][CSmCredentialManager::GatherAdvancedAuthCredentials][SM_WAF_AG_PLUGIN->ProcessAdvancedAuthCredentials returned SmNoAction.]
    [12/17/2018][13:30:36][7288][7552][5733z991-a5e6d5f8-612792fd-dbc34f5e-0e5eet5a-777][ProcessAdvancedAuthentication][CredentialManager returned SmNo or SmNoAction, calling ChallengeManager.]
    [12/17/2018][13:30:36][7288][7552][5733z991-a5e6d5f8-612792fd-dbc34f5e-0e5eet5a-777][CSmChallengeManager::DoAdvancedAuthChallenge][Calling SM_WAF_HTTP_PLUGIN->ProcessAdvancedAuthChallenge.]
    [12/17/2018][13:30:36][7288][7552][5733z991-a5e6d5f8-612792fd-dbc34f5e-0e5eet5a-777][CSmChallengeManager::DoAdvancedAuthChallenge][SM_WAF_HTTP_PLUGIN->ProcessAdvancedAuthChallenge returned SmExit.]
    [12/17/2018][13:30:36][7288][7552][5733z991-a5e6d5f8-612792fd-dbc34f5e-0e5eet5a-777][ProcessAdvancedAuthentication][Unable to challenge, end new request.]
    [12/17/2018][13:30:36][7288][7552][][ReportHealthData][Accumulating HealthMonitorCtxt.]
    [12/17/2018][13:30:36][7288][7552][5733z991-a5e6d5f8-612792fd-dbc34f5e-0e5eet5a-777][Tomcat5SerializedAgentData::doResponse][HTTP Status Code = 500]
    [12/17/2018][13:30:36][7288][7552][5733z991-a5e6d5f8-612792fd-dbc34f5e-0e5eet5a-777][ProxyValve::invoke][Exit status returned from the agent.]
    [12/17/2018][13:30:36][7288][7552][5733z991-a5e6d5f8-612792fd-dbc34f5e-0e5eet5a-777][ProxyValve::invoke][Leaving the agent.]

     

    Thank you for your helpful advices.

     

    Cheick.



  • 2.  Re: CA SiteMinder 12.7 Proxyui error 500
    Best Answer

    Posted 12-19-2018 08:27 AM

    We have finally found the error.

    In the documentation of CA SiteMinder SPS 12.7 there is an error / mistake. In fact, after installation and configuration, you have to move the proxyui folder located under to tomcat/webapp directory to proxy-engine forms directory. This is not done by default by the sps config exe that's why the server sends an http 500 error.

     

    this could help other people ...

     

    Cheick.