fixed a possible bug with the new configuration whitelist