[
https://issues.apache.org/jira/browse/QPID-6838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Scholz updated QPID-6838:
-------------------------------
Attachment: QPID-6838.patch
Simple patch for Windows SASL implementation to allow SASL EXTERNAL without
USERNAME.
> Qpid Messaging C++ client with SASL EXTERNAL on Windows should not require
> username
> -----------------------------------------------------------------------------------
>
> Key: QPID-6838
> URL: https://issues.apache.org/jira/browse/QPID-6838
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Affects Versions: qpid-cpp-0.34
> Reporter: Jakub Scholz
> Attachments: QPID-6838.patch
>
>
> Since the QPID-6511 was fixed, the Windows C++ client requires username to be
> specified in connection options when the SASL EXTERNAL mechanism is used.
> I don't think this is required. The previous versions of the client on
> Windows didn't needed the username (and they work fine) and the Linux
> versions also don't need it. Can this be reverted back to the original
> solution, so that one can use SASL EXTERNAL without specifying username?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
