Issue:
We're running Web Agent, the login pages are not working. Instead the
source code comes up in the browser.
I think that the content-type is not set in the response.
How can I fix this ?
Resolution:
At first glance, there's a known issue when you upgrade the Web Agent
which is running on Apache.
- Check the configuration of the Apache server
and if you have AddHandler configuration, comment
them or remove them and restart Apache.
The AddHandler are usually :
AddHandler smformsauth-handler .fcc
AddHandler smsslformsauth-handler .sfcc
AddHandler smadvancedauth-handler .scc
AddHandler smcookieprovider-handler .ccc
Web Agent on Apache shows @username=%USER% @smretries=0 @smheaders=sm_sdomain from login.fcc
https://comm.support.ca.com/kb/web-agent-on-apache-shows-username-user-smretries-0-smheaders-sm-sdomain-from-login-fcc/KB000075015
Tech Tip : CA Single Sign-On : Web Agent on Apache shows @username=%USER% @smretries=0 @smheaders=sm_sdomain from login.fcc
https://communities.ca.com/thread/241795548-tech-tip-ca-single-sign-on-web-agent-on-apache-shows-usernameuser-smretries0-smheaderssmsdomain-from-loginfcc
- If the .fcc page is customized, add to the ACO the Localization
parameter, and give it the value "no".
After Web Agent upgrade from 12SP3 to 12.52SP1, the .fcc page shows its code instead of the login page.
https://comm.support.ca.com/kb/after-web-agent-upgrade-from-12sp3-to-1252sp1-the-fcc-page-shows-its-code-instead-of-the-login-page/kb000046714
Tech Tip : CA Single Sign-On : After Web Agent upgrade from 12SP3 to 12.52SP1, the .fcc page shows its code instead of the login page.
https://communities.ca.com/thread/241770220-tech-tip-ca-single-sign-on-after-web-agent-upgrade-from-12sp3-to-1252sp1-the-fcc-page-shows-its-code-instead-of-the-login-page
Insure that the Apache version is still supported with the new Web
Agent version.
KB : KB000098074