Token Expiration Report takes long time to return and eventually failed - RSA Authentication Manager 8.1
Originally Published: 2014-06-02
Article Number
Applies To
Issue
Running a Token Expiration Report takes a long time, even few hours and then eventually it failed with an error. Users are in LDAP accounts.
Real-time System activity monitor generated as below:
Resolution
This is fixed in Authentication Manager 8.1 Patch 1 but not fully addressed the issue. It may be included in the next full fix in Patch 2.
[WORKAROUD]
This works for some user cases, but not for all cases.
This issue occurs when the Base DN value for the identity source is a root context such as "DC=RSA,DC=COM"
If the Base DN is not the root context such as " CN=USERS, DC=RSA,DC=COM" then the exception may not be thrown.
