This chapter describes the most important changes introduced in releases 11gR1, 11gR1 PS1, 11gR1 PS2, Oracle Identity Management 11gR1, 11gR1 PS3, Oracle Identity Management 11gR1 PS1, and 11gR1 PS5.
The features introduced in release 11gR1 PS5 include the following:
Encrypting credentials. For details, see Section 10.2, "Encrypting Credentials."
Trusted Header Assertion with the Oracle Access Manager Identity Assertion Provider. For details, see Chapter 15, "Introduction to Single Sign-On in Oracle Fusion Middleware" and Chapter 16, "Configuring Single Sign-On with Oracle Access Manager 11g".
Integrating application security with OPSS. For details, see Chapter 19, "Integrating Application Security with OPSS."
Developing applications using the Audit Service. For details, see Chapter 28, "Developing with the Audit Service".
Using the Identity Directory API in your applications. For details, see Chapter 26, "Developing with the Identity Directory API".
Administering the Keystore Service. For details, see Chapter 11, "Managing Keys and Certificates with the Keystore Service".
Developing applications using the Keystore Service. For details, see Chapter 27, "Developing with the Keystore Service".
Upgrading to PS5 with
upgradeOpss. For details, see Appendix G, "Upgrading Security Data."
Documentation updates include the following:
Updates to the discussion of the Common Audit Framework. For details, see Chapter 12, "Introduction to Oracle Fusion Middleware Audit Framework" and Chapter 13, "Configuring and Managing Auditing".
Procedures to enable SSL for the Identity Store Service. See Section 7.5.
The features introduced in Oracle Indentity Management 11gR1 PS1 include the following:
Oracle Entitlements Server, a tool that supersedes Oracle Authorization Policy Manager. For details, see Oracle Fusion Middleware Administrator's Guide for Oracle Entitlements Server.
The stand-alone audit loader.
The features introduced in release 11gR1 PS3 include the following:
Support for DB-based stores.
Support for the IBM WebSphere Application Server.
Support for identity virtualization, which allows querying multiple identity stores.
Support for security administrative scripts on IBM WebSphere Application Server.
The OPSS script
upgradeOpss to upgrade security data from 11gR1 PS1 or 11gR1 PS2 to 11gR1 PS3.
Additional OPSS scripts.
Improved Fusion Middleware Control security pages.
Enhanced OAMCfgTool for OAM 10g SSO, with additional parameters.
User and Role API support for IBM Tivoli and Microsoft ADAM directories.
The features introduced in Oracle Identity Management 11gR1 include the following:
Oracle Authorization Policy Manager, a tool to manage application security artifacts. The set of available tools to administer application security is expanded to Oracle WebLogic Administration Console, Oracle Enterprise Manager Fusion Middleware Control, WLST commands, and Oracle Authorization Policy Manager.
New material in this guide includes:
An appendix that lists all security-related WLST commands.
The features introduced in release 11gR1 PS2 include the following:
The Resource Catalog, a way of specifying resource types, resources, actions, and entitlements in an application policy grant. Starting with this release, OPSS supports resource-based policies with the introduction of the resource catalog.
Instructions for developing custom User and Role providers.
Use of the class ResourcePermission in permissions.
New WLST commands to manage resource types.
The system property
jps.deployment.handler.disabled of the Oracle WebLogic Server has been introduced.
A new use of the command
A new argument to the command
migrateSecurityStore to control the migration behavior upon encountering duplicate items. It applies only when migrating application policies.
The features introduced in release 11gR1 PS1 include the following:
The class Resource Permission.
Principal name comparison has been enhanced.
Manual settings for policy migration have been simplified. In particular, versioning the application is no longer required.
The WLST command
migrateSecurityStore supports the embedded LDAP store as a target.
The configuration of the identity store has been simplified. For example, previously required properties such as username.attr and login.name.attr are no longer needed when configuring an LDAP identity store.
The WLST command
reassociateSecurityStore supports an existing LDAP node as a target.
New and improved Oracle Fusion Middleware Control pages. In particular, using these pages, one can specify the SSO service to use in a domain.
The single most important new feature in the 11gR1 release is the introduction of the Oracle WebLogic Server as the environment where applications run and where security is provisioned.
The features introduced in release 11gR1 include the following:
Support for application policies and roles, and the authenticated and anonymous users and roles
Credential Store Framework
Auditing framework for Oracle Platform Security Services (OPSS) events for credential and policy management, and authorization checks
Support for application lifecycle security integrated with JDeveloper
Enhanced authorization framework
Consolidation of code-based and subject-based policies in system-jazn-data.xml
Management of security with Oracle Fusion Middleware and WLST commands
New security-related WLST commands
The features de-supported in release 11gR1 include the following:
Jazn is replaced with OPSS.
Jazn Realm API is replaced by the User and Role API.
Migration of OSDT toolkit from proprietary objects to JCE is desupported.
The identity store, as previously configured in system-jazn-data.xml, is replaced by the use of WebLogic authenticators.
The functions of Oracle Jazn Administration Tool are replaced as follows:
User and Role CRUD operations are replaced by the use of the Embedded LDAP configured and operated with the Oracle WebLogic Administration Console
The configuration of login modules is replaced with the use of the Oracle WebLogic Administration Console to configure authenticators
JavaSSO is no longer supported. On a Oracle WebLogic Server domain, Single Sign-On (SSO) is automatic within clusters only when session replication is turned on.
To upgrade from a previous release to the current, see any of the following documents: