The Token Expiration Report hangs and does not complete. The List All User report takes a long time and does not complete. Listing user groups in the Security Console gives error:
There was a problem processing your request. Unexpected error during command com.rsa.admin.PagedSearchGroupsCommand execution." Error : Batch entry 5 INSERT INTO AM_REPORT_TKN_EXP Error : Batch entry 263 INSERT INTO AM_REPORT_TKN_EXP (REPORT_ID.
The token expiration report fails with a duplicate users error:
Choose either Workaround 1 or 2 then move to step 2.
A simple workaround is to use the Users with Token report and filtering for the token expiration time. Be careful not to select account expiration. Also the default is Last, so if you are looking for users with tokens that expire in next 90 days, be sure to change that or you may end up with empty reports or unexpected results
Open the Operations Console and navigate to Deployment Configuration > Identity Source > Mapping.Uncheck the box to Enable the use of the MemberOf attribute. Customers have confirmed that unchecking the box resolves the issue. Unchecking the option to use the MemberOf attribute switches from using memberOf, to using the member attribute.
Membership Attribute. The attribute that contains the DNs of all the users and user groups that are members of a user group.
User MemberOf Attribute. Enables the system to resolve membership queries by using the value specified for the MemberOf attribute.
MemberOf Attribute. The attribute of users and user groups that contains the DNs of the user groups to which they belong.
Next, modify the identity source connection configuration by changing the User Group Base DN from dc=company,dc=net to be more detailed, such as OU=remoteusers,OU=finance,DC=company,DC=net.
From the Operations Console select Maintenance > Flush Cache > . Choose the option to flush cache for all objects.
Open the Security Console and select Reporting > Reports > Add New and run the Token Expiration Report.
This issue has been reported in defect AM-28040 and it is resolved in Authentication Manager 8.1 patch 4, scheduled for release in September 2014.
Patch 4 includes a partial fix for AM-28040. A more complete fix (AM-28656) is expected in early 2015.
In its simplest implementation, round-robin DNS works by responding to DNS requests not only with a single IP address, but a list of IP addresses of several servers that host identical services. The order in which IP addresses from the list are returned is the basis for the term round robin. RSA Identity Source should be configured with an IP address of a single domain controller, and not for a round-robin DNS name, or a directory load balancer. The IP address belonging round robin DNS cannot be used in identity source connection configuration.