You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deleting a user from admin UI doesn't delete them from CHI cache person_lookup - Subsequent authentications don't pull from cached value - 2 issues
#8451
Open
E-ThanG opened this issue
Dec 21, 2024
· 1 comment
Describe the bug
In PF 14.0, when a user is deleted from the admin UI their person_lookup attributes remain in the output of pfcmd cache person_lookup dump <SNIP>AD-User-Authentication.<SNIP>.radius
Also, even though the cached values remain, when the same user attempts a new authentication their details aren't pulled from the cache. Viewing the user in the admin UI users tab shows blanks for the cached values. Once the cache times out or is cleared new authentications will pull the information from AD.
To Reproduce
Steps to reproduce the behavior:
Perform a fresh authentication (I'm using 802.1x with PEAP/MSCHAPv2) and have user attributes pulled from AD (Title, Company, Firstname, Lastname, email, telephone, address, and so on)
Find the user in the admin UI users tab, observe that all of the attributes are populated.
Disconnect device from network, delete the user from admin UI, delete the device from admin UI (If it still exists).
Check pfcmd cache person_lookup dump <SNIP>AD-User-Authentication.<SNIP>.radius, the user hasn't been deleted from the cache.
Perform a new authentication,
Find the user in the admin UI users tab, observe that the attributes haven't been retrieved from AD or the cache.
Expected behavior
Deleting a user from the admin UI (Or any other method) should also delete them from all cached locations. They should be completely fresh on their next connection.
If cached values are retained, they should be used.
Unconfirmed: Please also validate that deleting a device removes it from all cached locations as well. Deleting anything should be global and complete.
The text was updated successfully, but these errors were encountered:
Describe the bug
In PF 14.0, when a user is deleted from the admin UI their person_lookup attributes remain in the output of
pfcmd cache person_lookup dump <SNIP>AD-User-Authentication.<SNIP>.radius
Also, even though the cached values remain, when the same user attempts a new authentication their details aren't pulled from the cache. Viewing the user in the admin UI users tab shows blanks for the cached values. Once the cache times out or is cleared new authentications will pull the information from AD.
To Reproduce
Steps to reproduce the behavior:
pfcmd cache person_lookup dump <SNIP>AD-User-Authentication.<SNIP>.radius
, the user hasn't been deleted from the cache.Expected behavior
The text was updated successfully, but these errors were encountered: