Sun Microsystems 819468310 - Manuals

Sun Microsystems 819468310 – Manual in PDF format online.

Manuals:

Manual

Manual Sun Microsystems 819468310

Summary

Page 3 - Contents; Sun Java System Access Manager 7.1 Release Notes

Contents Sun Java System Access Manager 7.1 Release Notes .......................................................................5 Revision History .....................................................................................................................................6 About Sun Java Sy...

Page 6 - About Sun Java System Access Manager 7.1; What’s New in This Release; Java ES Monitoring Framework Integration

Revision History The following table shows the Access Manager 7.1 Release Notes revision history. TABLE 1 Revision History Date Description of Changes July 2006 Beta release. March 2007 Java Enterprise System 5 release About Sun Java System Access Manager 7.1 Sun Java System Access Manager is part o...

Page 7 - Web Containers supported

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

Page 8 - Authentication module; Policy module

■ Number of successful authentications ■ Number of failed authentications ■ Number of successful logout operations ■ Number of failed logout operations ■ Transaction time for each module if possible (running and waiting states) 2. Sessions ■ Size of the session table (hence maximum number of session...

Page 10 - Deprecation Notification and Announcement

■ Support JCE Based SecureLogHelper - making it possible to use JCE (in addition to JSS) as a security provider for Secure Logging implementation Deprecation Notification and Announcement Sun Java(TM) System Access Manager 7.1 identity management APIs and XML templatesenable system administrators to...

Page 14 - Access Manager Legacy Mode; Java ES Silent Installation Using a State File; “Configure Now” Installation Option in Graphical Mode

Access Manager Legacy Mode If you are installing Access Manager with any of the following products, you must select theAccess Manager Legacy (6.x) mode: ■ Sun Java System Portal Server ■ Sun Java System Communications Services servers, including Messaging Server, CalendarServer, Instant Messaging, o...

Page 15 - “Configure Later” Installation Option; Determining the Access Manager Mode; Access Manager Policy Agents

“Configure Later” Installation Option If you ran the Java ES Installer with the “Configure Later“ option, you must run the amconfig script to configure Access Manager after installation. To select Legacy (6.x) mode, set thefollowing parameter in your configuration script input file ( amsamplesilent ...

Page 16 - Installation Issues; Upgrade Issues; Compatibility Issues

Known Issues and Limitations This section describes the following known issues and workarounds, if available, at the time ofthe Access Manager 7.1 release. ■ “Installation Issues” on page 16 ■ “Upgrade Issues” on page 16 ■ “Compatibility Issues” on page 16 ■ “Configuration Issues” on page 19 ■ “Acce...

Page 18 - commadmin; Delegated Administrator; commadmin; utility does not create an

Incompatibilities exist in core authentication module for legacy mode(6305840) Access Manager 7.1 legacy mode has the following incompatibilities in the core authenticationmodule from Access Manager 6 2005Q1: ■ Organization Authentication Modules are removed in legacy mode. ■ The presentation of the...

Page 19 - Configuration Issues

Configuration Issues ■ “Notification URL needs to be updated for Access Manager SDK installation without web container (6491977)” on page 19 ■ “Password Reset service reports notification errors when a password is changed (6455079)” on page 19 ■ “Platform server list and FQDN alias attribute are not...

Page 20 - Data validation for required attributes in the services (6308653); The; script does not update the realm/DNS aliases and

Platform server list and FQDN alias attribute are not updated(6309259, 6308649) In a multiple server deployment, the platform server list and FQDN alias attribute are notupdated if you install Access Manager on the second (and subsequent) servers. Workaround: Add the Realm/DNS aliases and platform s...

Page 21 - Access Manager Console Issues

Default Access Manager mode is realm in the configuration state filetemplate (6280844) By default, the Access Manager mode (AM_REALM variable) is enabled in the configuration state file template. Workaround: To install or configure Access Manager in Legacy mode, reset the variable in the state file:...

Page 22 - Add; attribute after data migration; Command Line Issue

Console does not return the results set from Directory Server afterreaching the resource limit (6239724) Install Directory Server and then Access Manager with the existing DIT option. Login to theAccess Manager Console and create a group. Edit the users in the group. For example, add userswith the f...

Page 23 - SDK and Client Issues; SDK clients need to restart after service schema change (6292616); Authentication Issues

5. Click Save. SDK and Client Issues ■ “Clients do not get notifications after the server restarts (6309161)” on page 23 ■ “SDK clients need to restart after service schema change (6292616)” on page 23 Clients do not get notifications after the server restarts (6309161) Applications written using th...

Page 25 - Session and SSO Issues; Using; HttpSession; with third-party web containers

List. If you create two new organizations with the same name, the operation fails, but AccessManager displays the “organization already exists” message rather than the expected “attributeuniqueness violated” message. Workaround: None. Ignore the incorrect message. Access Manager is functioning corre...

Page 27 - AMSDK Issues

AMSDK Issues ■ “Error displayed when performing AMIdentity.modifyService (6506448)” on page 27 ■ “Group members don't show up in selected list (6459598)” on page 27 ■ “Access Manager Login URL Returns Message " No such Organization found " (6430874)” on page 28 ■ “Sub-org creation not possib...

Page 28 - Sub-org creation not possible from Access Manager when using; SSL Issue

Access Manager Login URL Returns Message " No such Organization found " (6430874) The problem may be due to the use of mixed-case (both uppercase and lowercase) characters inthe fully qualified domain name (FQDN). Example: HostName.PRC.Example.COM Workaround : After installation, do not use ...

Page 29 - Samples Issue

The amconfig script fails when SSL certificate is expired. (6488777) If the Access Manager container is running in SSL mode, and the container SSL certificate isexpired, amconfig fails and may cause classpath corruption. Workaround: If you have already run amconfig with an expired certificate, and t...

Page 30 - Windows and HP-UX Issues; Federation and SAML Issues

JVM problems occur when running Access Manager on ApplicationServer (6223676) If you are running Application Server 8.1 on Red Hat Linux, the stack size of the threads createdby the Red Hat OS for Application Server is 10 Mbytes, which can cause JVM resource problemswhen the number of Access Manager...

Page 31 - Federation fails when using Artifact profile (6324056)

Federation fails when using Artifact profile (6324056) If you setup an identity provider (IDP) and a service provider (SP), change the communicationprotocol to use the browser Artifact profile, and then try to federate users between the IDP andSP, the federation fails. Workaround: None. Logout error...

Page 33 - Documentation Issues; Document unused properties in the

Documentation Issues ■ “Document the roles and filtered roles support for LDAPv3 plug-in (6365196)” on page 33 ■ “Document unused properties in the AMConfig.properties file (6344530)” on page 33 ■ “Document how to enable XML encryption (6275563)” on page 33 Document the roles and filtered roles supp...

Page 34 - Redistributable Files

5. If you are using a JDK version earlier than JDK 1.5, edit the jdk_root /jre/lib/security/java.security file and add Bouncy Castle as one of the providers. For example: security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider 6. Set the following property in the AMConfig.properties f...

Page 35 - How to Report Problems and Provide Feedback; Sun Welcomes Your Comments

How to Report Problems and Provide Feedback If you have problems with Access Manager or Sun Java Enterprise System, contact Suncustomer support using one of the following mechanisms: ■ Sun Support Resources (SunSolve) services at http://sunsolve.sun.com/ . This site has links to the Knowledge Base, ...

Page 36 - Accessibility Features for People With Disabilities

Accessibility Features for People With Disabilities To obtain accessibility features that have been released since the publishing of this media,consult Section 508 product assessments available from Sun upon request to determine whichversions are best suited for deploying accessible solutions. Updat...