This section contains the following topics:
Add Agent Configuration Parameters for SiteMinder Agent for IIS Manually (CQ 135135)
User Account Control Dialog Appears when Installing SiteMinder Components (135417)
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)
Web Agent Installation May Fail with Older Linux Kernels (54534)
Agent Logs from r12.0 SP3 CR04 still show CR03 after Upgrade
r12.0.3.09 Agents for IIS with ARR in Classic Pipeline Mode not Prompting for Credentials (154054)
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.
Symptom:
When I run the installation program for a SiteMinder component, the User Account Control dialog appears.
Solution:
This issue relates to the Windows operating environment. This issue occurs on all SiteMinder products. The User Account Control dialog appears in any of the following situations:
Web Agents that are configured to act as 4.x Agents do not support IPv6 addresses. For example, if you configure an r12.0 SP3 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.
|
Copyright © 2012 CA.
All rights reserved.
|
|