Technical data

Multiple Single Sign-On Middle Tiers with One Oracle Internet Directory
3-6 Advanced Topologies for Enterprise Deployments
2.
Use the Administer Partner Applications page to delete the existing entry for the
partner application sso1.mydomain.com.
3. Set the environment variable ORACLE_HOME to point to the Oracle home for
sso1.mydomain.com. Include $ORACLE_HOME/jdk/bin in the PATH variable.
4. Run the registration script. For the URLs, be sure to substitute values appropriate
for your installation. The script creates a partner application called
sso.mydomain.com.
$ORACLE_HOME/jdk/bin/java -jar $ORACLE_HOME/sso/lib/ossoreg.jar
-oracle_home_path orcl_home_path
-site_name site_name
-config_mod_osso TRUE
-mod_osso_url mod_osso_url
-u userid
[-virtualhost virtual_host_name]
[-update_mode CREATE | DELETE | MODIFY]
[-config_file config_file_path]
[-admin_id adminid]
[-admin_info admin_info]
For a description of command parameters, please see "Registering mod_sso" in
Chapter 4 of the Oracle Application Server Single Sign-On Administrator’s Guide.
To reregister mod_osso on sso2.mydomain.com:
1. On the computer sso2.mydomain.com, log in to the single sign-on administration
pages as the single sign-on administrator. Be sure to log in to
http://sso.mydomain.com/pls/orasso.
2. Use the Administer Partner Applications page to delete the existing entry for the
partner application sso2.mydomain.com.
3. Create a clear text osso.conf file using the following steps:
a. Click the Edit Partner Application Page for sso.mydomain.com.
b. On the Edit Partner Application page, make a note of the parameters sso_
server_version, cipher_key, site_id, site_token, login_url,
logout_url, and cancel_url. You will use the same values that you used
when you registered the application on sso1.mydomain.com. The idea is to
maintain the same site id, site token, and cipher key between both middle
tiers. This enables these servers to act as clones of each other.
c. Create the osso.conf file, using a text editor:
sso_server_version=v1.2
cipher_key=encryption_key
site_id=id
site_token=token
login_url=http://sso.mydomain.com/pls/orasso/orasso.wwsso_app_admin.ls_
login
logout_url=http://sso.mydomain.com/pls/orasso/orasso.wwsso_app_admin.ls_
logout
cancel_url=http://sso.mydomain.com:80/
4. Log in to sso2.mydomain.com as root; then navigate to the osso.conf file that
you created in Step 3. Obfuscate the file:
$ORACLE_HOME/Apache/Apache/bin/iasobf osso.conf $ORACLE_HOME/Apache/Apache/
conf/osso/osso.conf