[OASIS Issue Tracker] Updated: (MQTT-77) Should the Connect packet User Name and Password fields be binary rather than UTF-8

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/MQTT-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Coppen updated MQTT-77:
-------------------------------

              Summary: Should the Connect packet User Name and Password fields be binary rather than UTF-8  (was: Should the Connect packet Useri Name and Password fields be binary rather than UTF-8)
    Affects Version/s: 3.1.1

> Should the Connect packet User Name and Password fields be binary rather than UTF-8
> -----------------------------------------------------------------------------------
>
>                 Key: MQTT-77
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-77
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.1.1
>            Reporter: Andrew Banks
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira