Would this problem be fixed by updating to 4.1.8 or 4.2.1 or later?
(... I confirmed that the problem occurs in 4.1.7, and that updating the PAM to 4.2.0(.826) resolves it.)
Also, if this is a known problem, is there a DE number or manual that mentions it?
Or is this an issue that has been identified internally?