Federation Manager Guide › Federation Manager Installation › Virtual Host Configuration for Federation Manager

Virtual Host Configuration for Federation Manager

You can define multiple virtual hosts for Federation Manager. Virtual hosts can be useful for testing purposes because they allow you to install the asserting and relying party on the same system. Defining multiple virtual hosts also lets you configure SAML 2.0 IdP Discovery profile, using a separate host name and domain for the discovery service.

To define multiple virtual hosts, Federation Manager requires the following configuration setup:

• Add a host to the hostnames parameter in the server.conf file. The server.conf file is in the following directory:

  federation_mgr_home\secure-proxy\proxy-engine\conf.

• If Federation Manager is operating on the same system from which you access the Federation Manager UI or where you run a federation transaction, update the httpd.conf file. The httpd.conf file is in the directory federation_mgr_home\secure-proxy\httpd\conf.

  Note: If SSL is enabled for the embedded web server, make the following changes in the httpd-ssl.conf file also. The httpd-ssl.conf file is in the directory federation_mgr_home\secure-proxy\httpd\conf\extra folder.

  Update the httpd.conf file based on the system type you have as follows:

  • For IPV4 based systems, add a LISTEN directive as follows:

    LISTEN 127.0.0.1:port

  • For dual stack systems with IPv4 and IPv6 support, add LISTEN directives as follows:

    LISTEN 127.0.0.1:port

    LISTEN [::1]:port

  • For IPv6 systems, add a LISTEN directive as follows:

    LISTEN [::1]:port

  Additionally, in the hosts file of the system, update the loopback address entry so the new host name is added to it. The values are:

  • IPv4: 127.0.0.1
  • IPv6: [::1]