[
https://issues.apache.org/jira/browse/QPID-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael j. goulish updated QPID-2949:
-------------------------------------
Fix Version/s: (was: 0.8)
0.9
I was probably wrong to assign blocker status to this. I believe it
really is just an irritant, since even in the auth=no case I can still
successfully use qpid-route to create a route between two brokers, while
ignoring the spurious prompt.
I'm going to change this to 0.9 to get it out of the way of the release,
and then just fix this on trunk.
> broker prompts console interactively for password when --auth=no
> ----------------------------------------------------------------
>
> Key: QPID-2949
> URL: https://issues.apache.org/jira/browse/QPID-2949
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.8
> Reporter: michael j. goulish
> Assignee: michael j. goulish
> Priority: Minor
> Fix For: 0.9
>
> Attachments: dont_prompt_me.diff
>
>
> As a result of checkin svn r1024541, which promoted some client-side Sasl
> code to the common library for use in broker, the broker now prompts for a
> password when when it is run with --auth=no !
> The attached patch removes this behavior by propagating knowledge of
> "--auth=no" down to SaslFactory. If authorization has been turned off, the
> Saslfactory will create a null sasl object, just like it does if the code is
> compiled with no Sasl support.
> TODO -- also must fix the pathway where auth==yes.
> NOTE: this is apparently an irritant rather than a disaster, since it did not
> affect make check after the original checkin ( r102451 ).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
