Known Issues and Limitations
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
Access Manager Console Issues
■“New Access Manager Console cannot set the CoS template priorities (6309262)” on page 21
■“Old console appears when adding Portal Server related services (6293299)” on page 21
■“Console does not return the results set from Directory Server after reaching the resource limit (6239724)” on page 22
■“Add ContainerDefaultTemplateRole attribute after data migration (4677779)” on page 22
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.
Sun Java System Access Manager 7.1 Release Notes | 21 |
