Uploaded image for project: 'Qpid JMS'
  1. Qpid JMS
  2. QPIDJMS-73

add support for pipelining SASL init

    Details

    • Type: New Feature
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: qpid-jms-client
    • Labels:
      None

      Description

      In the case where only one option is configured (via QPIDJMS-69) for SASL mechanism, it may also be useful to optionally support pipelining output of the SASL init frame if that is possible (depending on the mechanism, it obviously only works for some, i.e those which dont require a server initiated challenge to begin).

      Raised based on comment from Gary Tully on QPIDJMS-61:

      it would be nice to be able to preconfigure sasl mechanisms such that the sasl init could be sent before the other end sends the supported mechanisms. This greatly reduces the amount of work a proxy must do but does bypass negotiation

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              gemmellr Robbie Gemmell
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: