Sun Microsystems 819468310 manual Web Service Security, Single Access Manager WAR file deployment

Page 7

What’s New in This Release

devices, applications, and service-driven networks. Typical uses of the JMX technology include: consulting and changing application configuration, accumulating statistics about application behavior, notification of state changes and erroneous behaviors. Data is delivered to centralized monitoring console.

Access Manager 7.1 uses the Java ES Monitoring Framework to capture statistics and service-related data such as the following:

Number of attempted, successful, and failed authentications

Policy caching statistics

Policy evaluation transaction times

Web Service Security

Access Manager 7.1 extends authentication capabilities to web services in the following ways:

Inserts tokens to outgoing messages

Evaluates incoming messages for security tokens

Enables point-and-click selection of Authentication providers for new applications

Single Access Manager WAR file deployment

Access Manager includes a single WAR file you can use to deploy Access Manager services consistently to any supported container on any supported platform. The Access Manager WAR file coexists with the Java Enterprise System installer which deploys multiple JAR, XML, JSP, HTML, GIF, and various properties files.

Enhancements to Core Services

Web Containers supported

Sun Java System Web Server 7.0

Sun Java System Application Server 8.2

BEA WL 8.1 SP4

IBM WebSphere 5.1.1.6

Monitoring Framework Integration

Access Manager can use the JES Monitoring Framework to monitor the following:

1.Authentication

Number of authentications attempted

Number of remote authentications attempted (optional)

Sun Java System Access Manager 7.1 Release Notes

7

Image 7
Contents Sun Java System Access Manager 7.1 Release Notes 070301@16599 Contents Contents Sun Java System Access Manager 7.1 Release Notes Java ES Monitoring Framework Integration About Sun Java System Access ManagerRevision History What’s New in This ReleaseSingle Access Manager WAR file deployment Web Service SecurityEnhancements to Core Services Authentication module Service Management module Deprecation Notification and Announcement Hardware and Software RequirementsHardware and Software Requirements RAM Supported BrowsersGeneral Compatibility Information Upgrade not supported for Access Manager Hpux versionConfigure NowInstallation Option in Text-Based Mode Access Manager Legacy ModeJava ES Silent Installation Using a State File Configure NowInstallation Option in Graphical ModeConfigure LaterInstallation Option Access Manager Policy AgentsDetermining the Access Manager Mode Compatibility Issues Known Issues and LimitationsInstallation Issues Upgrade IssuesKnown Issues and Limitations Workaround None Configuration Issues Data validation for required attributes in the services Access Manager Console Issues Command Line Issue Clients do not get notifications after the server restarts SDK and Client IssuesAuthentication Issues SDK clients need to restart after service schema changeApplicationuser Using HttpSession with third-party web containers Session and SSO IssuesServer Startup Issues Policy IssuesDebug error occurs on Access Manager startup 6309274 Error displayed when performing AMIdentity.modifyService Amsdk IssuesGroup members dont show up in selected list SSL Issue Clientsdk samples directory contains unwanted makefile Samples IssueLinux OS Issues Amconfig script fails when SSL certificate is expiredFederation and Saml Issues Windows and HP-UX IssuesFederation fails when using Artifact profile Globalization g11n IssuesLogout error occurs in Federation Removing UTF-8 is not working in Client Detection Document unused properties in the AMConfig.properties file Documentation IssuesDocument how to enable XML encryption Redistributable Files Documentation UpdatesAdditional Sun Resources How to Report Problems and Provide FeedbackSun Welcomes Your Comments Related Third-Party Web Sites Accessibility Features for People With Disabilities