[ 
https://issues.jboss.org/browse/RF-11309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

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
# deplot packaged WAR file

  was:
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

    Forum Reference: http://community.jboss.org/message/617828  (was: 
http://community.jboss.org/message/617828)

    
> form authentication broken
> --------------------------
>
>                 Key: RF-11309
>                 URL: https://issues.jboss.org/browse/RF-11309
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: core
>    Affects Versions: 4.0.0.Final
>         Environment: jboss-6.0.0.Final, richfaces-4.0.0.Final, Firefox 4 & 5
>            Reporter: Radim Hanus
>            Assignee: Jan Papousek
>         Attachments: jsf2demo-original.zip, jsf2demo-updated-mapping.zip
>
>
> 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
> # deplot packaged WAR file

--
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

        
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues

Reply via email to