Oracle® Access Manager Access Administration Guide 10g (10.1.4.0.1) Part Number B25990-01 |
|
|
View PDF |
This section describes new features of Oracle Access Manager 10g (10.1.4.0.1) and provides pointers to additional information within this book. Information from previous releases is also retained to help those users migrating to the current release.
The following sections describe the new features in Oracle Access Manager that are presented in this book:
Triggering Authentication Actions After the ObSSOCookie Is Set
Associating WebGates with Specific Virtual Hosts, Directories, and Files
Note: For a comprehensive list of new features and functions in Oracle Access Manager 10g (10.1.4.0.1), and a description of where each is documented, see the chapter on What's New in Oracle Access Manager in the Oracle Access Manager Introduction. |
The original product name, Oblix NetPoint, has changed to Oracle Access Manager. Most component names remain the same. However, there are several important changes that you should know about, as shown in the following table:
All legacy references in the product or documentation should be understood to connote the new names.
WebGates have been updated to use the same code as the Access System, and WebGate configuration parameters that once existed in WebGateStatic.lst have been moved to the Access System user interface.
After installing the new WebGates, you can now configure such parameters as IPValidation and IPValidationExceptions from the Access System GUI. The WebGateStatic.lst file no longer exists.
WebGates can work behind a reverse proxy.
Information on setting up a WebGate behind a reverse proxy has been added to this book.
The documentation on URL prefixes and patterns has been updated for clarity.
WebGates can work behind a reverse proxy.
Information on setting up a WebGate behind a reverse proxy has been added to this book.
You can cause authentication actions to be executed after the ObSSOCookie is set.
Typically, authentication actions are triggered after authentication has been processed and before the ObSSOCookie is set. However, in a complex environment, the ObSSOCookie may be set before a user is redirected to a page containing a resource. In this case, you can configure an authentication scheme to trigger these events.
Information has been added about the differences between configuring a form on the server where the WebGate resides and configuring it on a server other than the one hosting the WebGate.
It is no longer necessary to disable an authentication scheme before you modify it.
You can configure an authentication scheme that allows the user to log in for a period of time rather than a single session.
You can configure the Oracle Access Manager single sign-on logout URL to point to a logout.html
file in the language of the user's browser.
A section has been added on creating custom single sign-on logout URLs and logout pages.
You can configure the WebGate to only work with specific virtual hosts, directories, and files.
Information on troubleshooting that was dispersed throughout this manual has been consolidated in a separate appendix.