[
https://issues.apache.org/jira/browse/QPID-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283959#comment-13283959
]
Keith Wall commented on QPID-3997:
----------------------------------
Hi Rob, I committed under this Jira to resolve the JDK 1.7 test failure that
had been occurring for the last few days. On the error path (multiple auth
managers, but no default), it needed to close() the auth managers, in order to
remove any installed SASL mechanisms.
I also notice that the ApplicationRegistry#close() method should probably be
closing all the auth managers, and not just the default. I suggest this could
cause test failures too in some scenarios. I have not made this change.
regards, Keith
> [Java Broker] Allow assignment of AuthenticationManager on a per-port basis
> ---------------------------------------------------------------------------
>
> Key: QPID-3997
> URL: https://issues.apache.org/jira/browse/QPID-3997
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Rob Godfrey
> Assignee: Rob Godfrey
>
> Currently we only allow for a single AuthenticationManager across all ports.
> We should allow for separate ports to allow for different authentication
> schemes. Ideally we should also allow for different vhosts to be bound to
> different ports and for different SASL mechanisms to be bound to different
> authentication managers, but these steps should be covered by later JIRAs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
