reorganize SASL code so that it doesn't use streams-based API

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P3
    • 1.4.0
    • Affects Version/s: 1.4.0
    • Component/s: core-libs
    • None
    • beta
    • sparc
    • solaris_2.6

      The SASL code currently uses getInputStream/getOutputStream for doing
      integrity and privacy over the negotiated channel. Use more generic
      wrap/unwrap methods instead so that the code is less dependent on streams
      and can work with NIO.

            Assignee:
            Rosanna Lee (Inactive)
            Reporter:
            Rosanna Lee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: