You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Trevor Pounds (JIRA)" <ji...@apache.org> on 2008/02/20 04:37:15 UTC
[jira] Created: (AMQ-1587) Improvements/Bug Fixes for LDAP
Discovery Mechanism (LDAP Network Connector)
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
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.
[jira] Updated: (AMQ-1587) Improvements/Bug Fixes for LDAP
Discovery Mechanism (LDAP Network Connector)
Posted by "Trevor Pounds (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Trevor Pounds updated AMQ-1587:
-------------------------------
Attachment: LdapNetworkConnector.diff
Attaching Licensed Patch.
> 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.
[jira] Resolved: (AMQ-1587) Improvements/Bug Fixes for LDAP
Discovery Mechanism (LDAP Network Connector)
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino resolved AMQ-1587.
--------------------------------
Resolution: Fixed
> 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
> Assignee: Hiram Chirino
> 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.
[jira] Commented: (AMQ-1587) Improvements/Bug Fixes for LDAP
Discovery Mechanism (LDAP Network Connector)
Posted by "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.
[jira] Assigned: (AMQ-1587) Improvements/Bug Fixes for LDAP
Discovery Mechanism (LDAP Network Connector)
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Strachan reassigned AMQ-1587:
-----------------------------------
Assignee: Hiram Chirino
This looks great stuff with awesome documentation - fancy applying it? :)
> 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
> Assignee: Hiram Chirino
> 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.
[jira] Commented: (AMQ-1587) Improvements/Bug Fixes for LDAP
Discovery Mechanism (LDAP Network Connector)
Posted by "Trevor Pounds (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41707#action_41707 ]
Trevor Pounds commented on AMQ-1587:
------------------------------------
Any updates on this patch?
I'm also still having problems updating/overwriting the images on the confluence page documenting this feature.
> 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
> Assignee: Hiram Chirino
> 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.
[jira] Commented: (AMQ-1587) Improvements/Bug Fixes for LDAP
Discovery Mechanism (LDAP Network Connector)
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42034#action_42034 ]
Hiram Chirino commented on AMQ-1587:
------------------------------------
patch applied in rev 645580. Thx!
Not sure what the problem is with confluence.. could you rename and upload the images? Perhaps that would be the simple work around?
> 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
> Assignee: Hiram Chirino
> 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.
[jira] Issue Comment Edited: (AMQ-1587) Improvements/Bug Fixes for
LDAP Discovery Mechanism (LDAP Network Connector)
Posted by "Trevor Pounds (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42036#action_42036 ]
tpounds edited comment on AMQ-1587 at 4/7/08 9:16 AM:
------------------------------------------------------------
I think I can upload them with a different name and that will work as a simple workaround. It just seems strange that I can't overwrite the previous images properly.
Edit: I just tried modifying the confluence page and cannot seem to do so anymore. Any ideas?
was (Author: tpounds):
I think I can upload them with a different name and that will work as a simple workaround. It just seems strange that I can't overwrite the previous images properly.
> 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
> Assignee: Hiram Chirino
> 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.
[jira] Commented: (AMQ-1587) Improvements/Bug Fixes for LDAP
Discovery Mechanism (LDAP Network Connector)
Posted by "Trevor Pounds (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42036#action_42036 ]
Trevor Pounds commented on AMQ-1587:
------------------------------------
I think I can upload them with a different name and that will work as a simple workaround. It just seems strange that I can't overwrite the previous images properly.
> 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
> Assignee: Hiram Chirino
> 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.
[jira] Commented: (AMQ-1587) Improvements/Bug Fixes for LDAP
Discovery Mechanism (LDAP Network Connector)
Posted by "Trevor Pounds (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41455#action_41455 ]
Trevor Pounds commented on AMQ-1587:
------------------------------------
Please apply at your leisure.
BTW, I'm trying to update (i.e. resize) the images on the Confluence related to this patch. I am unable to delete overwrite my previous uploaded images. Do I need better karma for this? :) I posted a thread about this below.
see: http://www.nabble.com/Confluence-Image-Removal-Replacement-td15701101s2354.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
> Assignee: Hiram Chirino
> 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.