[ https://issues.jboss.org/browse/RF-11309?page=com.atlassian.jira.plugin.s... ] Jay Balunas updated RF-11309: ----------------------------- Fix Version/s: 4.1.0.Milestone2 Priority: Critical (was: Major) Component/s: compatibility core Forum Reference: http://community.jboss.org/message/617828 (was: http://community.jboss.org/message/617828) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11309?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11309: ------------------------------- Fix Version/s: 4.1.0.CR1 (was: 4.1.0.Tracking) Forum Reference: http://community.jboss.org/message/617828 (was: http://community.jboss.org/message/617828) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11309?page=com.atlassian.jira.plugin.s... ] Jay Balunas commented on RF-11309: ---------------------------------- Comment from jira: OK I've examined this problem thoroughly and find out following: reported behaviour can be reproduced when using FORM authentication and RF4 jars are available in WEB-INF/lib when I delete RF4 jars from WEB-INF/lib (note that referenced sample doesn't use RF4 at all) and use FORM authentication the login works as expected having both RF4 and BASIC authentication the login works as expected the discussion title change to reflect my latest research -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11309?page=com.atlassian.jira.plugin.s... ] Jay Balunas updated RF-11309: ----------------------------- Component/s: (was: compatibility) Forum Reference: http://community.jboss.org/message/617828 (was: http://community.jboss.org/message/617828) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11309?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak reassigned RF-11309: ---------------------------------- Assignee: Jan Papousek (was: Pavol Pitonak) Jan, please verify. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11309?page=com.atlassian.jira.plugin.s... ] Jan Papousek updated RF-11309: ------------------------------ Attachment: jsf2demo-updated-mapping.zip -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11309?page=com.atlassian.jira.plugin.s... ] Jan Papousek updated RF-11309: ------------------------------ Description: described in forum thread in a great detail, simple war to reproduce enclosed as well *steps to deploy the test application to JBoss AS 7.0.2* (from forum) # download and extract jsf2demo.zip (see attachments) # package contained maven project # add a security domain into standalone.xml: {code} <security-domain name="jmx-console"> <authentication> <login-module code="UsersRoles" flag="required"> <module-option name="usersProperties" value="${jboss.server.config.dir}/jmx-console-users.properties"/> <module-option name="rolesProperties" value="${jboss.server.config.dir}/jmx-console-roles.properties"/> </login-module> </authentication> </security-domain> {code} # copy both *jmx-console-users.properties* and *jmx-console-roles.properties* from jboss-6.0.0.Final/server/default/conf/props to jboss7/standalone/configuration was:described in forum thread in a great detail, simple war to reproduce enclosed as well Forum Reference: http://community.jboss.org/message/617828 (was: http://community.jboss.org/message/617828) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11309?page=com.atlassian.jira.plugin.s... ] Jan Papousek commented on RF-11309: ----------------------------------- When I change servlet mapping in web.xml file, it works correctly on JBoss AS 7.0.2: {code} <?xml version="1.0" encoding="UTF-8"?> <web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" version="2.5"> <servlet> <servlet-name>Faces Servlet</servlet-name> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <!-- <url-pattern>*.xhtml</url-pattern> --> <url-pattern>/faces/*</url-pattern> </servlet-mapping> <welcome-file-list> <!-- <welcome-file>home.xhtml</welcome-file> --> <welcome-file>faces/home.xhtml</welcome-file> </welcome-file-list> <security-constraint> <web-resource-collection> <web-resource-name>Secure</web-resource-name> <url-pattern>*.xhtml</url-pattern> </web-resource-collection> <auth-constraint> <role-name>JBossAdmin</role-name> </auth-constraint> </security-constraint> <login-config> <auth-method>FORM</auth-method> <realm-name>JBoss JMX Console</realm-name> <form-login-config> <!-- <form-login-page>/login.xhtml</form-login-page> --> <form-login-page>/faces/login.xhtml</form-login-page> <!-- <form-error-page>/loginError.xhtml</form-error-page> --> <form-error-page>/faces/loginError.xhtml</form-error-page> </form-login-config> </login-config> <security-role> <role-name>JBossAdmin</role-name> </security-role> </web-app> {code} See jsf2demo-updated-mapping.zip file in attachments. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11309?page=com.atlassian.jira.plugin.s... ] Jan Papousek edited comment on RF-11309 at 11/23/11 8:56 AM: ------------------------------------------------------------- When I change servlet mapping in web.xml file, it works correctly on JBoss AS 7.0.2: {code} <?xml version="1.0" encoding="UTF-8"?> <web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" version="2.5"> <servlet> <servlet-name>Faces Servlet</servlet-name> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <!-- <url-pattern>*.xhtml</url-pattern> --> <url-pattern>/faces/*</url-pattern> </servlet-mapping> <welcome-file-list> <!-- <welcome-file>home.xhtml</welcome-file> --> <welcome-file>faces/home.xhtml</welcome-file> </welcome-file-list> <security-constraint> <web-resource-collection> <web-resource-name>Secure</web-resource-name> <url-pattern>*.xhtml</url-pattern> </web-resource-collection> <auth-constraint> <role-name>JBossAdmin</role-name> </auth-constraint> </security-constraint> <login-config> <auth-method>FORM</auth-method> <realm-name>JBoss JMX Console</realm-name> <form-login-config> <!-- <form-login-page>/login.xhtml</form-login-page> --> <form-login-page>/faces/login.xhtml</form-login-page> <!-- <form-error-page>/loginError.xhtml</form-error-page> --> <form-error-page>/faces/loginError.xhtml</form-error-page> </form-login-config> </login-config> <security-role> <role-name>JBossAdmin</role-name> </security-role> </web-app> {code} See jsf2demo-updated-mapping.zip file in attachments. EDIT: Don't be confused from images in test application. I've added pictures to the welcome and login page to see whether mapping works correctly. was (Author: jpapouse): When I change servlet mapping in web.xml file, it works correctly on JBoss AS 7.0.2: {code} <?xml version="1.0" encoding="UTF-8"?> <web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" version="2.5"> <servlet> <servlet-name>Faces Servlet</servlet-name> <servlet-class>javax.faces.webapp.FacesServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>Faces Servlet</servlet-name> <!-- <url-pattern>*.xhtml</url-pattern> --> <url-pattern>/faces/*</url-pattern> </servlet-mapping> <welcome-file-list> <!-- <welcome-file>home.xhtml</welcome-file> --> <welcome-file>faces/home.xhtml</welcome-file> </welcome-file-list> <security-constraint> <web-resource-collection> <web-resource-name>Secure</web-resource-name> <url-pattern>*.xhtml</url-pattern> </web-resource-collection> <auth-constraint> <role-name>JBossAdmin</role-name> </auth-constraint> </security-constraint> <login-config> <auth-method>FORM</auth-method> <realm-name>JBoss JMX Console</realm-name> <form-login-config> <!-- <form-login-page>/login.xhtml</form-login-page> --> <form-login-page>/faces/login.xhtml</form-login-page> <!-- <form-error-page>/loginError.xhtml</form-error-page> --> <form-error-page>/faces/loginError.xhtml</form-error-page> </form-login-config> </login-config> <security-role> <role-name>JBossAdmin</role-name> </security-role> </web-app> {code} See jsf2demo-updated-mapping.zip file in attachments. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11309?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-11309: ---------------------------------- Assignee: (was: Brian Leathem) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11309?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11309: ------------------------------- Fix Version/s: 4.3-Tracking (was: 4.2-Tracking) Forum Reference: http://community.jboss.org/message/617828 (was: http://community.jboss.org/message/617828) Bumping to 4.3-tracking, given that a workaournd exists (changing the servlet mapping) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira