Removing RAM Registered Users
When running App Scan against RAM App Scan uses one userid for scans but for some reason a large number of "corrupted" user ids (different sets of html text and special characters like @#$%^) get introduced as users in RAM. This occurs when you have Microsoft Active Directory installed. When you search for all users in RAM you get these corrupted ids at the top of the search list. Is there a way to remove users from the internal RAM directory as app scan is only required to be run once on a RAM installation?
Running RAM 7.5.0.1 and WAS (standard) 7.0.0.13 and SQL DB.
Running RAM 7.5.0.1 and WAS (standard) 7.0.0.13 and SQL DB.
2 answers
On 3/17/2011 12:38 AM, besch wrote:
If app scan is required only once then make a backup of the database and
persist area before running the app scan, and then after the app scan
restore the database and persist area.
But I'm concerned that you are getting corrupted user ids. That doesn't
make sense. RAM wouldn't create any users except those that can validly
login. That tells me there is something wrong with how you configured
Websphere/RAM for LDAP access.
--
Rich Kulp
Rational Asset Manager developer
When running App Scan against RAM App Scan uses one userid for scans
but for some reason a large number of "corrupted" user ids
(different sets of html text and special characters like @#$%^) get
introduced as users in RAM. This occurs when you have Microsoft
Active Directory installed. When you search for all users in RAM you
get these corrupted ids at the top of the search list. Is there a way
to remove users from the internal RAM directory as app scan is only
required to be run once on a RAM installation?
Running RAM 7.5.0.1 and WAS (standard) 7.0.0.13 and SQL DB.
No there isn't. Users cannot be removed.
If app scan is required only once then make a backup of the database and
persist area before running the app scan, and then after the app scan
restore the database and persist area.
But I'm concerned that you are getting corrupted user ids. That doesn't
make sense. RAM wouldn't create any users except those that can validly
login. That tells me there is something wrong with how you configured
Websphere/RAM for LDAP access.
--
Rich Kulp
Rational Asset Manager developer