SiteMinder Access Gateway : Different hostname pointing to Access Gateway's apache.

Products

• SITEMINDER

Issue/Introduction

Query

Is it possible to access the Access Gateway using different hostname over the default ports.

Environment

R12.8.x

Cause

Customer has requirement to access Access Gateway's Apache using different hostnames.

Sample Hostname : host1. example.com , host2.example.com

Resolution

There are ways to configure the Access Gateway's Apache to use different hostname for instance app1.example.com and app2.example.com.

Option 1 : Use the SAN Certificate (Subject Alternative Name) which includes  all the server names to access Access gateway.

Theatrically this is possible from Apache configurations perspective and Here is a way you can try configuring with server name indication(SNI) , which Apache allows you to configure this SNI using different configuration files for different hostname and also with wildcard certificate.

https://www.digicert.com/kb/ssl-support/apache-multiple-ssl-certificates-using-sni.htm

Option 2. Use SAN certificate's with two subject name of the server in single certificate to manage the setting the passphrase in the spsapachessl.properties file but this you need to perform a POC before production deployment / changes.

Option 3 : Install another instance of Access Gateway on the same server with different port for Apache to avoid port conflicts with default Access Gateway instance and you can request app1.example.com for default domain and app2.example.com for another instance of Access Gateway is possible.

Note  : All the above use cases needs to be test before implementing in higher environments.