[
https://issues.apache.org/jira/browse/PROTON-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey updated PROTON-1486:
--------------------------------
Description:
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.
was:
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.
> Proton(-J) provides no mechanism to get or set the additional-data field on
> sasl-outcome
> ----------------------------------------------------------------------------------------
>
> Key: PROTON-1486
> URL: https://issues.apache.org/jira/browse/PROTON-1486
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Reporter: Rob Godfrey
>
> 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.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
