For SAML, duplicate Trusted Partner console edit errors (6326634)
Remote logging is not working for amConsole.access and amPasswordReset.access (6311786)
Adding more amadmin properties in the console is changing the amadmin user password (6309830)
New Access Manager Console cannot set the CoS template priorities (6309262)
Exception error occurs when adding a group to a user as a policy admin user (6299543)
In legacy mode, you cannot delete all users from a role (6293758)
Cannot add, delete, or modify Discovery Service resource offerings (6273148)
Wrong LDAP bind password should give error for the subject search (6241241)
Access Manager cannot create an organization under a container in legacy mode (6290720)
Old console appears when adding Portal Server related services (6293299)
In the Access Manager Console, create SAML Trusted Partner under the Federation > SAML tab. If you try to duplicate the Trusted Partner, errors occur.
Workaround: None. This problem is fixed in patch 1. See Access Manager 7 2005Q4 Patch 1 for information about applying the patch for your specific platform.
When remote logging is configured, all logs are written to the remote Access Manager instance except amConsole.accessand amPasswordReset.access for the password reset information. The log record is not written anywhere.
Workaround: None.
Adding or editing some of the properties for the amadmin user in the administration console causes the amadmin user password to change.
Workaround: None. This problem is fixed in patch 1. See Access Manager 7 2005Q4 Patch 1 for information about applying the patch for your specific platform.
The new Access Manager 7 2005Q4 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.
The Access Manager Console returns an exception error when you add a group to a user as a policy admin user.
Workaround: None.
In legacy mode, if you try to delete all users from a role, a user is left.
Workaround: Try again to delete the user from the role.
The Access Manager Administration Console does not allow you to add, delete, or modify the resource offerings for a user, role, or realm.
Workaround: None. This problem is fixed in patch 1. See Access Manager 7 2005Q4 Patch 1 for information about applying the patch for your specific platform.
The Access Manager Administration Console is not returning an error when the wrong LDAP bind password is used.
Workaround: None.
If you create a container and then try to create an organization under the container, Access Manager returns a “uniqueness violation error”.
Workaround: None.
Portal Server and Access Manager are installed on the same serve. 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.
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.