This KB includes instructions on how to verify the version of Apache HTTP Server running on the Siteminder Access Gateway Server.
PRODUCT: Siteminder
COMPONENT: Access Gateway Server
VERSION: Any
OS: Linux and Windows
Siteminder Access Gateway ships bundled with with an instance of Apache HTTP Server. Periodically, Comm Vulnerabilities and Exposures (CVE's) are published which address various web server and application servers, such as Apache HTTP Server. You will need to be able to compare the visions published in the CVE's with the version installed on the Siteminder Access Gateway Server.
Here are steps to determine which version of Apache Tomcat is running on a Siteminder Access Gateway Server
WINDOWS
OPTION #1: Command Line
1) Open a command-prompt (cmd.exe) with elevated privileges (Run As Administrator)
2) Change to the following directory
<Install_Dir>\CA\secure-proxy\httpd\bin\
<Install_Dir> = Root drive and path to the Siteminder Access Gateway installation
Default: C:\Program Files\CA\secure-proxy\
3) Run the following command:
apachectl -V
OPTION #2: File Explorer
1) Open Windows File Explorer
2) Change to the following directory
<Install_Dir>\CA\secure-proxy\httpd\bin
<Install_Dir> = Root drive and path to the Siteminder Access Gateway installation
Default: C:\Program Files\CA\secure-proxy\
3) 'Right-click' the following executable and select 'properties'
httpd.exe
4) In the Properties window, select the 'Details' tab
5) Review/record the value in the "Product Version" and/or "File Version" properties. This is the version of Apache HTTP Server.
LINUX
Using 'apachectl' to Determine Version of Apache HTTP Server
1) Change to the following directory
<Install_Dir>/CA/secure-proxy/httpd/bin/
<Install_Dir> = Root drive and path to the Siteminder Access Gateway installation
Default: /opt/CA/secure-proxy/
2) Run the following command:
./apachectl -V
Using 'httpd' to Determine Version of Apache HTTP Server
1) Set the Siteminder Access Gateway Environment Variables
a) Change to the following directory
<Install_Dir>/CA/secure-proxy/
<Install_Dir> = Root drive and path to the Siteminder Access Gateway installation
Default: /opt/CA/secure-proxy/
b) Run the Access Gateway Environment Variable Script:
. ./ca_sps_env.sh
2) Change to the Apache HTTP Server Installation Directory
<Install_Dir>/CA/secure-proxy/httpd/bin
3) Run the following command:
./httpd -V
RESULT: You should get output similar to the following:
Server version: Apache/2.4.58 (Unix)
Server built: Mar 5 2024 05:14:15
Server's Module Magic Number: 20120211:129
Server loaded: APR 1.7.4, APR-UTIL 1.6.3, PCRE 8.45 2021-06-15
Compiled using: APR 1.7.4, APR-UTIL 1.6.3, PCRE 8.45 2021-06-15
Architecture: 64-bit
Server MPM: worker
threaded: yes (fixed thread count)
forked: yes (variable process count)
Server compiled with....
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_PROC_PTHREAD_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D DYNAMIC_MODULE_LIMIT=256
-D HTTPD_ROOT="/tmp/apache/httpd-2.4.58/Release/"
-D SUEXEC_BIN="/tmp/apache/httpd-2.4.58/Release//bin/suexec"
-D DEFAULT_PIDLOG="logs/httpd.pid"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="conf/mime.types"
-D SERVER_CONFIG_FILE="conf/httpd.conf"