04-02-2019 06:44 AM
Recently one of our security testers changed his OU, and forgot to change it back before he left for the day.
When he came back in he was denied due to not being in the correct OU. Typically when this happens, our desktop group takes the PC to their work room, puts the device back onto the network and corrects the OU. GPResult showed the PC now in the correct OU.
When they took the machine back to the users desk, it still failed to auth. Looking in the Access Tracker we show it still passing the incorrect OU information.
Cached good authentications is expected, but does clearpass also cache failed authentication credentials?
Solved! Go to Solution.
04-02-2019 06:57 AM
It does cache group lookups: Please see here for ideas on how to fix: https://community.arubanetworks.com/t5/Security/Update-Clearpass-with-fresh-AD-info/td-p/145910
*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.4 User Guide
InstantOS 8.3 User Guide
Airheads Learning Videos
Aruba Central Documentation
Sign up for Security Alerts
Aruba Technical Webinars