AD accounts not locking after bad attempts limit is reached
Bug 26011
* cache: The srvinfo joined domain entry was made without a timestamp, so next
call could remove it due to being 'expired'. This would be seen as requests
to AD not using one DC, instead following DNS responses and possibly random DC
for each per-process call. Noticed when users wouldn't lock out as the bad
attempts were spread amoungst various DCs
Upgrade to QAS 4.0.3 maintenance version. Please see the following link for a list of fixes and a link to the download:
https://support.quest.com/Search/SolutionDetail.aspx?id=SOL82767
Seen on QAS 4.0.3.91 version
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center