activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trevor Pounds (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-358) JNDI / LDAP discovery mechanism
Date Thu, 11 Oct 2007 21:42:23 GMT

     [ https://issues.apache.org/activemq/browse/AMQ-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Trevor Pounds updated AMQ-358:
------------------------------

    Attachment: LdapNetworkConnector.java.svn.diff

Contributing patch. This patch was tested with ActiveMQ trunk, ApacheDS 1.0.2.

ActiveMQ LDAP network connector can be configured via XBean. In order for an LDAP entry to
be valid to work with this connector the entry must implement the ipHost and ipService objectClasses
as defined in RFC2307.  This is easily configurable when using ApacheDS with Apache Directory
Studio.  Though this is beyond the scope of describing this patch.

Example 1:
connects to the ldapserver with the provided credentials. And will search one level deep from
the base and below and connect to all entries below that match the given filter. In this case
entries that have cn=cluster0* as an attribute. Where * matches any number of characters.

<networkConnectors>
      <ldapNetworkConnector uri="ldap://myldapserver:10389"
                            base="ou=servers,ou=activemq,o=apache"
                            user="uid=admin,ou=system"
                            password="secret"
                            searchFilter="(cn=cluster0*)"
                            searchScope="ONELEVEL_SCOPE"
                            />
</networkConnectors>

Example 2:
connects to the ldapserver with the provided credentials. And will search the entire subtree
from the base and below and connect to all entries below that match the given filter. In this
case entries that have cn=server* as an attribute. Where * matches any number of characters.

<networkConnectors>
      <ldapNetworkConnector uri="ldap://myldapserver:10389"
                            base="ou=servers,ou=activemq,o=apache"
                            user="uid=admin,ou=system"
                            password="secret"
                            searchFilter="(cn=server*)"
                            searchScope="SUBTREE_SCOPE"
                            />
</networkConnectors>

To get a better understanding of what filters are allowed in LDAP please see RFC2254. For
more information on the usage of the searchScope attribute please refer to the javax.naming.directory.SearchControls
object that was introduced in Java v 1.3.  Upon acceptance of the patch I will gladly update
the ActiveMQ documentation to cover more advanced usage of the ldapNetworkConnector configuration,
though it should be fairly simple to use by anyone that has limited experience with LDAP and
JNDI.

> JNDI / LDAP discovery mechanism
> -------------------------------
>
>                 Key: AMQ-358
>                 URL: https://issues.apache.org/activemq/browse/AMQ-358
>             Project: ActiveMQ
>          Issue Type: New Feature
>            Reporter: James Strachan
>             Fix For: 5.2.0
>
>         Attachments: LdapNetworkConnector.java.svn.diff
>
>
> It'd be nice to use a clustered JNDI or LDAP server to perform discovery of networks,
clusters etc

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


Mime
View raw message