Hi Chris, Darren and Eva,
As I have clarified, the direct access approach is the preferred approach
by the client.
So we would need to access the self-service console from the Internet
directly using a external FQDN that has been added to the DNS system, and
mapped to a public IP address of the RSA server.
We have two RSA instances, one for primary and another for replica:
A secondary NIC has been configured on the VMWare server for each of the
RSA appliances, and public IPs have been assigned to that secondary NIC as
you can see below:
In the RSA network configuration, the second NIC has been connected and
enabled with the public IP address. But the fully qualified domain name of
the primary appliance is still the private FQDN of the appliance, this is
the result of the initial installation and configuration:
Our problem now is:
When we access the self-service console from Internet using the
https://external-fqdn/ssc, we can get to the self-service console
directly, meaning hitting the secondary NIC of the RSA server, but the
redirect URLs will always contain the private FQDN with the machine name
in it, this is not what we want. We want the redirect URLs only contain
the external FQDN because it can be recognized from the Internet.
Please suggest what configuration changes we should make to achieve the
result we want.
Thanks,
Xiao-Li Ding
Information Security Consultant and IT Architect
MS in Computer Science, CISSP, CISA, MBA
IBM Security Services, NA
xding@us.ibm.com
.................................................................................................
Links: IBM Security | Data Security | Emergency Response |
