This section contains the following topics:
SAML 1.1 Artifact Transaction Failing with SSL Exception [167393]
Web Agent Installation on Non-English Locale
User Account Control Dialog Appears when Installing CA SiteMinder® Components (135417)
Add Agent Configuration Parameters for CA SiteMinder® Agent for IIS Manually (CQ 135135)
IPv6 Addresses Not Supported by Web Agents Configured as 4.x Agent Types (65071)
Web Agent Installation Fails on 64-bit Linux (63714, 62738)
Multiple obj.conf Files and nete-wa-config (18615, 56424)
Uninstall Program Displays Debug Information on z/OS Systems
Symptom:
If the local character "ì" is entered as input to the Web Agent Configuration wizard in console more, it is not recognized. If you enter it and return to the previous page it is shown as a question mark character ("?").
The is caused by the underlying JVM, which does not recognize and support the "ì" character. Oracle is aware of the issue.
Solution:
Run the configuration wizard in GUI mode or change the name of the trusted host and host configuration objects so that they do not include the "ì" character.
Symptom:
On non-English locales, unattended mode agent installation can sometimes result in a "Bad string" error message.
Solution:
Ignore the error message. The installation completes successfully.
Symptom:
The SunOne 6.1 web server does NOT support the necessary AES ciphers required for FIPS ONLY. This limitation prevents the artifact profile federation from working over SSL.
Solution:
We suggest upgrading to new newer SunOne 7 web server.
Installing a web agent silently on a non-English locale shows a "Bad string" error message, however the installation completes successfully.
Symptom:
When I run the installation program for a CA SiteMinder® component, the User Account Control dialog appears.
Solution:
This issue relates to the Windows operating environment. This issue occurs on all CA SiteMinder® products. The User Account Control dialog appears in any of the following situations:
Symptom:
I cannot find the new Agent for IIS configuration parameters in the following Agent Configuration Object template:
IISDefaultSettings
Solution:
Add the following parameters manually to your existing Agent Configuration Objects:
Note: For more information, see the Web Agent Configuration Guide.
Web Agents that are configured to act as 4.x Agents do not support IPv6 addresses. For example, if you configure an 12.52 Web Agent to operate as a 4.x Web Agent, then this Web Agent will not support IPv6 addresses.
Note: To configure 4.x Web Agent support, select the Supports 4.x Agents check box in the Administrative UI.
Symptom:
I cannot install a Web Agent on my server that runs on a 64-bit Linux system.
Solution:
Install the following patches:
Symptom:
Prior to Sun ONE/Sun Java System v6.0, all configuration information went into a single obj.conf file. For Sun ONE/Sun Java System v6.0, the mechanism to configure virtual servers changed. You can configure one or more new classes, and virtual classes in the instance.
By default, a new server instance has one virtual server class, named default class, whose configuration file is obj.conf.
Each additional class in the instance has an administrator-assigned name. The process of creating a new class and a virtual server within the class in the instance creates an associated configuration file, named new_class.obj.conf, by default. Normally, new_class is the name of the virtual server class, but you can configure the server to use a different name. The mappings between the configuration files and virtual server classes is done in the server.xml file.
Running the Web Agent configuration script, ca-wa-config, updates the obj.conf file; however, the AuthTrans, NameTrans, and PathCheck directives, and Service lines, are not written into new_class.obj.conf files.
Solution:
Update a new_class.obj.conf file manually, by copying the AuthTrans, NameTrans, and PathCheck directives, and Service lines, from obj.conf to the top section of new_class.obj.conf.
Note: To find these lines easily, you can run a "diff" program on the obj.conf and newclass.obj.conf files after running the Agent configuration script.
Symptom:
On z/OS systems, the CA SiteMinder® Agent uninstall program erroneously displays debug information.
Solution:
Ignore the debug information. The information does not affect the uninstall operation.
|
Copyright © 2013 CA.
All rights reserved.
|
|