Web Agent 12.52 SP1 CR11: Web Agent Configuration NOT detecting Apache

Products

• CA Single Sign On Agents (SiteMinder)
• SITEMINDER

Issue/Introduction

 

The Web Agent 12.52SP1CR11 configuration wizard does not detect Apache 2.4 (64-bit) web server on Windows Server even if the Apache registry entry resides.

 

Environment

 

Web Agent 12.52SP1CR11 for Windows

 

Resolution

 

In CR11, register Apache as a service with the name "Apache2.4" in the machine at first. And then, Web Agent Configuration Wizard will detect the Apache. No registry entry is needed now.

For example, run the command such as following:

C:\Apache24\bin> httpd.exe -k install -n "Apache2.4"

Note: confirm if the service is successfully installed to run the below command:

C:\Apache24\bin> sc qc Apache2.4 

 

 

Another method if this one above leads to problem:

IMPORTANT: This article contains information about modifying the registry.

Before modifying the registry, create a backup of the registry and ensure the understanding on how to restore the registry if a problem may occur.

The Web Agent configuration wizard uses the Windows registry to locate the Apache servers root directory.

To do this, the configuration agents code tries to directly access HKEY_LOCAL_MACHINE\SOFTWARE\Apache Group\Apache and look for supported version numbers in the registry.

Because it utilizes this method, several potential problems can arise:

1. The registry path could be invalid.
   
   By default, the code looks in HKEY_LOCAL_MACHINE\SOFTWARE\Apache Group\Apache or HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Apache if path doesn't exist the configuration wizard won't find the servers.
   
   This could happen through either:
   
   - An Administrator deleting the registry branch.
   - An alternate name being used for this registry branch;
   
   
2. The ServerRoot registry entry could be missing
   
   If the ServerRoot registry entry has been renamed, or is missing the configuration wizard will be unable to determine Apache's location.
   
   
3. The ServerRoot registry entry could be pointing to an invalid path
   
   If the Apache web server root has been moved without updating the value stored in ServerRoot Siteminder will detect the path is invalid and subsequently ignore it.

To resolve these problems, create the following registry entries:

• Create a new key called Apache Group under HKEY_LOCAL_MACHINE\SOFTWARE\;
• Under the Apache Group key that has just been created, create a new key named after the Apache version number (for example 2.4.58 for 2.4.58);
• Under the version numbered key that has just been created, add a dword value called shared the value should be 1;
• Under the version numbered key that has just been created, add a string value called ServerRoot the value should contain the full path of the Apache server root, for example C:\Program Files\Apache Group\Apache2\

After making these changes, attempt to run the web agent configuration wizard again, no server restart is necessary.