[OASIS Issue Tracker] (MQTT-507) Allow Server-sent AUTH packets

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

    [ https://issues.oasis-open.org/browse/MQTT-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67351#comment-67351 ] 

Ken Borgendale commented on MQTT-507:
-------------------------------------

This same issue was discussed in the TC as MQTT-431.  There was a proposal to add the ability of the server to request the client to initiate reauthentication.  The decision of the TC was to close that issue without any action.

1.  What do we think is different now that the TC would come to a different opinion?

2. Do you think that the proposal in MQTT-431 is what is desired?

> Allow Server-sent AUTH packets
> ------------------------------
>
>                 Key: MQTT-507
>                 URL: https://issues.oasis-open.org/browse/MQTT-507
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: New Feature
>    Affects Versions: 5, CSD01
>            Reporter: Dominik Obermaier
>
> The initial AUTH packet can only be sent by the client to re-authenticate. There are use cases for a server-initiated AUTH packet. 
> An example would be if login credentials are revoked on the broker side (e.g. due to administrative interventions). There is currently no way to force the client to re-send the AUTH packet. A server side AUTH challenge may help in such cases, so the client has a chance to provide valid credentials in case the original secrets are not valid anymore. 
> Another use case would be OAUTH 2.0. The JWT as Access Token may expire and the broker can notify the client that a new token is required.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)