Uploaded image for project: 'JBoss Remoting (3+)'
  1. JBoss Remoting (3+)
  2. REM3-184

Client jars from eap6.1 fail to authenticate mgmt to running eap6.3

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • 3.4.0.Beta1
    • 3.3.0.CR4
    • None

    Description

      JBDS currently has 2 sets of jars in use for connecting to remove jboss installations. One set is used to connect only to wildfly, the other set used to connect to as7x, eap6x. The wf set of jars came from the wf release (not 100% identical), and the second set of jars came entirely from the eap6.1 release.

      Jars used for the 7x/eap6x servers fail to authenticate against remoting 3.3.0.CR4 as present in eap6.3.0.DR4.

      Strangely, the wildfly jars manage to connect and authenticate to eap6.3.

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-10116 Issues that affect AS7/EAP integration to tools

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-16764 Remote EAP 6.3 does not accept password

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              darran.lofthouse@redhat.com Darran Lofthouse
              rob.stryker Rob Stryker (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: