Doing commands such as: id and groups does not show the correct information in the following situation:
1 - Create a group-override file with an AD group that doesn't exist in ad yet.
2 - Allow vasd to process the override file so that the cache is up to date.
3 - Now create the AD group that you added to the override file.
4 - Wait for any replication that needs to occur then run:
2013-12-09 17:08:57 [debug] (2256) No deleted files to process for group overrides
2013-12-09 17:08:57 [debug] (2256) No changed files to process for group overrides
2013-12-09 17:08:57 [debug] (2256) No deleted files to process for user overrides
2013-12-09 17:08:57 [debug] (2256) No changed files to process for user overrides
Product Defect 327526
Defect fix 18.104.22.168 description:
* vasd: Override processing has been modified. It is faster now. Biggest change:
if a user/group is not found, overrides will be re-processed every loop.
An invalid entry in either file will trigger CPU/possible AD activity trying
to resolve and re-processing it every roughly 30 seconds until fixed.
NOTE: Each unknown entry will now trigger one of the following messages every
processing loop, roughly 30 seconds, similiar to access control behavior:
build_useroverride_db: Unable to find user/group from entry <%s>, will re-process in 30 seconds
build_groupoverride_db: Unable to find group from entry <%s>, will re-process in 30 seconds
Fixed in QAS 4.0.3 Maintenance Release