[PROTON-1486] no mechanism to get or set the additional-data field on sasl-outcome

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-j-0.19.0
• Fix Version/s: proton-j-0.20.0
• Component/s: proton-j
• Assignee: Keith Wall
• Reporter: Robert Godfrey
• Created: 18/May/17 13:04
• Updated: 02/Oct/19 19:21
• Resolved: 18/Jul/17 11:36

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.

Issue Links

• is cloned by: PROTON-1518 [proton-c] Proton provides no mechanism to get or set the additional-data field on sasl-outcome
• is required by: QPIDJMS-294 The SCRAM-SHA-* SASL mechanisms should verify the server final message if it is sent in the additional-data field of sasl-outcome
• links to: GitHub Pull Request #9