If you use Security Enhanced Linux (SELinux) to protect the Apache Web Server, you must set the security context for all of the Web Agent shared libraries to the same value as those used by other Apache Web Sever modules. To do this, use ls -Z to determine the security context, then use chcon to set the security context. For example:
where RSAWebAgentInstallPath is the location where you installed the Web Agent.
You also need to make sure that the security context allows the Apache Web Server to read and write to the sdconf.rec and sdstatus.12 files. Do this by either changing the location of the sdconf.rec and sdstatus.12 files from the default location, $VAR_ACE, to a location where read/write access is allowed (for example, the log directory), or change your policy to allow read/write access to $VAR_ACE.
If you are setting up multi-domain authentication, you must use the same WebID URL across all web servers. When using IIS web servers and Apache web servers, change the WebID URL on the Apache servers to /WebID/IISWebAgentIF.dll. For more information, see the Installation and Configuration Guide.
For security purposes, instruct end users to disable caching in their browsers.
Tracking Number: 16432 Problem: If you log on to a protected web site, then attempt to access a different page of the web site after the initial cookie expires, you must reauthenticate. This happens because the refresh cookie generated by the Web Agent after the initial cookie expires is not detected by the Apache Web Server software.
RSA and the RSA logo are registered trademarks of RSA Security Inc. in the United States and/or other countries. For the most up-to-date listing of RSA trademarks, see www.rsasecurity.com/legal/trademarks_list.pdf. EMC is a registered trademark of EMC Corporation. All other goods and/or services mentioned are trademarks of their respective companies.