[
https://issues.apache.org/jira/browse/QPID-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974962#comment-15974962
]
Alex Rudyy commented on QPID-7747:
----------------------------------
Hi Tomas,
In order to allow PLAIN authentication over insecure transport, you need to set
attribute "secureOnlyMechanisms" value to "[]" for Authentication provider.
Something like in the code below:
{code}
Map<String, Object> authenticationProviderAttributes = new HashMap<>();
authenticationProviderAttributes.put(AuthenticationProvider.TYPE, "Plain");
authenticationProviderAttributes.put(AuthenticationProvider.NAME,
"authProvider");
authenticationProviderAttributes.put("secureOnlyMechanisms", "[]");
broker.createChild(AuthenticationProvider.class,
authenticationProviderAttributes);
{code}
Alternately, you can add "secureOnlyMechanisms" into initial configuration file.
> Logging: Depend only on slf4j and remove logback dependencies
> -------------------------------------------------------------
>
> Key: QPID-7747
> URL: https://issues.apache.org/jira/browse/QPID-7747
> Project: Qpid
> Issue Type: Improvement
> Reporter: Tomas Klimavicius
> Attachments: embedded-broker-example.tar.gz
>
>
> Qpid is depending on logback as it's log implementation, but this makes it
> horrible to use inside projects that already use log4j or slf4j-jdk14.
> It would be much easier for users if the source code would only depened on
> slf4j. Now if we exclude logback and expect qpid to use our provided logger
> the code does not compile since qpid actually depends on logback -
> ch.qos.logback.classic.Logger logger =
> (ch.qos.logback.classic.Logger)LoggerFactory.getLogger("ROOT");
> And if you use something else you get a class cast exception.
> Also slf4j complains on every startup when you have multiple implementations
> in your classpath
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
