[OASIS Issue Tracker] (AMQP-104) SASL Outcome: differentiating application-data based on code

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

Brian Raymor created AMQP-104:
---------------------------------

             Summary: SASL Outcome: differentiating application-data based on code
                 Key: AMQP-104
                 URL: https://issues.oasis-open.org/browse/AMQP-104
             Project: OASIS Advanced Message Queuing Protocol (AMQP) TC
          Issue Type: Improvement
          Components: Claims Based Security
    Affects Versions: cbs-WD03
            Reporter: Brian Raymor
            Assignee: Brian Raymor
             Fix For: cbs-WD04


The current text:

If the exchange was unsuccessful, the additional-data field in the sasl-outcome frame body contains a list of error message strings for token names which caused the authentication to fail. 

//

What about more general failures such as 5 tokens were promised but 4 were transferred?

Do we want to differentiate the contents of additional-data based on the value of the code field?

0 Connection authentication succeeded.
1 Connection authentication failed due to an unspecified problem with the supplied credentials.
2 Connection authentication failed due to a system error.
3 Connection authentication failed due to a system error that is unlikely to be corrected without intervention.
4 Connection authentication failed due to a transient system error.




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