Dependencies of a VirtualHost on the Infrastructure (SSO Server)

The next step is to ensure the SSO configuration is working correctly. Below is

some information regarding the Single Sign-On configuration, which will be important

to look at:

    ORASSO Schema (WWSEC_ENABLER_CONFIG_INFO$)
    virtualname:port
    http://virtualname:port/pls/orasso/orasso.wwsso_app_admin.ls_login
    
    The SSO Server (orasso)
    http://virtualname:port/pls/orasso/orasso.wwsso_home.process_signon
    http://virtualname:port/pls/orasso/orasso.wwsso_app_admin.ls_login
    http://virtualname:port/pls/orasso/orasso.home
    http://virtualname:port/pls/orasso/orasso.wwsec_app_priv.logout

Reference:

Note:244112.1 Capture Single Sign-On orasso Schema Tables

   

We need to get rid any occurrences of an old name, or the machine name,

and replace it with the virtual name and port. For simplicity sake, lets

assume that you only want one virtual host on the Infrastructure (or IM home).

That means no virtual host configuration is needed in the httpd.conf. You

just change the ServerName parameter, and re-register the http server with SSO,

and don't use the the virtualhost flag as an ossoreg.jar parameter.

 

Note 1:

You don't need to change anything on the Infrastructure unless implementing SSL

with SSO, or desire a different ServerName for the SSO Server.

 

Note 2:

If using SSL, the use of the ssl.conf will mean using a Virtual Host for the

SSL configuration. See the documentation listed below for a Mid-Tier if

VirtualHosts *are* desired on the Infrastructure. Then, follow #6-10 to

re-configure the SSO Server. Note that you can configure ONE Virtual Host,

and modify the global Servername to be the same value.

 

We will first discuss the easiest method to configure one non-ssl virtual host

on the Infrastructure to differentiate the SSO steps from the other steps:

   

    ACTIONS

    -------

   

    1. In the httpd.conf, editing with Application Server Control:

       

       change this:

       ServerName machinename.domain.com

       to this:

       ServerName 

Note:

       This assumes that "virtualname" resolves to the IP Address of that box.

       However, its not important on the initial request, as the HTTP Server

       will respond when the IP address is requested. The Servername parameter

       come into play when setting the appropriate response headers, along with

       the Port parameter.

   

    2. Ensure theres no added "VirtualHost" configuration in the httpd.conf.

 

    3. Now is the time to change the Listen and Port parameter to a desired port(s).

      

    4. Restart the HTTP_Server.

   

    5. Test access:

       http://virtualname:port/

    6. Configure SSO with the new URL parameters:

       $ORACLE_HOME/sso/bin/ssocfg.sh http virtualname 7777

This *always* needs to be done when changing the protocol, host, or port)

   

    7. Ensure OID is properly configured:

   

       Open the OID Directory Manager, and do the following:

   

       Login using the orcladmin account.

       Expand the tree:

Entry Management
         cn=OracleContext
           cn=Products
             cn=DAS

Select the cn=OperationURLs page, do not expand the tree, just click on

      the cn=OperationURLs page.  The right hand pane will display a number of

      fields or attributes. The last field will be orcldasurlbase and will

      should be set to the Infrastructure HTTP Server and port. Change this

      entry to reflect the new name and port. e.g. http://virtualname:port.

      (this is stated just as a "url" desired, so do not include port 80

       or 443).

   

   

    8. See this Note to refresh the OID cache:

    

       Note:292380.1 How to Refresh Cache for OID Parameters

   

    9. Re-register the Infrastructure OHS with SSO...

   

       - Set $ORACLE_HOME and environment to the Infrastructure directories.

       - Ensure you are using the Java which came with the installation,

         using the command, "which java".

   

       Paste this into a plain text file, and make it all one line, changing

       appropriately, for your configuration,  then paste into the command line:

   

       $ORACLE_HOME/jdk/bin/java -jar $ORACLE_HOME/sso/lib/ossoreg.jar
       -oracle_home_path 
       -site_name  \
       -config_mod_osso TRUE \
       -mod_osso_url http://virtualname:port
       -u oracle  \ # since oracle user starts ohs

       Sometimes needed:
       -ssoDBConnect :1521:asdb
       -pass 

The goal is to set the proper URL. Since the VirtualHost *is* the Servername,

      we don't need the -virtualhost flag, and this registration will set the

      default osso.conf obfuscated file.

   

    10. Restart the http server

          Hopefully, this has been "10 steps to get the Infrastructure working with a Virtual Host"

          Test it only on the Infrastructure:

        http://virtualname:port/pls/orasso/ --> log in and out as orcladmin
        http://virtualname:port/oiddas/ --> log in and out as orcladmin

        Don't continue until this works. Once this works, you can configure

        VirtualHosts on the Mid-tier, and get Portal to work with them. If

        desiring multiple virtual hosts, or configuring SSL, configure the

        Infrastructure as if it were a Mid-Tier, (with instructions below),

        and then follow #6-10, above. Note that you can configure ONE Virtual

        Host, modify the global Servername (and Port) to be the same value,

        and everything should work fine. These are the sole dependencies. If

        using multiple Virtual Hosts, or enable the SSL Virtual Host, there

        are more dependencies.

^^^major checkpoint 2^^^

Note: In version 10.1.2.x, the documentation was greatly improved to include all

steps to configure dependencies after changing a name or port value. A good place

start is the following Oracle Documentation:

 

   Oracle Application Server Administrator's Guide 10g Release 2 (10.1.2)

   http://download.oracle.com/docs/cd/B14099_19/core.1012/b13995/toc.htm

   "4 Managing Ports"

 

   Usually, its a port change is performed one Oracle home at a time...

  

      By default, Infrastructure or Identity Management home:

      "4.4.3 Changing the HTTP Server Port on an Identity Management Installation"

http://download.oracle.com/docs/cd/B14099_19/core.1012/b13995/ports.htm#i1039402

While configuring a VirtualHost is not necessarily changing the port, it could be.

   The same steps are required when changing the protocol, name, or port to access

   the SSO Server.