You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2017/06/29 12:36:00 UTC
[jira] [Updated] (QPID-7789) [Java Broker, WMC] The webclient sasl
implementation should always answer a challenge by sending back a response.
[ https://issues.apache.org/jira/browse/QPID-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-7789:
-----------------------------
Description:
Currently the client does not always send back a response to a challenge. For example in the SCRAM case when the client receives the server-final message it knows that the negotiation completed but in certain circumstances the broker might need another challenge/response round-trip.
The client should respect the broker's wish and always respond to challenges. The response would be empty if the client thinks the negotiation finished.
In addition it should probably be easier for the client to detect whether a message from the broker is a outcome with additional data or a challenge. Currently the only distinction is that the challenge carries a "id" while the outcome with data does not.
This relates to QPID-7787.
was:
Currently the client does not always send back a response to a challenge. For example in the SCRAM case when the client receives the server-final message it knows that the negotiation completed but in certain circumstances the broker might need another challenge/response round-trip.
The client should respect the brokers wish and always respond to challenges. The response would be empty if the client thinks the negotiation finished.
In addition it should probably be easier for the client to detect whether a message from the broker is a outcome with additional data or a challenge. Currently the only distinction is that the challenge carries a "id" while the outcome with data does not.
This relates to QPID-7787.
> [Java Broker, WMC] The webclient sasl implementation should always answer a challenge by sending back a response.
> -----------------------------------------------------------------------------------------------------------------
>
> Key: QPID-7789
> URL: https://issues.apache.org/jira/browse/QPID-7789
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Lorenz Quack
> Fix For: qpid-java-broker-7.0.0
>
>
> Currently the client does not always send back a response to a challenge. For example in the SCRAM case when the client receives the server-final message it knows that the negotiation completed but in certain circumstances the broker might need another challenge/response round-trip.
> The client should respect the broker's wish and always respond to challenges. The response would be empty if the client thinks the negotiation finished.
> In addition it should probably be easier for the client to detect whether a message from the broker is a outcome with additional data or a challenge. Currently the only distinction is that the challenge carries a "id" while the outcome with data does not.
> This relates to QPID-7787.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org