|Oracle® Application Server Single Sign-On Administrator's Guide
Part Number B15988-01
This section describes new features of the OracleAS Single Sign-On 10g (10.1.4.0.1) and provides pointers to additional information. Information from previous releases is also retained to help those users migrating to the current release.
The following sections describe the new features in OracleAS Single Sign-On that are presented in this book:
Configuring Custom (Deployment-Specific) Pages
Changes to the Syntax for Invoking OracleAS Single Sign-On
Changing the Single Sign-On Administration Group
Elimination of the Database Access Descriptor (DAD)
Protecting URLs in the Absence of a Load Balancer
Information on Authentication Levels
Login Page Error Codes
Configuring Single Sign-On Server for Multiple Realms
Configuring SSL for Partner Applications
Debug Log Files
URLs to Protected Resources Fail to Return the Resource
Secure Transmission of mod_osso Cookies
Obsolete Error Messages
You can implement federated authentication using Oracle Application Server Single Sign-On and Oracle Identity Federation. Federated single sign-on permits users to access information on different corporate Web sites while authenticating to only one of those sites. You can configure either Oracle Application Server Single Sign-On or Oracle Identity Federation to be the authentication mechanism for users who want to access resources that are protected by either product.
The WWSSO_LS_CONFIGUATION_INFO$ table is no longer required for the single sign-off page.
You can configure custom login pages for external applications.
See Also:"Installing Deployment-Specific Pages".
The syntax for invoking OracleAS Single Sign-On has been simplified. For example, instead of accessing the administration home page by typing the following URL:
You can now use the following:
The steps for this procedure have changed.
This information for this has been updated. Pointers have been added to additional information.
See Also:"Configuring Globalization Support".
This table no longer is needed and has been removed.
See Also:"Troubleshooting an Inaccessible Server".
The syntax for this operation has changed.
Information on authentication levels has been expanded.
See Also:"Authentication Levels".
Information on login page error codes has been updated.
Information on the authentication URL has been updated.
This procedure has changed.
Information has been added about configuring SSL for partner applications (including OracleAS Single Sign-On).
A note has been added to notify users that debug log files should not be deleted when OC4J is running.
A note has been added regarding some browsers' limitations regarding URL length. For some situations, configuring mod_osso to use the POST method instead of the GET directive can be an effective work-around.
See Also:"URL Exceeds Maximum Length".
A section has been added regarding adding the OssoSecureCookies directive to ensure that cookies are transmitted using HTTPS.
See Also:"Secure Transmission of mod_osso Cookies".
The error, "Forbidden Error When Accessing OracleAS Single Sign-on Administration" is now obsolete, as are all Type 41400 errors.
See Also:"Troubleshooting OracleAS Single Sign-On".