Computer Accessories User Manual

5. Click Save.
SDK and Client Issues
■
“Clients do not get notications 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 notications after the server restarts (6309161)
Applications written using the client SDK (amclientsdk.jar) do not get notications 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 xed in patch 1.
Authentication Issues
■
“Distributed Authentication UI server performance drops when application user has
insucient privileges (6470055)” on page 23
■
“Incompatibility for Access Manager default conguration of Statistics Service for legacy
(compatible) mode (6286628)” on page 24
■
“Attribute uniqueness broken in the top-level organization for naming attributes (6204537)”
on page 24
Distributed Authentication UI server performance drops when
application user has insucient privileges (6470055)
When you deploy the Distributed Authentication UI server using the default application user,
performance drops signicantly 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:
1. In the Access Manager console, create a new user. For example, create a user named
AuthUIuser.
Known Issues and Limitations
Sun Java System Access Manager 7.1 Release Notes 23