This patch was posted in JIRA QPID-2949.

    It provides a way to tell SaslFactory that console
    interaction is NOT ok. i.e. if the code is running
    as part of a broker, or a demonized client of some
    kind. Just tell it to never do interaction, and any
    patch attempt to interact will be treated as an error.



    This script demonstrates that all goes well if you supply enough info :

            rm -rf /tmp/data_1 /tmp/data_2
            mkdir /tmp/data_1 /tmp/data_2

            # in window 1:
            ../qpidd -p 5672 --data-dir /tmp/data_1 --auth=yes --mgmt-enable=yes \
                     --log-enable info+ ./qpidd_1.log --log-source yes           \
                     --sasl-config=/home/mick/trunk/qpid/cpp/src/tests/sasl_config

            # in window 2:
            ../qpidd -p 10000 --data-dir /tmp/data_2 --auth=yes --mgmt-enable=yes \
                     --log-enable info+ ./qpidd_1.log --log-source yes            \
                     --sasl-config=/home/mick/trunk/qpid/cpp/src/tests/sasl_config

            # in window 3 ( from qpid dir )
            ./tools/src/py/qpid-route dynamic add zig/zig@localhost zig/zig@localhost:10000 qmf.default.direct

            # and now view the created route
            ./tools/src/py/qpid-route route list localhost:5672

    If you say auth=no, that works fine also.

    HOWEVER PLEASE NOTE --

    if you say auth=yes, but then do not supply enough into to avoid the need for interaction,
    the attempted interaction will result in the connection being closed. Then the originating broker
    will re-try the connection, and you will get a two-broker infinite loop until you fix it.



git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@1040689 13f79535-47bb-0310-9956-ffa450edef68

0 files changed, 0 insertions, 0 deletions