|Applies To||RSA Product Set: SecurID|
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.1.0 patch 5
|Issue||When logged into the Security Console and selecting Settings > Self Service Settings and then selecting Identity Sources the following error displays:|
There was a problem processing your request.
No Identity Source is available
Identity sources are configured and users are seen in the Security Console.
Users can log onto self-service console page and request a token.
Admins can assign tokens and see both internal and external identity sources.
|Cause||In the Security Console, set logging to verbose|
Review the /opt/rsa/am/....imsTrace.log fopr messages such as:
2014-10-21 13:10:40,617, [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'], (AbstractPropertiesSynchronizer.java:695), trace.com.rsa.ims.security.keymanager.sys.AbstractPropertiesSynchronizer, WARN, den-prod-auth-01.quickplay.local,,,,Database information not found
com.rsa.common.DataNotFoundException: No data for 0000-Global-0000.ims.sso.filter.properties found
The reason for this error is that there is a difference in the enrollment of identity sources is different from Authentication Manager 7.1 to Authentication Manager 8.0/8.1; that is, only internal database users are enrolled in Authentication Manager 8.0/8.1. Migration from 7.1 to 8.0/8.1 has introduced the above issue. The root cause of the defect is how the migration is handled for user enrollment.
|Resolution||A fix for this issue is scheduled for Authentication Manager 8.1 patch 6 or patch 7.|
Note that during Quick Setup another user name may have been selected. Use that user name to login.
The above query should resolve the issue. Make sure after running the query, the internal database is added for enrollment if required from Self-Service Settings > Identity Sources.
|Notes||Same symptom as Jira AM-27838/AM-26825 which were fixed in patch 1|