Contained Within
Find More DocumentationFeatured Support Resources |  Download this book in PDF (820 KB)
Sun Java System Access Manager 7.1 Release NotesAugust 2009 Part Number 819-4683-22 The Sun JavaTM System Access Manager 7.1 Release Notes contain important information available for the Sun Java Enterprise System (Java ES) release, including new Access Manager features and known issues with workarounds, if available. Read this document before you install and use this release. To view the Java ES product documentation, including the Access Manager collection, see http://docs.sun.com/prod/entsys.5. Check this site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date documentation. Revision HistoryThe following table shows the Access Manager 7.1 Release Notes revision history. Table 1 Revision History
About Sun Java System Access Manager 7.1Sun Java System Access Manager is part of the Sun Identity Management infrastructure that allows an organization to manage secure access to Web applications and other resources both within an enterprise and across business-to-business (B2B) value chains. Access Manager provides these main functions:
Access Manager 7.1 Patch ReleasesThe latest revisions of the Access Manager 7.1 patches are available for download from SunSolve Online: http://sunsolve.sun.com. The most recent patch IDs are:
Note – Access Manager 7.1 patches are cumulative. You can install the latest patch without first installing an earlier patch. However, if you did not install an earlier patch, review the new features and issues in the earlier patch sections to determine if any of the features and issues apply to your deployment. Information about Access Manager 7.1 patches includes: Sun Alerts. Occasionally, Sun releases Alerts for Access Manager 7.1. Consider periodically checking SunSolve (http://sunsolve.sun.com/) to determine if there are any Sun Alerts that affect your deployment. Sun Java System LDAP JDK PatchesSun provides the following LDAP JDK patches for security and performance related fixes:
Check SunSolve (http://sunsolve.sun.com/) for the latest version of these patches. For more information, see Sun Alert http://sunsolve.sun.com/search/document.do?assetkey=1-26-242246-1. Note – For most deployments, Sun recommends that you apply the latest version of these patches. However, in the following situations, these patches are required:
Access Manager 7.1 Patch 3Access Manager 7.1 patch 3 fixes a number of problems, as listed in the README file included with the patch. Patch 3 also includes changes and known issues: New Features and Changes in Access Manager 7.1 Patch 3
Sun Java System LDAP JDK Patches are AvailableCheck the Sun Java System LDAP JDK Patches section to determine if you need to apply these patches. Running the updateschema Script is RequiredBeginning with patch 3 (and any subsequent patches unless specifically noted), you must run the updateschema.sh script on Solaris and Linux systems or the updateschema.pl script on Windows. The updateschema script updates the Sun Java System Directory Server schema with any new attributes required by the patch. Requirements for the updateschema.sh or updateschema.pl script include:
Access Manager 7.1 WAR File Deployment To locate the updateschema script:
For an Access Manager 7.1 WAR file deployment, run the updateschema script after you add the patch. The script prompts you for paths to the following items:
Access Manager 7.1 Installer (Package-Based) Deployment After you unzip the patchID.zip file, the updateschema.sh or updateschema.bat script is in the patchID directory, where patchID is 126356-03, 126357-03, 126358-03, or 126359-03, depending on your platform. For an Access Manager 7.1 installer (package-based) deployment, run the updateschema script after you add the patch. The script prompts you for the same Directory Server information as requested for a WAR file deployment. Limitation is Removed for Creation of Data Store Authentication Module Instance in Legacy ModePatch 3 removes the limitation for Creation of Data Store authentication module instance fails in Legacy mode (6764919). In patch 2, the amadmin user was prevented from logging in to any authentication module other than the Data Store and Application authentication modules. CR 6811036 in patch 3 removes this restriction, but at the same time re-implements the original security fix to protect the authentication for the amadmin user, which is considered as a special or “internal” user. An internal user such as amadmin must first authenticate internally to the OpenSSO configuration data store before it can authenticate to any authentication module. Hence you can login as amadmin to any authentication module only if you can first successfully authenticate to the configuration data store. Note. Due to CR 6811036, if you log in as amadmin to the Access Manager Admin Console and provide an incorrect password, the “Your authentication module is denied' message will be displayed instead of “Authentication Failed” (which was displayed prior to patch 2). Backward Compatibility Issue Between Access Manager 7.1 and amclientsdk.jar is FixedPatch 3 fixes the Backward compatibility issue between Access Manager 7.1 and amclientsdk.jar File (6754863). If you apply patch 3, the workaround documented for patch 2 is not needed. Sun Java Web Console 3.1 Patches Are RequiredThe fix for CR 6804294 requires that the following Java Web Console 3.1 patches be applied:
These patches are available on SunSolve (http://sunsolve.sun.com/). New Property Prevents Sessions From Being Destroyed After Session UpgradeFor a Distributed Authentication UI server deployment, Access Manager 7.1 patch 3 (CR 6700722) includes the new com.sun.identity.authentication.destroySessionAfterUpgrade property to prevent old sessions from being destroyed after a session upgrade. Values for this property can be:
Note. This new property applies only to a Distributed Authentication UI server and not to Access Manager 7.1 server. To prevent sessions from being destroyed after a session upgrade:
New Property Allows SSO Token Restriction Other Than an IP AddressAccess Manager 7.1 patch 3 (CR 6496155) includes the new com.iplanet.dpro.session.dnRestrictionOnly property to enforce the DN as the SSO token restriction rather then the IP address in cross-domain single sign-on (CDSSO) deployments and cookie-hijacking prevention mode. Values for this property can be:
Note: Older agents that use amclientsdk.jar from Access Manager 7 2005Q4 patch 5 and earlier should not set this property to true. To require Access Manager 7.1 server to enforce that an agent send the DN as the SSO token restriction:
Distributed Authentication UI Server Works With Basic AuthenticationAn Access Manager 7.1 patch 3 Distributed Authentication UI server now works with basic authentication (CR 6754852). SecurID Authentication Support is Added for Linux SystemsAccess Manager 7.1 patch 3 includes support for the SecurID authentication module on Linux systems (CR 6767780). (SecurID authentication support is also available on Solaris SPARC systems and on Solaris x86 systems since patch 2.) Known Issues in Access Manager 7.1 Patch 3
Single WAR Access Manager Deployment Cannot Use https Protocol Handler (6810092)If Access Manager 7.1 patch 3 is deployed from a single WAR file, the https protocol handler cannot be used. Workaround. None. If config Directory Path on Windows Contains a Space, Patch 3 updateschema.pl Fails (6852463)If Access Manager 7.1 patch 3 is deployed from a single WAR file on Windows, running the updateschma.pl script fails if the path to the config directory contains a space. For example: c:\Documents and Settings\Administrator\AMConfig Workaround. In the updateschema.pl file, add a double quote (") around the filename path in the following lines and then rerun the script: $XMLFILE="$AM_ETCDIR/add_cert_org_serverconfig.xml"; $XMLFILE="$AM_ETCDIR/add_cert_org.xml"; $XMLFILE="$AM_ETCDIR/add_choice_none_org.xml"; $XMLFILE="$AM_ETCDIR/add_choice_none_org_serverconfig.xml"; $XMLFILE="$AM_ETCDIR/add_delegation_default_SubjectIdType.xml"; $XMLFILE="$AM_ETCDIR/add_auth_attr.xml"; For example: $XMLFILE="\"$AM_ETCDIR/add_cert_org_serverconfig.xml\""; $XMLFILE="\"$AM_ETCDIR/add_cert_org.xml\""; $XMLFILE="\"$AM_ETCDIR/add_choice_none_org.xml\""; $XMLFILE="\"$AM_ETCDIR/add_choice_none_org_serverconfig.xml\""; $XMLFILE="\"$AM_ETCDIR/add_delegation_default_SubjectIdType.xml\""; $XMLFILE="\"$AM_ETCDIR/add_auth_attr.xml\""; Entry 1 Hard-coded Path Should be Removed from Patch 3 updateschema.pl Script on Windows (6852467)If Access Manager 7.1 patch 3 is deployed from a single WAR file on Windows, running the updateschma.pl script fails because the path to the tools directory is hard-coded. Workaround. Remove /amAdminTools from the following line of the updateschema.pl file and then rerun the script: $AM_ADMIN_CMD="$WAR_TOOLS_DIR/amAdminTools/$DEPLOY_URI/bin/amadmin.bat"; Access Manager 7.1 Patch 2Note – Considerations for patch 2 include:
Access Manager 7.1 patch 2 fixes a number of problems, as listed in the README file included with the patch. Patch 2 also includes these changes:
Access Manager 7.1 on WebLogic Server requires new ldapjdk.jar File (6774634)Sun provides a new ldapjdk.jar file that includes security and performance related fixes for Access Manager 7.1 patch 2. However, the Sun ldapjdk.jar won't be effective on WebLogic Server because weblogic.jar bundles an older ldapjdk.jar file. Workaround. Put the Sun ldapjdk.jar ahead of weblogic.jar in the CLASSPATH, as follows:
Creation of Data Store authentication module instance fails in Legacy mode (6764919)If you install Access Manager 7.1 patch 2 in Legacy mode and you create a Data Store authentication module instance in the Console, an error occurs while the module instance is created. Note: This problem applies only to Access Manager 7.1 patch 2 and previous releases. Workaround for Access Manager 7.1 in Legacy Mode. On systems running Access Manager 7.1 in Legacy Mode, in Directory Server, add the sunRegisteredServiceName attribute to the Data Store service and set the sunAMAuthDataStoreAuthLevel attribute to the minimum value (zero), to ensure the creation of the Data Store authentication module instance. For example, using ldapmodify: ldapmodify -D "cn=Directory Manager" -w dm-password -h ds-host -p ds-port dn: ds-rootdn changetype: modify add: sunRegisteredServiceName sunRegisteredServiceName: sunAMAuthDataStoreService ldapmodify -D "cn=Directory Manager" -w dm-password -h ds-host -p ds-port dn: ou=default,ou=OrganizationConfig,ou=1.0,ou=sunAMAuthDataStoreService,ou=services, ds-rootdn changetype: modify add: sunkeyvalue sunkeyvalue: sunAMAuthDataStoreAuthLevel=0 Sub-realm administrator can log in as amadmin in root realm (6761627)If Access Manager 7.1 is installed in Realm mode and a sub-realm administrator creates another amadmin user in the sub realm, the second amadmin can also log in to the root (top-level) realm. Access Manager 7.1 patch 2 fixes this problem. As the consequence of this fix, amadmin can log in to the Console using this URL: http://amhost.example.com:port/amserver/UI/Login?module=DataStore New com.sun.identity.appendSessionCookieInURL property (6740071)The new com.sun.identity.appendSessionCookieInURL property determines whether Access Manager appends the session cookie to the URL for zero page authentication. Set this property to false to prevent Access Manager from appending the session cookie to the URL. For example, if an application is filtering incoming URLs for special characters for security reasons and a cookie contains a special character, then access is denied The default value is true (cookie is appended). Backward compatibility issue between Access Manager 7.1 and amclientsdk.jar File (6754863)A backward compatibility issue exists between Access Manager 7.1 (all patch levels) and the amclientsdk.jar bundled with the policy agent 2.2 Hotpatch 5 and 7. Workaround. If Access Manager 7.1 does not have cookie hijacking prevention enabled, add the following property to the policy agent AMAgent.properties file: com.sun.identity.enableUniqueSSOTokenCookie=false Note: If Access Manager 7.1 does have cookie hijacking prevention enabled, this workaround will not work. Access Manager JAR files should include version number in MANIFEST.MF file (6693152)Access Manager JAR files now have the version and build timestamp added to the MANIFEST.MF file. For example: Specification-Version: "7.1" Implementation-Version: "AM_7.1_20080917:05:27:19" Security permission is missing for CRL validation (6673538)Certificate-based authentication is not working if it is configured with Certificate Revocation list (CRL) checking. Workaround. For an existing Access Manager instance, add the following security permission to the web container server policy file and then restart the web container: permission java.security.SecurityPermission "getProperty.ocsp.*"; For Sun Java System Application Server and IBM WebSphere Application Server, the security policy file is server.policy. For BEA WebLogic Server, the file is weblogic.policy. For new Access Manager instances, the respective web container amconfig script has been revised to add this security permission to the security policy file. SecurID authentication is supported on Solaris x86 systems (6621802)SecurID authentication is now supported on Solaris x86 systems (as well as on Solaris SPARC systems). Access Manager Key Provider needs option to use types other than JKS format (6603228)The default Key Provider implementation (JKSKeyProvider) uses JKS format. Access Manager now includes the following new configuration property that allows the keystore type to be changed. For example, for PKCS12 format: com.sun.identity.saml.xmlsig.storetype=PKCS12 To use this new property, add it the AMConfig.properties file and restart the Access Manager web container. Delegation privileges cannot be defined for a filtered role (6486843)If you create a new filtered role, it does not appear under the Privileges tab in the Admin Console. Workaround. After you apply patch 2, follow these steps to update the Delegation Service (sunAMDelegationService) in the Directory Server schema:
Now, when you log in to the Administration Console, the filtered role will appear under the Privileges tab. Persistent cookie support is added (6600325)Persistent cookie support is added for Access Manager session cookies if:
Access Manager 7.1 Patch 1Access Manager 7.1 patch 1 fixes a number of problems, as listed in the README file included with the patch. Patch 1 also includes the following new features and known issues:
Support for specific application idle session timeout valuesPatch 1 allows different applications to have different session idle timeout values. In an enterprise, some applications might require session idle timeout values that are less than the session idle time out specified in the session service. For example, you have specified session the idle timeout value in the session service as 30 minutes, but an HR application should timeout if a user has been idle for more than 10 minutes. This feature is not currently supported for Distributed Authentication and Cross Domain Single Sign-on scenarios Requirements to use this feature are:
To use this feature:
For example, consider a policy http://host.sample.com/hr/*, with this Authentication Scheme Condition:
If there are multiple policies defined to protect resources of the HR application, you must add the Condition to all of the policies. When a user in a distinct session attempts to access the HR application protected by the Access Manager agent, that user is prompted to authenticate for the LDAP scheme (if the user is not yet authenticated). If the user has already authenticated to the LDAP scheme, that user is allowed access only if the time is less than 10 minutes since the time the last authentication or if the time is less than 10 minutes since that user's last access time to the HR application. Otherwise, the user is prompted to authenticate to the LDAP scheme again to access the application. The Idle Session Timeout for a realm is configured for the highest value required by all applications. Shorter Idle Session Timeout requirements are enforced by the Policy Condition protecting the appropriate applications. However, if you define explicit "deny" policies to protect the application, it would break this protection. This is because the new the new Condition extends the idle timeout for the application, assuming that the access to the application is allowed if this Condition is satisfied. If the other "deny" policy is satisfied, the user can not access the application. Application idle timeout of value 0 is treated as Integer.MAX_VALUE for the purposes of idle timeout enforcement. Web Proxy Agent 2.2-01 in CDSSO mode does not work with Access Manager 7.1 Patch 1 (CR 6611841)The Web Proxy Agent 2.2-01 in Cross Domain Single Sign-on mode does not work with Access Manager 7.1 Patch . The agentRootURL requirement was added as a security measure to ensure that CDC is handing off ssotoken cookie to trusted agents running at known URLs. Workaround
Distributed Auth UI does not work with a WebSphere Application Server 5.1.1.12 server (CR 6625928)In Patch 1, the Distributed Authentication user interface does not work with a WebSphere Application Server 5.1.1.12 server. Password file exposed in a temporary directory after Patch 1 re-deployment (CR 6640377)After Access Manager Patch 1 applied to Access Manager 7.1 and re-deployed, several/tmp directories are created. In one of them, the permissions are incorrectly set so that the sun_ad_dirmgrpasswd is readable. These directories are automatically deleted when the deployment is completed, but they are exposed for a matter of time before hand. This is a potential security risk. Workaround Before re-deploying the patch, set umask 077. The files will then be created with the correct permissions. LDAP Failover not working properly (CR 6611627)LDAP failover does not work if the primary LDAP failover server is set to SSL and the secondary server is set to non-SSL. There is no workaround at this time. amconfig does not tag-swap and re-register the monitoring framework descriptor (CR 6636710)When Patch 1 is applied to a full Access Manager installation using the amconfig script to redeploy all of the web applications, amconfig does not tag swap the monitoring framework descriptor. As a result, the monitoring framework description at $CONFIG_DIR/com.sun.cmm.am.xml only contains tags. Workaround Back up the monitoring framework descriptor (Solaris locatoin is /etc/opt/SUNWam/config/com.sun.cmn.am.xml, Linux location is /etc/opt/sun/identity/config/com.sun.am.xml) before applying the patch. Once the patch is applied, replace the patched file with the original file in the same location. amtune does not work if installed in a non-default directory (CR6640673)The amtune script will not work if installed in a non-default directory. This occurs on all platforms. The script is defaulting to the LDAP installation directory when the package is not found on the system. Workaround Modify the amtune-directory so that LDAP_DIR points to the DSEE base directory: DSADMIN=$LDAP_DIR/ds6/bin/dsadm amtune does not delete the world readable password file (CR 6640672)The amtune script does not delete the password file after it completes. The file should be deleted after the completion of the script. Workaround Modify the set DSADMIN_PASSFILE attribute, or any directory that only the root user can read, in the amtune-env file before running the amtune script. For example: DSADMIN_PASSFILE=/var/tmp/dspassfile amtune should set thread pool size at 3 times the number of CPUs or cores for CMT servers (CR 6631123)The optimal size of Access Manager's notification thread pool size (com.iplanet.am.notification.threadpool.size in AMConfig.properties) was 3 times the number of CPU's where Access Manager is deployed or the number of cores in cases of CMT servers like Niagara I and II (Sun Fire T1000/2000 and T5120/T5220 servers). The current amtune-identity sets the maximum number of thread pools at 28 regardless of number of CPU's and calculates the optimal value based on the available amount of memory. Workaround Increase the value in the com.iplanet.am.notification.threadpool.size property in AMConfig.properties by three times the number of CPU's or cores in cases of CMT servers (e.g., T1000/T2000 or T5210/T5220 servers), overriding the recommended values by amtune-identity script. amsfo.pl does not work for Windows (CR 6629189)For Access Manager Patch 1 for Windows, the amsfo.pl script does not work properly. There is no workaround at this time. Not able to deploy WAR file generated by patch.bat if -l option is used for Windows (CR 6636474)If you are deploying the WAR file using patch.bat, do not use the -l option as it will cause errors and fail to deploy. amserveradmin.bat throwing errors for Access Manager 7.1 Patch for Windows (CR 6631526)Executing the amserveradmin.bat batch file produces the following error message:
This is because after reconfiguring, tokens in this file are not getting tag swapped. Workaround In the amserveradmin.bat.template, set the value for AM_DIR to AM_DIR=c:\sun\identity. Rename the template file to amserveradmin.bat. amsfo.pl script does not work for Session Failover in a Single War deployment for Windows (CR 6646519)In a single WAR deployment for Windows, the session failover script, amsfo.pl, fails to start the amsessiondb client. In order to fix this, perform all of the steps described in the following workaround. Workaround
Access Manager classpath not pointing to xml.sec.jar in Patch 1 for Windows (CR 6644461)In Access Manager Patch 1 for Windows, the Access Manager classpath is not pointing to the patched version of the xmlsec.jar. Workaround Copy jes-install-dir\identity\lib\xmlsec.jar to jes-install-dir\share\lib\xmlsec.jar. Post authentication plug-in supports Microsoft SharePoint (CR 6541695)The Access Manager post-authentication plug-in (ReplayPasswd.java) has been modified in this patch release to read the com.sun.am.sharepoint_login_attr_name=sharepoint-login-value property. The value of this property indicates the user token that SharePoint uses for authentication. For example, if “login” is the LDAP attribute that is mapped in both the places (Access Manager and SharePoint), then the property should be com.sun.am.sharepoint_login_attr_name=login. The post-authentication plug-in will read this property and retrieve the corresponding value from Directory Server. It will then replace this value as a session property. The IIS6 authentication plug-in is modified to read this new property and set authorization headers for Sharepoint to work. Retrieving schema from Active Directory data store fails (CR 6542686)Access Manager 7.1 would not successfully retrieve the schema if you are using the Active Directory datastore. Installing patch 1 will fix this issue. To incorporate the fix, load the am_remote_ad_schema.ldif file. This file is located at /etc/opt/SUNWam/config/ldif for Solaris systems, /etc/opt/sun/identity/config/ldif for Linux systems, and \identity\config\ldif for Windows systems. Access Manager supports the JDK 1.5 HttpURLConnection setReadTimeout method (CR 6536635)To support the setReadTimeout method, the AMConfig.properties file has the following new property for you to set the read timeout value: com.sun.identity.url.readTimeout If the web container is using JDK 1.5, set this property to an appropriate value to cause connections to time out, in order to avoid having too many open HttpURLConnections that might cause the server to hang. The default is 30000 milliseconds (30 seconds). The setReadTimeout method is ignored if com.sun.identity.url.readTimeout is not present in the AMConfig.properties file or is set to an empty string. saml samples will not work if the saml module instance is created with lower case name "saml" (CR 6648342)If a SAML instance is created with the name "saml", the amSAML authentication fails and the sample will not work. G11n: CLI commands amhasetup and amserver are not localized (CR 6567135)For EMEA locales, the amhasetup and amserver command line utilities return unlocalized output. For other languages, the output is localized. G11n: The User sub-tab incorrectly translated in French language (CR 6633529)After you have created a user in the User sub-tab of the Realm tab in the French language, the edited user message is incorrectly displayed as Modification de Utilisateur. Web Security Service Issues Fixed6543625 — UserName token authentication can authenticate against a configured LDAP moduleThe UserName token authentication is able to authenticate against a configured LDAP module. In previous releases, the UserName token authentication could only use the Access Manager file-based authentication realm. 6543626 — SOAPRequestHandler returns the SSOToken set in the SubjectSOAPRequestHandler now returns the SSOToken set in the Subject, in addition to X509 or UserName token that was used for authentication. The SSOToken is in the format usable to the PolicyEvaluator API. 6544177 — When using X509 token with an invalid certificate AM always accepts the cert even without root CAWhen using X509 token with an invalid certificate, Access Manager always accepts the certificate, despite the fact that the root CA is not in the Keystore. this problem has been fixed. 6559603 — Boolean configuration flag for "request" signingA web service user can now choose boolean configuration for SOAP request signing. 6543620 Access Manager Policy Agent profiles able to apply a digital signature to the service request for UserName tokenAccess Manager Policy Agent profiles can apply a digital signature to the service request and the service response. In previous releases, digital signature could be used only in case when X509 token is included into SOAP message for authentication. 6543623 Access Manager Policy Agent profiles able to encrypt SOAP request body and SOAP response bodyAccess Manager Policy Agent profiles are now able to encrypt SOAP request body and SOAP response body. 6570021 Encryption supports SOAP messages with extra spaces.Access Manager now supports the encryption of SOAP message with extra spaces and new lines between XML elements of SOAP message. It is common to see SOAP messages with extra spaces and new lines inserted for better readability. Removed ACIs that cause unnecessary performance degradation (CR 6484947)The amtune script has been changed to enhance the performance of AM 7.1 by removing unnecessary ACI checks. You must run amtune after the patch installation to remove the ACIs. 6.3–based console online help not displayed win Application Server 8.2 (CR 6587213)If you have installed Access Manager from the Java ES 5 update 1, and have it deployed with Application Server 8.2, the Access Manager console online help will not display. This only occurs in the 6.3–based Access Manager console, accessed by /amconsole. Multiple passwords not required for amtune scriptIn Access Manager 7.1 Patch 1 you do not need to enter multiple passwords when executing individual amtune scripts. Only the wrapper amtune script which calls individual scripts needs multiple passwords. For instance, amtune-os and amtune-identity do not require any password. amtune-directory requires only Directory Manager password, while amtune-ws6, -ws7 and -as8 require the corresponding web container admin passwords. amtune-os will not run in local zoneamtune-os will not run if the wrapper amtune script is run in a local zone on Solaris 10, or higher, but other individual amtune scripts will still run. Pre-Installation ConsiderationsReview the following section before applying the patch. Installing and Configuring Access ManagerThe Access Manager patches described in this document do not install Access Manager. Before you install the patch, Access Manager 7.1 must be installed on the server. For information about installation for Sun Java Enterprise System 5, see following documents:
For information about installation for Sun Java Enterprise System 5 Update 1, see following documents: You should also be familiar with running the amconfig script to deploy, re-deploy, and configure Access Manager, as described in the Chapter 2, Running the Access Manager amconfig Script, in Sun Java System Access Manager 7.1 Postinstallation Guide. For a list of the Access Manager patches that are made obsolete by this patch and any patches that you must install before you install this patch, refer to the README file included with this patch.  Caution – Access Manager patches (as with any other patches) should be tested on a staging or pre-deployment system before you put them into a production environment. Also, the patch installer might not update your customized JSP files properly, so you might need to make manual changes in these files in order for Access Manager to function properly. Patch Installation InstructionsNote – Beginning with patch 3 (and any subsequent patches unless specifically noted), you must run the updateschema.sh script on Solaris and Linux systems or the updateschema.pl script on Windows. The updateschema script updates the Sun Java System Directory Server schema with any new attributes required by the patch. For more information see Running the updateschema Script is Required. Patch Installation Instructions For Solaris SystemsBefore you install the Solaris patch, make sure that you have backed up the files listed in Pre-Installation Considerations. To add and remove patches on Solaris systems, use the patchadd and patchrm commands, which are provided with the OS. patchadd Command Use the patchadd command to install a patch on a standalone system. For example: # patchadd /var/spool/patch/126356-03 Note – If you are installing the Solaris patch on a Solaris 10 global zone, invoke the patchadd command with the -G argument. For example: patchadd -G /var/spool/patch/126356-03 The postpatch script displays a message about redeploying the Access Manager applications, except on a system that has only the Access Manager SDK component installed. The postpatch script creates the amsilent file in the following directory:
AccessManager-base is the base installation directory. The default base installation directory is /opt on Solaris systems and /opt/sun on Linux systems. The amsilent is based on the amsamplesilent file, but with some required parameters set according to the Access Manager configuration files on the system. The password parameters, however, contain default values. Uncomment and modify the value of each password parameter and carefully check values of other parameters in this file, as needed for your deployment. The COMMON_DEPLOY_URI parameter, the URI prefix for the common domain web application, also contains a default value. If you have chosen a non-default value for this URI, make sure to update this value. Otherwise, the redeployment of the web applications with amconfig and the patch generated amsilent file will fail. Then, run the following command (shown with Access Manager installed in the default directory): # cd /opt/SUNWam/bin # ./amconfig -s /opt/SUNWam/amsilent Caution – The amsilent file contains sensitive data such as administrator passwords in plain text, so make sure you secure the file as appropriate for your deployment. patchrm Command Use the patchrm command to remove a patch from a standalone system. For example: # patchrm 126356-03 The backout script displays a message similar to the patchadd command, except on a system that has only the Access Manager SDK component installed. After the patch is removed, redeploy the Access Manager applications using the amsilent file in the AccessManager-base/SUNWam directory, where AccessManager-base is the base installation directory. The default base installation directory is /opt on Solaris systems. Set the parameters in the amsilent file, as needed for your deployment. Then, run the following command, which is shown with Access Manager installed in the default directory on Solaris systems: # cd /opt/SUNWam/bin # ./amconfig -s /opt/SUNWam/amsilent For additional information and examples about the patchadd and patchrm commands, see the appropriate Solaris man pages. Solaris 10 ZonesThe Solaris 10 operating system introduced the new concept of “zones.” Consequently, the patchadd command includes the new -G option, which adds a patch only to the global zone. By default, the patchadd command looks for the SUNW_PKG_ALLZONES variable in the pkginfo of packages to be patched. However, for all Access Manager packages, the SUNW_PKG_ALLZONES variable is not set, and the -G option is required if Access Manager 7.1 is installed in the global zone. If Access Manager is installed in a local zone, the patchadd -G option has no effect. If you are installing Access Manager 7.1 patches on a Solaris system, it is recommended that you use the -G option. For example: # patchadd -G AM7_patch_dir Similarly, if Access Manager is installed in the global zone, the -G option is required to run the patchrm command. For example: # patchrm -G 126356-03 Patch Installation Instructions For Linux SystemsBefore you install the Linux patch, make sure that you have backed up the files listed in Pre-Installation Considerations. The installpatch installs a patch on a standalone Linux system. For example: # ./installpatch The postpatch script prints messages similar to the messages on a Solaris system. However, the procedure to back out a patch on a Linux system is different than on a Solaris system. There is no generic script to back out a Linux patch. If a lower version of the patch was previously installed, you can re-install that version and then follow the postpatch instructions to redeploy the Access Manager applications by running the amconfig script. If the patch is installed on the Access Manager 7.1 RTM release and you want to remove the patch and restore the system to the RTM state, you must reinstall the Access Manager RTM bits using the reinstallRTM script. This script takes the path where the Access Manager RTM RPMs are stored and installs the RTM RPMs over the patched RPMs. For example: # ./scripts/reinstallRTM path_of_AM71_RTM_RPM_directory After you run the reinstallRTM script, redeploy the Access Manager applications by running the amconfig script and the restart the web container. Patch Installation Instructions For Windows SystemsThe requirements to install the Windows patch include:
Installing the Windows PatchBefore you install the Windows patch, make sure that you have backed up the files listed in Pre-Installation Considerations. In the base directory path for input to the patch scripts, use a forward slash (/). For example: c:/sun To install the Windows patch:
Note – If Access Manager is deployed to Web Server 7.0, make sure that Web Server administration server is up and running Backing Out the Windows PatchTo back out the Windows patch:
Access Manager 7.1 Patch 1 Single WAR DeploymentNote – Sun provides patch functionality for Access Manager 7.1 WAR deployments on all platforms in patch 140504, which is available on http://sunsolve.sun.com/. See the patch README file for more information. (For consistency with other Access Manager 7.1 patches, “02” is the first release of this patch.) This section describes new features, installation instructions and known problems for Access Manager 7.1 patch 1 single WAR deployment. New Container Versions SupportedThe Access Manager 7.1 patch 1 now supports the following containers:
The version of Access Manager single web-application (WAR) supported on these containers is located in zip_install_directory/applications/jdk14. zip_install_directory is the directory to which you downloaded the .ZIP file for the WAR. Note – Even though WebLogic 9.2 is compatible with Sun's JDK version 1.5_04, not all of the classes required by Access Manager are present. Access Manager single web-application, when deployed from zip_install_directory/applications/jdk15, will result in exceptions thrown of missing classes. The deployment succeeds and the console is accessible, but this causes issues with the clients. In general, zip_install_directory/applications/jdk14 should be used for non-Sun or third party containers, even if their run time environment is JDK 1.5.x. Considerations for Single WAR Deployment with WebSphere 6.1After you obtain the Access Manager 7.1 patch 1 single WAR, see Adding Access Manager Permissions to the Server Policy File in Sun Java System Access Manager 7.1 Postinstallation Guide for information on configuring the permissions to the server policy file for the web container on which Access Manager will be deployed. In addition to the policy changes, follow the steps described in Deploying an Access Manager 7.1 WAR File in IBM WebSphere Application Server in Sun Java System Access Manager 7.1 Postinstallation Guide. Considerations for Single WAR Deployment with Weblogic 9.2For BEA WebLogic Server 9.2, the following JVM property needs to be added in the BEA WebLogic Server instance start script, startWebLogic.sh: JAVA_OPTIONS= "-Djavax.xml.soap.MessageFactory=com.sun.xml. messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl" After you obtain the Access Manager 7.1 patch 1 single WAR, see Adding Access Manager Permissions to the Server Policy File in Sun Java System Access Manager 7.1 Postinstallation Guide for information on configuring the permissions to the server policy file for the web container on which Access Manager will be deployed. Applying Patch 1 for Single WAR DeploymentThe application of patch 1 is required if you already have an RTM version of the Access Manager single web-application deployed and wish to redeploy the Access Manager patch 1 web application. If there is no prior deployment of Access Manager, then Access Manager single web-application (WAR) provided under the zip_install_dir/applications directory can be used. The patch is provided in a separate directory, zip_install_dir/patch. In this directory, there is a README provided with instructions on running the patch utility. The patch utility and related files provided in the ZIP file are only for applying the patch to Access Manager single web-application downloaded from the SUN's download site. This patch will not operate with the Access Manager single WAR web-application generated by using the Java Enterprise Systems 5 “Configure Later” option with DEPLOY_LEVEL=10. After you have successfully applied the patch, copy the following property in the configured instance's AMConfig.properties file and then restart the container: com.sun.identity.url.readTimeout=30000 This patch does not support the patch application to the JavaEE SDK Access Manager WAR file. Known Issues with Patch 1 WAR DeploymentThis section lists the known issues with the Access Manager 7.1 patch 1 WAR deployment. Modifying SAML source ID in WAR deployment for Access Manager 7.1 Patch 1 (CR 6582972)This issue will only occur when you already have a RTM version of Access Manager single web-application deployed and would now want to redeploy Access Manager patch 1 web-application. After you have successfully un-deployed the RTM version of Access Manager and redeployed the patch 1 version of Access Manager, follow the steps outlined under the "Workaround" section. If you are deploying Access Manager patch 1 web-application without any prior installation of Access Manager in your environment, then the outlined workaround is not required. Additionally, this workaround is applicable only when using SAML v.1. Workaround
amAdmin from amAdminTools.zip Single WAR does not work with IBM JDK WebSphere 6.1 (CR 6618861)Currently there is no support to run Access Manager's CLI tools with a non-Sun JDK. What’s New in This ReleaseThis release includes the following new features: Java ES Monitoring Framework IntegrationAccess Manager 7.1 integrates with the Java Enterprise System monitoring framework through Java Management Extensions (JMX). JMX technology provides the tools for building distributed, Web-based, modular, and dynamic solutions for managing and monitoring 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:
Web Service SecurityAccess Manager 7.1 extends authentication capabilities to web services in the following ways:
Single Access Manager WAR file deploymentAccess 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 can coexist with the Java Enterprise System installer, which deploys multiple JAR, XML, JSP, HTML, GIF, and various properties files. For more information about staging, configuring, and deploying the Access Manager WAR file, see the Sun Java System Access Manager 7.1 Postinstallation Guide. Enhancements to Core ServicesWeb Containers supported
Monitoring Framework Integration Access Manager can use the Java Enterprise System Monitoring Framework to monitor the following:
Authentication module
Policy module
Service Management module
Access Manager SDK
Web Services support
Installation module
Delegation module
Upgrade
Logging
Deprecation Notification and AnnouncementSun Java(TM) System Access Manager 7.1 identity management APIs and XML templates enable system administrators to create, delete, and manage identity entries in Sun Java System Directory Server. Access Manager also provides APIs for identity management. Developers use the public interfaces and classes defined in the com.iplanet.am.sdk package to integrate management functions into external applications or services to be managed by Access Manager. Access Manager APIs provide the means to create or delete identity-related objects as well as to get, modify, add, or delete the objects' attributes from Directory Server. The Access Manager com.iplanet.am.sdk package, commonly known as AMSDK, will not be included in a future Access Manager release. This includes all related APIs and XML templates. No migration options are available now, and no migration options are expected to be available in the future. The user provisioning solutions provided by Sun Java System Identity Manager are compatible replacements that you can start to use now. For more information about Sun Java System Identity Manager, see http://www.sun.com/software/products/identity_mgr/index.xml. Hardware and Software RequirementsThe following table shows the hardware and software that are required for this release. Table 2 Hardware and Software Requirements
If you have questions about support for other versions of these components, contact your Sun Microsystems technical representative. Supported BrowsersThe following table shows the browsers that are supported by the Sun Java Enterprise System 5 release. Table 3 Supported Browsers
General Compatibility InformationAMSDK intersystem incompatibility with Access Manager serverThe following combinations are not compatible between the AMSDK and the Access Manager server in the following Java Enterprise System releases:
Upgrade not supported for Access Manager HPUX versionThere is no support for an upgrade path from Access Manager 7 2005Q4 to Access Manger 7.1 (this release) for the HPUX version. Access Manager Legacy ModeIf you are installing Access Manager with any of the following products, you must select the Access Manager Legacy (6.x) mode:
You select the Access Manager Legacy (6.x) mode, depending on how you are running the Java ES installer: To determine the more for an Access Manager 7.1 installation, see Determining the Access Manager Mode. Java ES Silent Installation Using a State FileJava ES installer silent installation is a non-interactive mode that allows you to install Java ES components on multiple host servers that have similar configurations. You first run the installer to generate a state file (without actually installing any components) and then edit a copy of the state file for each host server where you plan to install Access Manager and other components. To select Access Manager in Legacy (6.x) mode, set the following parameter (along with other parameters) in the state file before you run the installer in silent mode: ... AM_REALM = disabled ... For more information about running the Java ES installer in silent mode using a state file, see the Chapter 5, Installing in Silent Mode, in Sun Java Enterprise System 5 Installation Guide for UNIX. “Configure Now” Installation Option in Graphical ModeIf you are running the Java ES Installer in graphical mode with the “Configure Now” option, on the “Access Manager: Administration (1 of 6)” panel, select “Legacy (version 6.x style)”, which is the default value. “Configure Now” Installation Option in Text-Based ModeIf you are running the Java ES Installer in text-based mode with the “Configure Now” option, for Install type (Realm/Legacy) [Legacy] select Legacy, which is the default value. “Configure Later” Installation OptionIf 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 the following parameter in your configuration script input file (amsamplesilent): ... AM_REALM=disabled ... For more information about configuring Access Manager by running the amconfig script, refer to the Sun Java System Access Manager 7.1 Administration Guide. Determining the Access Manager ModeTo determine whether a running Access Manager 7.1 installation has been configured in Realm or Legacy mode, invoke: http(s)://host:port/amserver/SMSServlet?method=isRealmEnabled Results are:
Access Manager Policy AgentsThe following table shows the compatibility of Policy Agents with the Access Manager 7.1 modes. Table 4 Policy Agents Compatibility With Access Manager 7.1 Modes
Known Issues and LimitationsThis section describes the following known issues and workarounds, if available, at the time of the Access Manager 7.1 release. Installation IssuesInformation about Java System Enterprise installation issues is contained in the Java Enterprise System 5 Release Notes. See the section Access Manager Installation Issues in Sun Java Enterprise System 5 Release Notes for UNIX. This section contains the following Known Issues: Access Manager single WAR deployment on WebLogic requires JAX-RPC 1.0 JAR files to communicate with client SDK (6555040)There is a known issue with the single WAR deployed on Weblogic 8.1, with JAX-RPC initialization. In order for Access Manager to communicate with the client SDK, you need to replace the JAX-RCP 1.1 jar files with JAX-RPC 1.0 jar files. Workaround: There are two ways to obtain the WAR file. One is through the Java Enterprise System 5 installer with Access Manager set to the Configure Later option, the other is from Sun's download site. If you have generated the WAR file through the Java Enterprise System 5 installer with the Configure Later option:
If you have obtained the WAR file through the Sun download site (http://www.sun.com/download/index.jsp):
Additional .jar file is required for single WAR generated by the Java Enterprise System 5 installer for Websphere 5.1 (6550261)If the Access Manager single WAR is generated using the Java Enterprise System 5 installer with the Configure Later option, additional .jar files are required before you deploy Websphere 5.1. Workaround:
Single WAR deployment for Webshpere requires changes to server.xml to communicate with client SDK (6554379)In order for the Access Manager single WAR deployment with Websphere 5.1 to successfully communicate with the client SDK, you must make changes to the server.xml file. Workaround: To correctly change the server.xml file, see the following steps:
Changes required for Distributed Authentication to work with Access Manager single War for Weblogic and Webshpere (6554372)The Distributed Authentication WAR requires additional jar files for parsing for both Weblogic 8.1 and Websphere 5.1 because the container is version JDK14. The JDK14 .jar files are located in the following directory of the .zip file: ZIP-ROOT/applications/jdk14/jarFix Workaround: For Weblogic 8.1:
For Websphere 5.1:
Single WAR Configurator fails against DS (6562076)Access Manager deployed as a single WAR fails to configure on Directory Server 6 with a single component root suffix, for example. dc=example. However, it works with multi component root suffix, for example dc=example,dc=com. After running the configurator with configuration datastore as Sun Java System Directory server, it is always advised to go and edit the serverconfig.xml to replace the cn=directory manager with less privileged user, such as cn=dsameuser. This user should be available in the directory server with proper access permissions to the Access Manager service tree. Workaround: Use the multi component root suffix, for example dc=example,dc=com. Multi-server configuration of AM Single WAR on same host throws exception (6490150)When configuring the second instance of Access Manager single WAR on the same host against Directory Server, it throws an exception while updating the Organization Alias. This issue does not occur if the second instance configured is on a different host. Upgrade IssuesFor additional information, see Upgrade Issues in Sun Java Enterprise System 5 Release Notes for UNIX. Required Services not supported in Access Manager 7.1 Console in Realm Mode (6615838)The Required Services functionality is not supported in Realm Mode. Required Services are services that are dynamically added to user entries when the entries are created. Required Services are not supported for users created under the Access Control tab (that is, using the realm feature) because these users will be under the services node. This scenario applies to an Access Manager 7.1 installation in Legacy Mode or the coexistence of Access Manager 7.1 in Legacy Mode with Sun OpenSSO Enterprise 8.0. However, the Required Services functionality is supported as follows:
Compatibility Issues
Access Manager Single Sign-On fails on Universal Web Client (6367058, 6429573)The problem occurs after you install Access Manager, Messaging Server, and Calendar Server and configure them to work together, and then install the Java Enterprise System 5 120955-01 patch. The user encounters a login error. The error is due to an incompatibility between Policy Agent 2.1 properties and AMSDK. There is no workaround at this time. StackOverflowError occurs on Web Server 7.0 running in 64–bit mode (6449977)If Access Manager is configured on a Web Server 7.0 instance using a 64–bit JVM, the user encounters a Server Error message when accessing the console login page. The Web Server error log contains a StackOverflowError exception. Workaround: Modify the Web Server configuration by following these steps:
Incompatibilities exist in core authentication module for legacy mode (6305840)Access Manager 7.1 legacy mode has the following incompatibilities in the core authentication module from Access Manager 6 2005Q1:
Workaround: None. Delegated Administrator commadmin utility does not create a user (6294603)The Delegated Administrator commadmin utility with the -S mail,cal option does not create a user in the default domain. Workaround: This problem occurs if you upgrade Access Manager to version 7.1 but you do not upgrade Delegated Administrator. If you do not plan to upgrade Delegated Administrator, follow these steps:
Delegated Administrator commadmin utility does not create an organization (6292104)The Delegated Administrator commadmin utility with the -S mail,cal option does not create an organization. Workaround: See the workaround for the previous problem. Configuration Issues
Incorrect console redirection behind a load balancer (6480354)If you have Access Manager instances deployed behind a load balancer, login to the Access Manager Console may be redirected to one of the Access Manager instances rather than to the load balancer. The URL in the browser also changes to the Access Manager instance. For example, this problem can occur if you login into the Console using this URL: http://loadbalancer.example.com/amserver/realm This redirection can occur in both Realm mode and Legacy mode deployments. There are two workarounds for this issue. You can use either one:
Notification URL needs to be updated for Access Manager SDK installation without web container (6491977)If you install the Access Manager SDK without a web container by running the Java ES 5 installer with the Configure Now option, the com.iplanet.am.notification.url property in the AMConfig.properties file is set to NOTIFICATION_URL. If you don't perform any additional web container configuration, users will not receive notifications from the remote Access Manager server. Workaround: Reset this property as follows: com.iplanet.am.notification.url="" Password Reset service reports notification errors when a password is changed (6455079)When a password is changed, Access Manager submits the email notification using an unqualified sender name Identity-Server, which results in errors entries in the amPasswordReset logs. For example:
Workaround: The following workaround is for Solaris systems. For other platforms such as Linux, Windows, or HP-UX, adjust the base installation directory for the specific platform.
Account Locking feature fails to send email notification when the user's account is locked (6760137)If the Account Locking feature is enabled and a user is locked out after a defined number of failures, an email notification is not sent. Workaround. Change the lockOutEmailFrom property as described in Step 2 of the workaround for Password Reset service reports notification errors when a password is changed (6455079) and then restart Access Manager server. 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 not updated if you install Access Manager on the second (and subsequent) servers. Workaround: Add the Realm/DNS aliases and platform server list entries manually. For the steps, see the section Adding Additional Instances to the Platform Server List and Realm/DNS Aliases in Sun Java System Access Manager 7.1 Postinstallation Guide. Data validation for required attributes in the services (6308653)Access Manager 7.1 enforces required attributes in service XML files to have default values. Workaround: If you have services with required attributes that do not have values, add values for the attributes and then reload the service. Document workaround for deployment on a secure WebLogic 8.1 instance (6295863)If you deploy Access Manager 7.1 into a secure (SSL enabled) BEA WebLogic 8.1 SP4 instance, an exception occurs during the deployment of each Access Manager web application. Workaround: Follow these steps:
The amconfig script does not update the realm/DNS aliases and platform server list entries (6284161)In a multiple server deployment, the amconfig script does not update the realm/DNS aliases and platform server list entries for additional Access Manager instances. Workaround: Add the Realm/DNS aliases and platform server list entries manually. For the steps, see the section Adding Additional Instances to the Platform Server List and Realm/DNS Aliases in Sun Java System Access Manager 7.1 Postinstallation Guide. Default Access Manager mode is realm in the configuration state file template (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: AM_REALM = disabled Performance IssuesIn Realm mode, creation of a new group generates Group Admin with ACIs that never get used (6485695)If Access Manager is installed in Realm mode, whenever a new group is created, Access Manager dynamically creates a new Group Admin with the ACIs necessary to manage the group. In Realm mode, these Group Admin ACIs are not used. Directory Server, however, still evaluates them while processing entries under the suffix, which can degrade Access Manager performance, particularly if a deployment creates a large number of groups. Workaround: The workaround for this problem involves two parts:
Preventing Group Admin ACIs From Being Created The following procedure prevents Access Manager from creating a Group Admin and corresponding ACIs whenever a new group is created. Note – This procedure permanently prevents the creation of Group Admins and corresponding ACIs whenever a new group is created. Use this procedure only if this behavior is appropriate for your specific deployment.
Removing Existing Group Admin ACIs Note – The following procedure uses the ldapsearch and ldapmodify utilities to find and remove the Group Admin ACIs. If your deployment is using Directory Server 6.0, you can also use the Directory Server Control Center (DSCC) or the dsconf command to perform these functions. For more information, see the Directory Server 6.0 documentation: http://docs.sun.com/app/docs/coll/1224.1 The following procedure removes Group Admin ACIs that already exist in Directory Server.
Access Manager Console Issues
New Access Manager Console cannot set the CoS template priorities (6309262)The new Access Manager 7.1 Console cannot set or modify a Class of Service (CoS) template priority. Workaround: Login to the Access Manager 6 2005Q1 Console to set or modify a CoS template priority. Old console appears when adding Portal Server related services (6293299)Portal Server and Access Manager are installed on the same server. With Access Manager installed in Legacy mode, login to the new Access Manager Console using /amserver. If you choose an existing user and try to add services (such as NetFile or Netlet), the old Access Manager Console (/amconsle) suddenly appears. Workaround: None. The current version of Portal Server requires the Access Manager 6 2005Q1 Console. Console does not return the results set from Directory Server after reaching the resource limit (6239724)Install Directory Server and then Access Manager with the existing DIT option. Login to the Access Manager Console and create a group. Edit the users in the group. For example, add users with the filter uid=*999*. The resulting list box is empty, and the console does not display any error, information, or warning messages. Workaround: The group membership must not be greater than the Directory Server search size limit. If the group membership is greater, change the search size limit accordingly. Add ContainerDefaultTemplateRole attribute after data migration (4677779)In Legacy mode, he user's role does not display under an organization that was not created in Access Manager. In debug mode, the following message is displayed: ERROR: DesktopServlet.handleException() com.iplanet.portalserver.desktop.DesktopException: DesktopServlet.doGetPost(): no privilige to execute desktop This error becomes evident after the Java ES installer migration scripts are run. The ContainerDefaultTemplateRole attribute is not automatically added to the organization when the organization is migrated from an existing directory information tree (DIT) or from another source. Workaround: Use the Directory Server console to copy the ContainerDefaultTemplateRole attribute from another Access Manager organization and then add it to the affected organization. Command Line IssueOrganization Admin role is fails to create a new user with the amadmin command line utility (6480776)An administrator assigned the Organization Admin role is not able to create a new user with the amadmin command line utility due to incorrect logging privileges. Workaround: Both the Organization Admin and the Top-level admin may set the permissions. To do so through the Administration Console:
SDK and Client Issues
Clients do not get notifications after the server restarts (6309161)Applications written using the client SDK (amclientsdk.jar) do not get notifications if the server restarts. Workaround: None. SDK clients need to restart after service schema change (6292616)If you modify any service schema, ServiceSchema.getGlobalSchema returns the old schema and not the new schema. Workaround: Restart the client after a service schema change. This problem is fixed in patch 1. Authentication IssuesDistributed Authentication UI server performance drops when application user has insufficient privileges (6470055)When you deploy the Distributed Authentication UI server using the default application user, performance drops significantly due to the default application user's restricted privileges. Workaround: Create a new user with appropriate privileges. To create a new user with the proper ACIs:
Incompatibility for Access Manager default configuration of Statistics Service for legacy (compatible) mode (6286628)After installation with Access Manager in legacy mode, the default configuration for the Statistics Service has changed:
Workaround: None. Attribute uniqueness broken in the top-level organization for naming attributes (6204537)After you install Access Manager, login as amadmin and add the o, sunPreferredDomain, associatedDomain, sunOrganizationAlias, uid, and mail attributes to the Unique Attribute List. If you create two new organizations with the same name, the operation fails, but Access Manager displays the “organization already exists” message rather than the expected “attribute uniqueness violated” message. Workaround: None. Ignore the incorrect message. Access Manager is functioning correctly. Session and SSO IssuesSystem creates invalid service host name when load balancer has SSL termination (6245660)If Access Manager is deployed with Web Server as the web container using a load balancer with SSL termination, clients are not directed to the correct Web Server page. Clicking the Sessions tab in the Access Manager Console returns an error because the host is invalid. Workaround: In the following examples, Web Server listens on port 3030. The load balancer listens on port 80 and redirects requests to Web Server. In the web-server-instance-name/config/server.xml file, edit the servername attribute to point to the load balancer, depending on the release of Web Server you are using. For Web Server 6.1 Service Pack (SP) releases, edit the servername attribute as follows: <LS id="ls1" port="3030" servername="loadbalancer.example.com:80" defaultvs="https-sample" security="false" ip="any" blocking="false" acceptorthreads="1"/> Web Server 6.1 SP2 (or later) can switch the protocol from http to https or https to http. Therefore, edit servername as follows: <LS id="ls1" port="3030" servername="https://loadbalancer.example.com:443" defaultvs="https-sample" security="false" ip="any" blocking="false" acceptorthreads="1"/> Using HttpSession with third-party web containersThe default method of maintaining sessions for authentications is “internal session” instead of HttpSession. The default invalid session maximum time value of three minutes is sufficient. The amtune script sets the value to one minute for Web Server or Application Server. However, if you are using a third-party web container (IBM WebSphere or BEA WebLogic Server) and the optional HttpSession, you might need to limit the web container's maximum HttpSession time limit to avoid performance problems. Policy IssuesDeletion of dynamic attributes in Policy Configuration Service causing issues in editing of policies (6299074)The deletion of dynamic attributes in Policy Configuration Service causes issues in editing of policies for this scenario:
Results are: “Error Invalid Dynamic property being set.” No policies were displayed in the list by default. After a search is done, the policies are displayed, but you cannot edit or delete the existing policies or create a new policy. Workaround: Before removing the dynamic attributes from the Policy Configuration Service, remove the references to those attributes from the policies. Server Startup IssuesDebug error occurs on Access Manager startup (6309274, 6308646)Access Manager 7.1 startup returns the debug errors in amDelegation and amProfile debug files:
Workaround: None. You can ignore these messages. AMSDK Issues
Error displayed when performing AMIdentity.modifyService (6506448)When using AMIdentity.modifyService to set desktop service dynamic attribute on a realm, Access Manager returns a null pointer exception. Workaround:Add the following property to AMConfig.properties and then restart the server.: com.sun.am.ldap.connnection.idle.seconds=7200 Group members don't show up in selected list (6459598)The problem occurs under the following conditions:
All the users in the exampleDB data store show up as available, but scarter does not show up in the Selected field. Workaround: Add the operation user=read to the supported LDAPv3 operations in the exampleadminDB data store. 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 in the fully qualified domain name (FQDN). Example: HostName.PRC.Example.COM Workaround : After installation, do not use the default Access Manager login URL. Instead, in the login URL, include the LDAP location of the default organization. For example: http://HostName.PRC.Example.COM/amserver/UI/Login?org=dc=PRC,dc=Example,dc=COM Once you've successfully logged in to Access Manager, you can eliminate the need to enter the full path to the user's organization each time you log in to Access Manager. Follow these steps:
You can now log in using any one of the following URLs:
Sub-org creation not possible from Access Manager when using amadmin (5001850)This problem occurs when multi-master replication is enabled between two Directory Servers and you attempt to create a sub-organization using the amadmin utility. Workaround: In both Directory Servers, set the nsslapd-lookthroughlimit property to -1. SSL IssueThe amconfig script fails when SSL certificate is expired. (6488777)If the Access Manager container is running in SSL mode, and the container SSL certificate is expired, amconfig fails and may cause classpath corruption. Workaround: If you have already run amconfig with an expired certificate, and the classpath is corrupted, first obtain a valid SSL certificate. Revert to the original domain.xml file, or a copy of the domain.xml file, in which the classpath is not corrupted. Then rerun the amconfig command: /opt/SUNWam/bin/amconfig -s $PWD/amsamplesilent Samples IssueClientsdk samples directory contains unwanted makefile (6490071)Sample files are included in the Client SDK. These demonstrate how to write stand-alone programs and how to write web applications. The samples are located under the directory where you generated the Makefile.clientsdk, and in the following subdirectories: .../clientsdk-samples/ .../clientsdk-webapps/ Clientsdk-samples includes samples for authentication, logging, policy and SAML stand-alone programs. Clientsdk-webapps includes samples for user management, service management, and policy programs. Each sample has a Readme.html file with instructions on compiling and running the sample program. In order to compile the samples, the makefile should be run in the corresponding sub-directory. The Top-level makefile does not compile the samples in the sub-directories. Linux OS IssuesJVM problems occur when running Access Manager on Application Server (6223676)If you are running Application Server 8.1 on Red Hat Linux, the stack size of the threads created by the Red Hat OS for Application Server is 10 Mbytes, which can cause JVM resource problems when the number of Access Manager user sessions reaches 200. Workaround: Set the Red Hat OS operating stack size to a lesser value such as 2048 or even 256 Kbytes, by executing the ulimit command before you start Application Server. Execute the ulimit command on the same console that you will use to start Application Server. For example: # ulimit -s 256; Windows and HP-UX Issues
Access Manager auto configuration failed when installing on zh_TW and es locales (6515043)Workaround: In zh_TW and es locales on HP-UX platform, Access Manager has to be configured in "Config Later" mode only. Start the JavaES installer, install the Access Manager product and exit the JavaES installer. Then invoke the Access Manager configurator as shown below:
HP-UX needs gettext binary with AM while installing Java Enterprise System full stack (6497926)There is no current workaround for this problem. Federation and SAML IssuesLogout error occurs in Federation (6291744)In realm mode, if you federate user accounts on an identity provider (IDP) and service provider (SP), terminate Federation, and then logout, an error occurs: Error: No sub organization found. Workaround: None. Globalization (g11n) Issues
Administration console components displayed in English in the zh locale (6470543)When setting the browser locale to zh, the Administration console components are displayed in English, for example the Version, Help and Logout buttons. Workaround: Set browser locale setting to zh-cn instead of zh. Current Value and New value are incorrectly displayed in the console (6476672)In the localized version of the Administration console, the labels for the Current Value and New Value attributes are incorrectly displayed as label.current.value and label.new.value, respectively. Policy condition date must be specified according to English custom (6390856)Policy condition date format labels under the Chinese locale are not displayed according to Chinese customs. Labels are proposing a date format like English date format. Related fields also accept English date format values. Workaround: For each field, follow the date format example given in the field label. Removing UTF-8 is not working in Client Detection (5028779)The Client Detection function is not working properly. Changes made in the Access Manager 7.1 Console are not automatically propagated to the browser. Workaround: There are two workarounds:
Multi-byte characters are displayed as question marks in log files (5014120)Multi-byte messages in log files in the /var/opt/SUNWam/logs directory are displayed as question marks (?). Log files are in native encoding and not always UTF-8. When a web container instance starts in a certain locale, log files will be in native encoding for that locale. If you switch to another locale and restart the web container instance, the ongoing messages will be in the native encoding for the current locale, but messages from previous encoding will be displayed as question marks. Workaround: Make sure to start any web container instances always using the same native encoding. Documentation Issues
Missing information when configuring Access Manager in SSL mode (6660610)In Chapter 8, Configuring Access Manager in SSL Mode, in Sun Java System Access Manager 7.1 Postinstallation Guide, the documentation fails to mention that the port number is changed from 80 to 443 if configure SSL for Access Manager with a secure WebServer and did not select the "Enable SSL" checkbox during installation. Access Manager supports non-ascii character passwords if Directory Server is configured to support them (6661374)Access Manager supports non-ascii characters in password fields only if the Directory Server is configured to support them. The Sun Java System Directory Server 7-Bit check plug-in should be disabled to let non-ascii characters to be stored. This flag, by default, is enabled in Directory Server 5.2 and should be disabled if non-ascii characters are needed to be entered in the userPassword entery. The 7-Bit Check Plug-in is disabled by default in Directory Server versions 6.0 and above. Document the roles and filtered roles support for LDAPv3 plug-in (6365196)After applying the respective patch, you can configure roles and filtered roles for the LDAPv3 plug-in, if the data is stored in Sun Java System Directory Server (fixes problem ID 6349959). In the Access Manager 7.1 Administration console, in LDAPv3 configuration for the “LDAPv3 Plug-in Supported Types and Operations” field, enter the values as: role: read,edit,create,delete filteredrole: read,edit,create,delete You can enter one or both of the above entries, depending on the roles and filtered roles you plan to use in your LDAPv3 configuration. Document unused properties in the AMConfig.properties file (6344530)The following properties in the AMConfig.properties file are not used: com.iplanet.am.directory.host com.iplanet.am.directory.port Document how to enable XML encryption (6275563)To enable XML encryption for either Access Manager or Federation Manager using the Bouncy Castle JAR file to generate a transport key, follow these steps:
For more information, refer to problem ID 5110285 (XML encryption requires Bouncy Castle JAR file). Documentation UpdatesTo access these documents, see the Access Manager 7.1 collection: http://docs.sun.com/coll/1292.2 A new document entitled Chapter 1, Technical Note: Deploying Access Manager Instances to an Application Server Cluster, in Technical Note: Deploying Access Manager to an Application Server Cluster has been added to the Access Manager 7 2005Q4 collection. The Sun Java System Access Manager Policy Agent 2.2 collection has also been revised to document new agents: http://docs.sun.com/coll/1322.1 Redistributable FilesSun Java System Access Manager 7.1 does not contain any files that you can redistribute to non-licensed users of the product. System Virtualization SupportSystem virtualization is a technology that enables multiple operating system (OS) instances to execute independently on shared hardware. Functionally, software deployed to an OS hosted in a virtualized environment is generally unaware that the underlying platform has been virtualized. Sun performs testing of its Sun Java System products on select system virtualization and OS combinations to help validate that the Sun Java System products continue to function on properly sized and configured virtualized environments as they do on non-virtualized systems. For information about Sun support for Sun Java System products in virtualized environments, see System Virtualization Support in Sun Java Systems Products in http://docs.sun.com/coll/1292.2. How to Report Problems and Provide FeedbackIf you have problems with Access Manager or Sun Java Enterprise System, contact Sun customer support using one of the following mechanisms:
So that we can best assist you in resolving problems, please have the following information available when you contact support:
Sun Welcomes Your CommentsSun is interested in improving its documentation and welcomes your comments and suggestions. Go to http://docs.sun.com/ and click Send Comments. Provide the full document title and part number in the appropriate fields. The part number is a seven-digit or nine-digit number that can be found on the title page of the book or at the top of the document. For example, the part number of the Access Manager Release Notes is 819-4683-22. Additional Sun ResourcesYou can find useful Access Manager information and resources at the following locations:
Accessibility Features for People With DisabilitiesTo 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 which versions are best suited for deploying accessible solutions. Updated versions of applications can be found at http://sun.com/software/javaenterprisesystem/get.html. For information on Sun's commitment to accessibility, visit http://sun.com/access. Related Third-Party Web SitesThird-party URLs are referenced in this document and provide additional, related information. Note – Sun is not responsible for the availability of third-party Web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|