[jira] Commented: (AMQ-1587) Improvements/Bug Fixes for LDAP Discovery Mechanism (LDAP Network Connector)

["Trevor Pounds (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/AMQ-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41343#action_41343 ] 

Trevor Pounds commented on AMQ-1587:
------------------------------------

I've started documenting the usage at [LDAP Broker Discovery Mechanism|http://activemq.apache.org/ldap-broker-discovery-mechanism.html]

> Improvements/Bug Fixes for LDAP Discovery Mechanism (LDAP Network Connector)
> ----------------------------------------------------------------------------
>
>                 Key: AMQ-1587
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1587
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Connector
>    Affects Versions: 5.0.0
>            Reporter: Trevor Pounds
>             Fix For: 5.1.0
>
>         Attachments: LdapNetworkConnector.diff
>
>
> These are much needed improvements and bug fixes for the AMQ-358.  The original patch worked for only a subset of cases.  I have updated the original network connector I submitted with the following features and fixes.
> - detection and handling of multiple LDAP entries pointing to the same upstream broker
> - anonymous binding support (not everyone wants to put their login credentials in an XML file!)
> - LDAP server failover support
> - general logging improvements
> - fix bug that only allowed a single discovered network connector from a broker
> - persistent search capabilities allowing a broker to stay in sync with the LDAP server entries (only works for LDAP servers who support the extensions defined in [draft-ietf-ldapext-psearch-03.txt|http://www.ietf.org/proceedings/01aug/I-D/draft-ietf-ldapext-psearch-03.txt])

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.