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.:
The problem occurs under the following conditions:
Define a realm with the following realm configuration:
Top-level realm is amroot. A subrealm is example.com.
The subrealm example.com has two data stores: exampleDB and exampledminDB.
The data store exampleDB contains all the users starting at dc=example,dc=com. Supported LDAPv3 operations is set to user=read,write,create,delete,service.
The data store exampleadminDB contains an admin group for the realm. The admin group is DN: cn=example.com Realm Administrators,ou=Groups,dc=example,dc=com. This group has a single member, scarter. Supported LDAPv3 operations is set to group=read,write,create,delete.
Click the Subjects tab, then Groups, then the entry for example.com Realm Administrators.
Click the User tab.
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.
The problem may be due to the use of mixed-case (both uppercase and lowercase) characters in the fully qualified domain name (FQDN).
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:
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:
Go to the Realm tab in Realm mode, or go to the Organization tab in Legacy mode.
Click the default realm or organization name.
In this example, click prc.
Change all uppercase characters in the Realm/DNS Alias value to lowercase characters.
In this example, add the all-lowercase value hostname.prc.example.com to the list, and then remove the mixed-case HostName.PRC.Example.COM value from the list.
Click Save, and log out of Access Manager Console.
You can now log in using any one of the following URLs:
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.