Oracle® Access Manager Developer Guide 10g (10.1.4.3) E12491-01 |
|
Previous |
Next |
This section describes new features of Oracle Access Manager release 10.1.4. This includes details for 10g (10.1.4.0.1), 10g (10.1.4.2.0), and 10g (10.1.4.3).
The following sections describe the new features in Oracle Access Manager that are reflected in this book:
Note: For a comprehensive list of all new features and functions in Oracle Access Manager 10.1.4, and a description of where each is documented, see the chapter on what's new 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.
The Oracle Access Manager 10g (10.1.4.3) software developer kit (SDK) for Windows continues to support .NET Framework 1.1 and Microsoft Visual Studio 2002. AccessGates created using this SDK continue this support.
A new and optional SDK for Windows is also provided which supports .NET version 2 and MSDE Visual Studio 2005. This 10g (10.1.4.3) SDK for .NET 2 is for use only to create custom AccessGates. It can be added to a 10g (10.1.4.3) deployment.
The chapter on the authorization plug-in API contains information on the ability to make an external call for data to be used in authorization. Ordinarily, authorization information flows from the Access Server to the AccessGate. An external call for data can obtain external authorization information that the AccessGate can send to the Access Server. This call does not return an error, however, if the returned value is null.
A note has been added to the section on the C API.
A cross-reference has also been added to information on GetRequestContext
in the section on managed code.
In the same chapter, information has been reorganized. The discussion of attribute and search parameters now appears before the discussion of functions.
Each version of a manual contains corrections if needed. In this guide, corrections with 10g (10.1.4.3) include the following:
Soap tags
Namespaces in Web Services Description Language (WSDL)
ObAnPluginFns with details of SetActionFn
The support features described in this section reflect the results of the Oracle Access Manager 10.1.4 globalization process with emphasis on multibyte support through the use of Unicode to enable processing of internationalized data and the impact on older environments that you upgrade.
Multibyte support and XML encoding
Identifies behavior with this and earlier versions and backward compatibility with encoding in requests and responses; examples are included.
Multibyte support and IdentityXML Functions and Parameters
Illustrates UTF-8 encoding for multibyte support in several examples
Multibyte support and IdentityXML
Identifies behavior with this and earlier versions and backward compatibility with XML pages, SOAP/IdentityXML requests, and Identity Event Plug-in data sent to executables.
Multibyte support and the Access Manager SDK, Access Manager APIs, Custom AccessGates
Identifies behavior with this and earlier versions and backward compatibility with the Access Manager SDK, Access Manager APIs, and custom AccessGates
Multibyte support and Custom C Authorization Plug-in Interfaces identifies behavior with this and earlier versions and backward compatibility with custom C authorization plug-ins and interfaces
Oracle Access Manager 10g (10.1.4.3) uses either Native POSIX Thread Library (NPTL) or LinuxThreads. The default mode is LinuxThreads for all but Oracle Access Manager Web components for Oracle HTTP Server 11g.
Note: On Linux, Oracle Access Manager Web components for Oracle HTTP Server 11g use only NPTL; you cannot use the LinuxThreads library. In this case, do not set the environment variable LD_ASSUME_KERNEL to 2.4.19. |
Information on using IdentityXML to create Web services has been updated.
Code samples has been provided and explained to illustrate how to use IdentityXML Web services to make calls to a WebPass.
Two samples have been added, to show how to create a Web service call when a WebPass is protected by a WebGate and when a WebPass is not protected by a WebGate.
Older information on creating a Java proxy object has been removed.
The chapter on IdentityXML functions and parameters contains new information on configuring challenge phrases and challenge responses. Other updates have been made to remove old information and to clarify the remaining information.
This chapter describes how to configure Add, Delete, Replace, and Replace_All operations on individual and multiple challenge-and-response pairs.
In the Identity Server globalparams.xml file, you can use the negativeListForEntityAttributes
parameter to identify specific attributes that are not read or cached during view and modify profile operations. With IdentityXML, a listed attribute can only be read and cached.
See Also:
|
The information on pre-6.5 IdentityXML syntax has been removed.
In the IdentityXML chapter, information has been reorganized. The discussion of attribute and search parameters now appears before the discussion of functions.
IdentityXML examples have been updated to reflect the post-6.5, WSDL-compatible syntax.
In the IdentityXML chapter, a new specification on who can search for deactivated users.
With Oracle Access Manager 10g (10.1.4.3), IdentityXML requests for gathering the attribute list pertaining to modifying a profile (modifyUser, modifyGroup, and modifyObject), no longer depend on a panel in the Identity System.
The code for WebGates has been rewritten so that WebGates and AccessGates share the same code base.
A new lazyload method has been added to the ObUserSession constructor in the Access Manager API as a result of this rewrite
New diagnostics have been added as a result of this rewrite.
New status codes have been added as a result of this rewrite.