[
https://issues.apache.org/jira/browse/ROL-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Johnson resolved ROL-2100.
--------------------------------
Resolution: Fixed
Fixed by removing the no longer needed schema enforcement filter:
https://github.com/apache/roller/commit/0d42c6d20f33343d5a99851ad7bae0b5b9f2ef06
> secure.login and schemaenforement.https.urls broken
> ---------------------------------------------------
>
> Key: ROL-2100
> URL: https://issues.apache.org/jira/browse/ROL-2100
> Project: Apache Roller
> Issue Type: Bug
> Components: Authentication, Roles and Access Controls
> Affects Versions: 5.1.2
> Reporter: David Johnson
> Assignee: David Johnson
> Priority: Minor
> Fix For: 5.2.3
>
>
> The two Roller configuration properties mentioned in the summary no longer
> work in Roller. Apparently they were broken when we upgraded to some newer
> version of Spring Security.
> The relevant code is in RollerContext. initializeSecurityFeatures().
> As a work-around, one may be able to configure secure login behavior by
> modifying the Spring Security configuration file (security.xml) directly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
