You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2010/11/18 16:37:15 UTC
[jira] Commented: (QPID-2949) broker prompts console interactively
for password when --auth=no
[ https://issues.apache.org/jira/browse/QPID-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933454#action_12933454 ]
Robbie Gemmell commented on QPID-2949:
--------------------------------------
Hi Michael,
I see that you have tagged this issue Fix For 0.8 originally, but later updated your comment to suggest the issue is only an irritant. Do you still think this needs to be fixed for 0.8, and if so do you intend to do so?
I think it could be concerning enough for users to see the broker requesting passwords that it would be good to fix it for 0.8 if the change is reasonable, especially if as your comments now suggest its also an issue when auth=yes....but the JIRAs current Minor status is almost as far from Blocker as it gets. Let me know what you think as there wont be much point producing another RC until this goes in, if it going to.
Robbie
> 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.8
>
> 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-subscribe@qpid.apache.org