[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-251) Return server assigned client id to client
[ https://issues.oasis-open.org/browse/MQTT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59457#comment-59457 ] Andrew Schofield commented on MQTT-251: --------------------------------------- The point about client ID "stealing" is valid, but my view is that's really about establishing the right to use a particular client ID. I think that's also an aspect of access control. You could for example use a client cert and require that the client ID must match the common name, or something like that. > Return server assigned client id to client > ------------------------------------------ > > Key: MQTT-251 > URL: https://issues.oasis-open.org/browse/MQTT-251 > Project: OASIS Message Queuing Telemetry Transport (MQTT) TC > Issue Type: Improvement > Components: futures > Reporter: Allan Stockdill-Mander > > In the 3.1.1 specification section 3.1.3.1 http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html#_Toc398718031 it is permitted for a client to connect with a zero length client id, the server internally uses a unique identifier for that client but the client does not know the idenfitier and is required to connect with clean session true. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]