[
https://issues.apache.org/jira/browse/JSPWIKI-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jürgen Weber reopened JSPWIKI-212:
----------------------------------
For Weblogic and Geronimo the problem is still worse, because they immediately
send 403 forbidden (JSPWIKI-389).
Container managed security is orthogonal to SSL, else containers would always
require transport-guarantee CONFIDENTIAL.
If an Administrator wants container managed security, she is not bound to want
SSL, too. So transport-guarantee CONFIDENTIAL should be off by default and
commented out in web.xml. There should be a hint in a comment that it might be
necessary.
> transport-guarantee CONFIDENTIAL should be removed from web.xml
> ---------------------------------------------------------------
>
> Key: JSPWIKI-212
> URL: https://issues.apache.org/jira/browse/JSPWIKI-212
> Project: JSPWiki
> Issue Type: Improvement
> Components: Authentication&Authorization
> Affects Versions: 2.6.2
> Environment: apache-tomcat-6.0.16
> Reporter: Jürgen Weber
> Assignee: Andrew Jaquith
> Priority: Minor
>
> The default web.xml of JSPWiki contains two times
> <user-data-constraint>
> <transport-guarantee>CONFIDENTIAL</transport-guarantee>
> </user-data-constraint>
> for container managed authorization.
> But by default Tomcat has not switched on SSL, and trying to log in to
> JSPWiki you get
> Firefox can't establish a connection to the server at localhost:8443.
> By default the user-data-constraint element should be removed as it makes
> activating container managed authorization unnecessarily difficult.
> Especially as it is not easy or obvious to notice the connection between the
> cited error message and the user-data-constraint element.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
