VisualVM
  1. VisualVM
  2. VISUALVM-559

Need user feedback when determined that username/password may be sent via an insecure connection

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.0, 1.0.1, 1.1, 1.1.1, 1.2, 1.2.1, 1.2.2, 1.3, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5
    • Fix Version/s: 1.3.6
    • Component/s: plugins
    • Labels:
      None

      Description

      VisualVM should be updated so that the dialog box for connecting to a
      remote RMI host-and-port gets a checkbox saying "connection must use SSL".

      When true, VisualVM will use the following JMXServiceURL:

      service:jmx:rmissl:///jndi/rmi://hostName:portNum/jmxrmi

      When false (default value), VisualVM will use the following JMXServiceURL:

      service:jmx:rmi:///jndi/rmi://hostName:portNum/jmxrmi

      @ luis-miguel.alventosa@sun.com 2005-2-11 14:10:59 GMT

      If SSL is checked, set a new property jmx.remote.x.check.stub to true for the
      environment map when VisualVM connects to the target VM.

        Activity

        Hide
        thurka added a comment - - edited

        We used similar fix to JConsole. VisualVM will check for SSL-protected RMI registry and warn user that username/password will be sent in plain text. Fixed in revision 3232.

        Show
        thurka added a comment - - edited We used similar fix to JConsole. VisualVM will check for SSL-protected RMI registry and warn user that username/password will be sent in plain text. Fixed in revision 3232.
        Hide
        rainerfrey added a comment -

        The way this is fixed is very annoying. We use monitoring within a trusted network, and therefore don't use SSL. With 1.3.6, there is now a warning for every saved connection in VisualVM at startup (about 2 dozens in my case). Could this please be changed in a way more along the lines of the original report. that a connection can be marked to require a secure connection, and does not warn if it is not required.

        Show
        rainerfrey added a comment - The way this is fixed is very annoying. We use monitoring within a trusted network, and therefore don't use SSL. With 1.3.6, there is now a warning for every saved connection in VisualVM at startup (about 2 dozens in my case). Could this please be changed in a way more along the lines of the original report. that a connection can be marked to require a secure connection, and does not warn if it is not required.
        Hide
        jsedlacek added a comment -

        Improved for the next VisualVM version in revision 3326.

        Show
        jsedlacek added a comment - Improved for the next VisualVM version in revision 3326.

          People

          • Assignee:
            thurka
            Reporter:
            yardus
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: