[
https://issues.apache.org/jira/browse/AMQ-5288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-5288:
------------------------------
Description:
Currently the MQTT protocol converter doesn't really try to map connection
error into the MQTT spec codes. We need to distinguish between bad client Ids
and authentication issues. We should return codes that match these error
conditions
InvalidClientIdException - 0x02 Connection Refused, identifier rejected
CredentialException - 0x04 Connection Refused, bad user name or password
SecurityException - 0x05 Connection Refused, not authorized
was:
Currently the MQTT protocol converter doesn't really try to map connection
error into the MQTT spec codes. We need to distinguish between bad client Ids
and authentication issues. We should return codes that match these error
conditions
IvalidClientIdException - 0x02 Connection Refused, identifier rejected
CredentialException - 0x04 Connection Refused, bad user name or password
SecurityException - 0x05 Connection Refused, not authorized
> Return proper error codes to MQTT client on failed connect.
> -----------------------------------------------------------
>
> Key: AMQ-5288
> URL: https://issues.apache.org/jira/browse/AMQ-5288
> Project: ActiveMQ
> Issue Type: Bug
> Components: MQTT
> Affects Versions: 5.10.0
> Reporter: Timothy Bish
> Fix For: 5.11.0
>
>
> Currently the MQTT protocol converter doesn't really try to map connection
> error into the MQTT spec codes. We need to distinguish between bad client
> Ids and authentication issues. We should return codes that match these error
> conditions
> InvalidClientIdException - 0x02 Connection Refused, identifier rejected
> CredentialException - 0x04 Connection Refused, bad user name or password
> SecurityException - 0x05 Connection Refused, not authorized
--
This message was sent by Atlassian JIRA
(v6.2#6252)
