You are viewing a plain text version of this content. The canonical link for it is here.

Posted to proton@qpid.apache.org by "Ted Ross (JIRA)" <ji...@apache.org> on 2015/07/30 20:38:04 UTC

[jira] [Created] (PROTON-970) SASL options for setting path and name should not be transport-specific

Ted Ross created PROTON-970:
-------------------------------

             Summary: SASL options for setting path and name should not be transport-specific
                 Key: PROTON-970
                 URL: https://issues.apache.org/jira/browse/PROTON-970
             Project: Qpid Proton
          Issue Type: Bug
          Components: proton-c
            Reporter: Ted Ross


Both pn_sasl_config_name and pn_sasl_config_path take a pn_sasl_t object as an argument, suggesting that different transports may use different configurations.
Cyrus SASL treats both the path and (server) name as per-process settings.
The above methods in pn_sasl should reflect this scope and not use a pn_sasl_t as an argument.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)