Introduction

     Previous  Next    Open TOC in new window  Open Index in new window  View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Introduction and Roadmap

The following sections describe the content and organization of this document, as well as new features in AquaLogic Enterprise Security 2.2:

 


Audience and Scope

This document summarizes the features of the BEA AquaLogic™ Enterprise Security products and presents an overview of the architecture and capabilities of the security services. It provides a starting point for understanding the family of BEA AquaLogic Enterprise Security products.

The document is intended for all users of the BEA AquaLogic Enterprise Security product family, including:

The BEA AquaLogic Enterprise Security products incorporate many terms and concepts that are defined in the glossary. BEA recommends that you review the terminology to become familiar with the various terms and concepts.

 


Guide to This Document

This document is organized as follows:

 


Related Information

The BEA corporate web site provides all documentation for BEA AquaLogic Enterprise Security, including:

 


New and Changed Features in This Release

This release of AquaLogic Enterprise Security has several new and changed features.

Performance Statistics

The performance statistics feature enables the collection of authentication and authorization data for troubleshooting and performance analysis. The performance statistic feature is controlled by an auditing security provider, the PerfDBAuditor provider, which you configure and enable for each Security Service Module for which you want to gather statistics.

The performance statistics feature gathers the following information, for each SSM configuration ID and host name, aggregated for each time interval specified by the Performance Statistics Interval setting:

See Administration and Deployment Guide.

Web Services Client Authorization Cache

A client-side Authorization cache allows an application that is using the Web Services SSM to take advantage of in-process caching to achieve performance improvements when making authorization calls.

The Web Services Authorization cache is implemented as an Axis handler. The handler implementation allows you to add and remove the Authorization cache without affecting existing code. The Authorization cache can be configured through a Java API. If you do not use the configuration API to configure the cache, the default values for the cache are used.

See Programming Security for Web Services.

Authorization Through XACML

External applications can ask authorization questions through use of the XACML protocol. This capability is supported only in the Web Services SSM.

The XACML service is implemented as an extension to the existing Authorization Service in the Web Service SSM, and uses the same configuration and administration scripts of the Web Service SSM. The XACML service is silently installed together with the Web Service SSM.

See Programming Security for Web Services for additional information.

New Installation Features

This release of AquaLogic Enterprise Security includes a utility to help you upgrade from AquaLogic Enterprise Security 2.1. See Installing the Administration Server for additional information.

As of version 2.2 of ALES, the user who installs the Administration Server and SSMs does not require administrator privileges on a Windows platform, or root access on a Sun Solaris or Linux platform. The installation procedures set the file and directory permissions based on the user who runs the installer.

Support for Non-U.S.-English Locales

You can install the Administration Server and SSMs in non-US-English locales. If you install AquaLogic Enterprise Security on a machine that is part of a non-US-English locale, it is assumed that all other components with which AquaLogic Enterprise Security communicates will also be installed on the same non-US-English locale, including the policy RDBMS and the authentication source (LDAP or RDBMS).

WebLogic Server 9.x SSM Added

The WebLogic Server 9.x Security Service Module (SSM) integrates AquaLogic Enterprise Security with BEA WebLogic Server 9.1 and 9.2. This SSM uses a different security framework from the one used in the WebLogic Server 8.1 SSM and the other AquaLogic Enterprise Security SSMs. When you install the WebLogic Server 9.x SSM, AquaLogic Enterprise Security uses the WebLogic Server 9.x security framework. As a consequence, when you use the WebLogic Server 9.x SSM, you configure security providers in the WebLogic Administration Console, rather than in the AquaLogic Enterprise Security Administration Console. You still use the AquaLogic Enterprise Security Administration Console to create resources and to write security policies for all SSMs, and to configure providers in SSMs other than the WebLogic Server 9.x SSM. You must also use the AquaLogic Enterprise Security Administration Console to configure the deployment parent in the ASI Authorizer and ASI Role Mapper providers.

See Integrating ALES with Application Environments for additional information.

WebLogic 9.x Security Providers Supported

This release of AquaLogic Enterprise Security supports any of the WebLogic 9.x security providers. However, the Security Service Module for WebLogic Server 9.x is configured differently, as described in Integrating ALES with Application Environments.

You can also use the WebLogic Server 9.x WebLogicMBeanMaker to create any of the security provider types described in Developing WebLogic Security Providers.

Web Services SSM Now Supports Microsoft .Net and WebLogic Workshop 9.0 Clients

The Web Services SSM includes a set of examples that illustrate Web Services client development in different environments. The examples are located in BEA_HOME\ales22-ssm\examples. For this release, the following new examples are included:

ssmWorkshop

Demonstrates how to access the ALES Web Services SSM through its published WSDL in a WebLogic Workshop 8.1 or 9.x environment.

ssmNET

Demonstrates how to access the ALES Web Services SSM through its published WSDL in the .NET 1.1 or 2.0 environment.

WebLogic Portal 9.2 Integration Supported

This release of AquaLogic Enterprise Security allows you to integrate with WebLogic Portal 9.2 server and portal applications, resulting in an enhanced set of security services for use in protecting WebLogic Portal. AquaLogic Enterprise Security participates in the authoring and management of policy for WebLogic Portal resources. Once AquaLogic Enterprise Security is integrated with WebLogic Portal, you use AquaLogic Enterprise Security Administration Server to manage resources related to portal desktops, books, pages, and portlets.

See Integrating ALES With Application Environments for additional information.

AquaLogic Service Bus Integration Supported

This release of AquaLogic Enterprise Security allows you to integrate AquaLogic Service Bus 2.5. AquaLogic Service Bus 2.5 (ALSB) is a configuration-based, policy-driven Enterprise Service Bus. It facilitates a loosely coupled architecture, facilitates enterprise-wide reuse of services, and centralizes management. You can use AquaLogic Enterprise Security to manage access control to ALSB's runtime resources, using the ALES WebLogic Server 9.x Security Service Module.

ALES secures only the runtime resources of ALSB, in general those resources that ALSB passes to isAccessAllowed(); it does not secure the resources used during ALSB configuration, such as the ALSB console.

See Integrating ALES With Application Environments for additional information.

Additional Platforms Supported

This release of AquaLogic Enterprise Security supports the following additional platforms:

New Examples

This release of AquaLogic Enterprise Security includes the following new examples. Each example has a readme file that describes its function.

Adding Application Context from the BLM API

In this release of AquaLogic Enterprise Security, the BLM API has been enhanced to allow you to send an Application Context to the auditing service.

The following BLM API methods have been added to provide for the Application Context:


  Back to Top       Previous  Next