Uploaded image for project: 'Qpid Proton'
  1. Qpid Proton
  2. PROTON-970

SASL options for setting path and name should not be transport-specific

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • None
    • None
    • proton-c

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              tross Ted Ross
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: