[ 
https://issues.apache.org/jira/browse/QPID-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934455#action_12934455
 ] 

Ted Ross commented on QPID-2949:
--------------------------------

>>TODO -- also must fix the pathway where auth==yes.

This is important since the problem isn't the state of the --auth configuration 
but the fact that a server process is prompting for interactive input.

>>NOTE: this is apparently an irritant rather than a disaster, since it did not 
>>affect make check
>>after the original checkin ( r102451 ).

I disagree with this statement.  All this means is that make-check has 
insufficient coverage.  If a server process is hanging while waiting for 
interactive input, I'd say that's closer to disaster than irritant.


> 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_noauth.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

Reply via email to