2 Replies Latest reply on Dec 9, 2010 5:21 PM by skoithodan

    jmx-console and web-console authentication stopped working

    skoithodan

      I configured jmx-console and web-console authentication in dev and prod one year back and it was working as expected till now. But now in prod it stopped working and no longer forcing authentication. All required files web.xml, jboss-web.xml, user properties files and login-config.xml are not modified. In dev it still working. I am not able to see any difference in these files and not able to find out why is this happening. There is no error when accessing these consoles and it go to these consoles directly.

      Is there any setting that will bypass this authentication once it is configured?

      I am using JBoos_4.2.2 GA.

      Any help will be highly appreciated

       

      Thanks

      Mathew

        • 1. Re: jmx-console and web-console authentication stopped working
          kaba

          Can you please post your config file or checkt it.

          The following file are concerned:

           

          login-config.xml in deploy/conf directory

          *.propertie in deploy/conf/props/ directory/

          jboss-web.xml and web.xml in deploy/jmx-console.war/META-INF

          Pay attention your directory structure may be differents  as some  are JBoss Version dependant .

          Check well your config file you will find differences.

          • 2. Re: jmx-console and web-console authentication stopped working
            skoithodan

            Hi Thanks for the reply.

             

            After a long debugging I found the issue. The issue is in web.xml under jboss-web.deployer/conf I added the following entry to redirect from 8080 to 8443. This I did only couple of months back. If this code is there jmx-consloe or web-console won't force authentication and go directly to the page. If I comment that it force authentication in these two consoles.

             

            <security-constraint>

                 <web-resource-collection>

                    <web-resource-name>Protected Context</web-resource-name>

                      <url-pattern>/*</url-pattern>

                 </web-resource-collection>

              <!-- auth-constraint goes here if you requre authentication -->

                 <user-data-constraint>

                    <transport-guarantee>CONFIDENTIAL</transport-guarantee>

                 </user-data-constraint>

            </security-constraint>

             

            I am not sure how these two are related. Can you please help to make these two work  together?

             

            thanks

            Mathew