You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2017/12/20 15:33:00 UTC
[jira] [Assigned] (PROTON-1518) Proton provides no mechanism to get
or set the additional-data field on sasl-outcome
[ https://issues.apache.org/jira/browse/PROTON-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Ross reassigned PROTON-1518:
-----------------------------------
Assignee: Andrew Stitcher (was: Keith Wall)
> Proton provides no mechanism to get or set the additional-data field on sasl-outcome
> ------------------------------------------------------------------------------------
>
> Key: PROTON-1518
> URL: https://issues.apache.org/jira/browse/PROTON-1518
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
> Reporter: Keith Wall
> Assignee: Andrew Stitcher
> Labels: sasl
> Fix For: proton-c-0.21.0
>
>
> This JIRA refers to Proton(-C) only. Analogous work was already carried out for Proton-J under PROTON-1486.
> The Proton Engine API provides no mechanism for getting or setting the additional-data field on sasl-outcome.
> Some SASL mechanisms (e.g. SCRAM-SHA-\*) send additional data along with the outcome (in the case of SCRAM-SHA-\* the additional data is a proof that the server is also aware of the credentials and is not simply just accepting any credential data as part of some sort of attack).
> One approach for the API would be to expose the additional-data field using the send/recv/pending methods used for exchanging the challenge/response in the earlier phases of the sasl exchange.
--
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