It's very hard to debug the SASL authentication failures, because remoting connection doesn't log information about the failure cause. IMO the problem is in method org.jboss.remoting3.ConnectionImpl.receiveAuthResponse(int, byte[]), namely this piece of code:

                  try {
                      challenge = saslServer.evaluateResponse(response);
                  } catch (SaslException e) {
                      try {
                          connectionHandler.sendAuthReject(id);
                      } catch (IOException e1) {
                          authMap.remove(auth);
                          auth.dispose();
                          log.trace("Failed to send auth reject", e1);
                      }
                      return;
                  }
      

      The catch block consumes the exception without letting user know what happened.

      Suggested fix:
      Print Stack trace on TRACE log level in the catch block.

              dlloyd@redhat.com David Lloyd
              josef.cacek@gmail.com Josef Cacek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: