The .fcc page showing its code instead of the login page on Web Agent
search cancel

The .fcc page showing its code instead of the login page on Web Agent

book

Article ID: 46714

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On CA Single Sign On Agents (SiteMinder) SITEMINDER

Issue/Introduction

 

When running a Web Agent, when accessing the Custom HTML
Authentication Scheme .fcc, then the .fcc code doesn't get interpreted
and all its code shows in the browser :

  <!-- SiteMinder Encoding=ISO-8859-1; -->
  @username=%USER%
  @smretries=3
  @smerrorpage=/siteminderagent/error.html
  <!-- My Custom Authentication Page Version : 1.1 --><html>

  <head>
  <title>My Company</title>

  etc.

The Web Agent traces reports also some errors lines :

WebAgentTrace.log

  [09/15/2016][08:55:18][17132][1734338304][CSmFormTemplateCache.cpp:226]
   [CSmFormTemplateCache::GetForm][][][][][][][][][][][Serving form template
   '/opt/CA/webagent/samples/forms/myauth.fcc' from disk.]
   
  [09/15/2016][08:55:18][17132][1734338304][CSmFormTemplateCache.cpp:269]
   [CSmFormTemplateCache::GetForm][][][][][][][][][][][Form template
   '/opt/CA/webagent/samples/forms/myauth.fcc' stored in cache.]
   
  [09/15/2016][08:55:18][17132][1734338304][SmFCC.cpp:1483][SmFcc::setup]
   [][][][][][][][][][][Error. No redirect target found in namespace.]
   
  [09/15/2016][08:55:18][17132][1734338304][CSmHttpPlugin.cpp:8788]
   [CSmHttpPlugin::ProcessAdvancedAuthResource][][][][][][][][][][]
   [unable to process FCC parameters. Returning SmNoAction.]

 

Environment

 

Web Agent 12.52SP1CR01 on Apache 2.2 on RedHat 6 64bit;

 

Cause

 

  The Custom Authentication .fcc file hasn't been completely
  internationalized, and as such, the Web Agent cannot interpret the
  code completely.

 

Resolution


  All Custom .fcc upgrade from 12SP3 to 12.52SP1 needs some adjustments.

  To override them, add to the ACO the Localization parameter, and give it the
  value "no" as per documentation (1).

  Also to localize the .fcc Custom Authentication Scheme, there are additional
  steps to have it run (2)

  To override the issue the time you need to adjust the .fcc page, do the following :

  - Stop the Web Agent;
  - In the Web Agent ACO, add the Parameter "Localization" with the value "No"
  - Start the Web Agent;

 

Additional Information

 

(1)

    Disable Internationalization to Use Customized FCCs from Upgraded
    Agents Versions Prior to 12.51

      [...]

      Warning

      Disabling agent internationalization prevents the use of all forms
      supplied with the new agent and disables all other agent
      internationalization features. For a longer term solution, we
      recommend migrating your existing FCCs to work on an
      internationalized agent and reenabling agent
      internationalization. For more information, see FCC
      Internationalization.

      8. Set the value of the parameter to No. (Default Value for
      Localization Parameter: Yes.)

    https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/siteminder/12-52-01/release-notes/installation-and-upgrade-considerations/web-agent-installation-and-upgrade-considerations.html
   

(2)

    FCC Internationalization

      8. Set the value of the parameter to No. (Default Value for
         Localization Parameter: Yes.)

    https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-identity-and-access-management/single-sign-on/12-8.html