By docteger on Jan 10, 2008
Charles Wesley, one of the QA engineers working on Federated Access Manager and related products, sent this procedure out to the firstname.lastname@example.org mailing list. This is the type of minutiae (in a good way) that is available on the list. Plus, you can ask questions specific to your deployment, get answers, and help to review the official docs. You can join the list here - but only if you have an account. Thanks Charles for giving me the opportunity to publicize the list and for this procedure - which only needed a little formatting in its move from email to blog. Configuring OpenSSO on an Instance of Web Server 7.x Owned by webservd When installed using the Java Enterprise System installer, Web Server 7.x creates a web server instance owned by the user
webservd. In Solaris 10,
webservdhas a home directory of
/by default. If OpenSSO is deployed to an instance owned by
webservdwith the default settings, the configuration will fail because the OpenSSO configurator will not create files under
/. Following is a simple procedure to allow configuration on a
webservd-owned web server instance to succeed.
- Create a new home directory for
- Change the ownership of the directory to owner
chmod -R webservd:webservd /export/home/webservd
/export/home/webservdas the home directory of
- Restart the web server instance on which OpenSSO will be deployed.
- Deploy the OpenSSO WAR.
- Configure the war file and enter
/export/home/webservdas the configuration directory that will be used by OpenSSO.