Bug ID 1103369: DELETE of REST auth token does not result in deletion of the pamcache token file on a multi slot VIPRION chassis or vCMP guest

Last Modified: Jan 24, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,, 17.0.0,

Fixed In:,,,

Opened: Apr 27, 2022
Severity: 3-Major


Deletion of REST tokens from cache /var/run/pamcache is not happening when the token expires or is deleted.


The deleted token is still present in the cache. Memory is consumed as a cache is stored in an in-memory filesystem


A large number of REST auth tokens get created. Multi-slot VIPRION or Multi-slot vCMP Guest.


Remove the pamcache directory from the set being acted upon by "csyncd" by running the following commands in bash: # clsh "cp /etc/csyncd.conf /etc/csyncd.conf.$(date +%Y%m%d_%H%M%S)" # clsh "sed -i '/run\/pamcache/,+2s/^/#/' /etc/csyncd.conf" # clsh "bigstart restart csyncd"

Fix Information

Auth tokens in /run/pamcache are deleted as required.

Behavior Change