glassfish
  1. glassfish
  2. GLASSFISH-20185

Enable Secure Admin page does not show the error msg from backend to user.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.0_b82_EE7MS7
    • Fix Version/s: 4.0_b84_RC1
    • Component/s: admin_gui
    • Labels:
      None

      Description

      Go to Server (Admin Server) page and click the "Secure Administration ...." button.
      This goes to the Secure Administration page. If you try to enable Secure Admin and there is error, the error msg from backend is not shown properly.

      User will see this if they try to enable secure admin without adding another admin user or add a password to the 'admin' user.

        Activity

        Hide
        Anissa Lam added a comment -
        • What is the impact on the customer of the bug?
          User will not know that they may need to add another admin user or add a password before enabling secure admin.
        • How likely is it that a customer will see the bug and how serious is the bug?
          Pretty common if user wants to enable secure admin, since out-of-box open source edition doesn't have any password set for 'admin'.
        • Is it a regression? Does it meet other bug fix criteria (security, performance, etc.)?
          yes, a regression introduced back in build 78 when fixing GLASSFISH-18429
        • What CTS failures are caused by this bug?
          CTS doesn't test console.
        • What is the cost/risk of fixing the bug?
          minimal. It is a very localized fix.
        • Is there an impact on documentation or message strings?
          No,
        • Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
          Follow the above steps and enable secure admin to ensure the error msg is shown correctly.
        • Which is the targeted build of 4.0 for this fix?
          build 84.
        Show
        Anissa Lam added a comment - What is the impact on the customer of the bug? User will not know that they may need to add another admin user or add a password before enabling secure admin. How likely is it that a customer will see the bug and how serious is the bug? Pretty common if user wants to enable secure admin, since out-of-box open source edition doesn't have any password set for 'admin'. Is it a regression? Does it meet other bug fix criteria (security, performance, etc.)? yes, a regression introduced back in build 78 when fixing GLASSFISH-18429 What CTS failures are caused by this bug? CTS doesn't test console. What is the cost/risk of fixing the bug? minimal. It is a very localized fix. Is there an impact on documentation or message strings? No, Which tests should QA (re)run to verify the fix did not destabilize GlassFish? Follow the above steps and enable secure admin to ensure the error msg is shown correctly. Which is the targeted build of 4.0 for this fix? build 84.
        Hide
        Anissa Lam added a comment -

        Log Message:
        ------------
        GLASSFISH-20185. Should include alertMsg_1.inc which doesn't check for config existence.

        Revisions:
        ----------
        61187

        Modified Paths:
        ---------------
        trunk/main/appserver/admingui/common/src/main/resources/appServer/securityAdmin.jsf

        Show
        Anissa Lam added a comment - Log Message: ------------ GLASSFISH-20185 . Should include alertMsg_1.inc which doesn't check for config existence. Revisions: ---------- 61187 Modified Paths: --------------- trunk/main/appserver/admingui/common/src/main/resources/appServer/securityAdmin.jsf

          People

          • Assignee:
            Anissa Lam
            Reporter:
            Anissa Lam
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: