[
https://issues.apache.org/jira/browse/QPID-3997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288048#comment-13288048
]
Keith Wall commented on QPID-3997:
----------------------------------
Hi Rob,
I committed under this Jira to resolve the JDK 1.7. I also moved some of the
responsibilities of ApplicationRegistry to a different class:
AuthenticationManagerRegistry. Would you review please?
> [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]
