Uploaded image for project: 'OASIS Message Queuing Telemetry Transport (MQTT) TC'
  1. OASIS Message Queuing Telemetry Transport (MQTT) TC
  2. MQTT-77

Should the Connect packet User Name and Password fields be binary rather than UTF-8

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.1
    • Fix Version/s: 3.1.1
    • Component/s: core
    • Labels:
      None
    • Proposal:
      Hide

      >> As per current working draft << The User Name field MUST contain a UTF8 encoded string.

      >> Change spec to allow binary data in the password field << The Password field contains 0 to 65535 bytes of binary data prefixed with a 2 byte length field which indicates the number of bytes used.

      Show
      >> As per current working draft << The User Name field MUST contain a UTF8 encoded string. >> Change spec to allow binary data in the password field << The Password field contains 0 to 65535 bytes of binary data prefixed with a 2 byte length field which indicates the number of bytes used.
    • Resolution:
      Hide

      Fixed in WD14

      Show
      Fixed in WD14

      Description

      The WD10 draft says :

      3.1.3.4 User Name
      If the User Name Flag is set to 1, this is the next field in the payload. User Name is a UTF-8 encoded string and can be used by the server for authentication, and authorization.
      3.1.3.5 Password
      If the Password Flag is set to 1, this is the next field in the payload.,Password is a UTF-8 encoded string and can be used by the server for authentication of the client

      This allows implementer s to display these fields on admin screens but prevents them from being from carrying binary tokens.

      We don't need to change the wire format to encode this if the binary field is prefixed with a 2 byte length.

        Attachments

          Activity

            People

            • Assignee:
              andrew_banks Andrew Banks (Inactive)
              Reporter:
              andrew_banks Andrew Banks (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: