[
https://issues.apache.org/jira/browse/QPID-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-3283:
-----------------------------
Description:
This improvement forms part of the proposal I made to the Qpid Developer List
on 2011-05-16 in the posting entitled "Java Broker: Pluggable Authentication
Managers".
The existing AuthenticationManager and configuration classes will be refactored
to allow a user to choose an implementation of AuthenticationManager through
new elements in the config.xml.
Existing use-cases (that is authentication against the etc/passwd file) will be
maintained by plugging-in the PrincipalDatabaseAuthenticationManager
implementation. Future implementations of AuthenticationManager could then
allow authentication to be delegated to an external system such as an LDAP
Directory.
This change *will* alter the format of the config.xml file. Existing users of
<=0-12 will need to edit their config.xml when upgrading. Documentation will
be updated to guide upgraders and helpful error messages will gently reject
older configure files.
See also:
https://cwiki.apache.org/confluence/display/qpid/Java+Pluggable+Authentication+Managers
was:
This improvement forms part of the proposal I made to the Qpid Developer List
on 2011-05-16 in the posting entitled "Java Broker: Pluggable Authentication
Managers".
The existing AuthenticationManager and configuration classes will be refactored
to allow a user to choose an implementation of AuthenticationManager through
new elements in the config.xml.
Existing use-cases (that is authentication against the etc/passwd file) will be
maintained by plugging-in the PrincipalDatabaseAuthenticationManager
implementation. Future implementations of AuthenticationManager could then
allow authentication to be delegated to an external system such as an LDAP
Directory.
This change *will* alter the format of the config.xml file. Existing users of
<=0-10 will need to edit their config.xml when upgrading. Documentation will
be updated to guide upgraders and helpful error messages will gently reject
older configure files.
See also:
https://cwiki.apache.org/confluence/display/qpid/Java+Pluggable+Authentication+Managers
Affects Version/s: (was: 0.11)
Fix Version/s: 0.13
> Make AuthenticationManager pluggable
> ------------------------------------
>
> Key: QPID-3283
> URL: https://issues.apache.org/jira/browse/QPID-3283
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Assignee: Keith Wall
> Fix For: 0.13
>
>
> This improvement forms part of the proposal I made to the Qpid Developer List
> on 2011-05-16 in the posting entitled "Java Broker: Pluggable Authentication
> Managers".
> The existing AuthenticationManager and configuration classes will be
> refactored to allow a user to choose an implementation of
> AuthenticationManager through new elements in the config.xml.
> Existing use-cases (that is authentication against the etc/passwd file) will
> be maintained by plugging-in the PrincipalDatabaseAuthenticationManager
> implementation. Future implementations of AuthenticationManager could then
> allow authentication to be delegated to an external system such as an LDAP
> Directory.
> This change *will* alter the format of the config.xml file. Existing users
> of <=0-12 will need to edit their config.xml when upgrading. Documentation
> will be updated to guide upgraders and helpful error messages will gently
> reject older configure files.
> See also:
> https://cwiki.apache.org/confluence/display/qpid/Java+Pluggable+Authentication+Managers
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
