Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
5.1.0.5
-
None
Description
The new overload of MetaDataLocator.findMeta, which takes a page name, does not check the configured defaults, as the other overload does. This breaks the documented means of adding SECURE_PAGE meta data to multiple pages (which is to contribute them to the MetaDataLocator configuration), since RequestSecurityManagerImpl.isSecure uses this new method.