Uploaded image for project: 'TinkerPop'
  1. TinkerPop
  2. TINKERPOP-1600

Consistent use of base 64 encoded bytes for SASL negotiation

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Done
    • 3.2.3
    • 3.2.4
    • driver, server
    • None

    Description

      Gremlin Server currently uses a mix of base 64 encoded bytes and byte arrays for SASL negotiation. This can cause problems for certain serializers (like toString serialization with gryo) as the byte array won't be respected. In an effort to easily support virtually any serializer a switch to using just base 64 string is probably best.

      This can be done in such a way as to be backward compatible. The base64 SASL value will be returned in the response message status attributes map in a key called "sasl". The original byte array will continue to be returned in the response message result. Eventually, we could phase out the byte array in the result - perhaps with 3.3.0.

      Attachments

        Issue Links

          Activity

            People

              spmallette Stephen Mallette
              spmallette Stephen Mallette
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: