Bug ID 501338: AD log message when cache init failed because of empty admin credentials

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4

Fixed In:
12.0.0

Opened: Jan 16, 2015
Severity: 3-Major

Symptoms

Some AD Query options require AD Group or AD PSO cache.The options are: "fetch nested groups", "fetch primary group" or any password management option. Starting from APM 11.5.0, a cache is associated with a server object, so there is no way to build a cache using a user's credentials. If administrator credentials are not specified for the associated AAA AD Server object, then cache initialization fails silently.

Impact

It is not obvious why cache initialization failed.

Conditions

A feature that requires a cache is configured for AD Query.

Workaround

None

Fix Information

Now if cache init failure occurs, an error message is logged into /var/log/apm logfile to explain the reason, which is administrator credentials required.

Behavior Change