sounds a good idea! - I'll look into it
cheers,
Rob
http://rajdavies.blogspot.com/
On Oct 12, 2007, at 7:56 AM, tpounds wrote:
Like I was saying earlier when I submitted the patch, I will gladly
put some
documentation up on the site pertaining to this new feature...but I
was
wondering where teh best place to put it would be...currently it
seems like
the ActiveMQ page has documentation that is jumbled up for various
versions
of ActiveMQ...I've noticed in a few places where 5.X features are
mixed with
various other versions...This patch is definitely a feature for the
5.X
series of ActiveMQ, but shuold we look into segregating some of the
documentation better by major/minor revisions of the software...I
proposed
the same solution in the ServiceMix forums when Guillaume was
asking about
the 4.0 documentation.
see: http://www.nabble.com/ServiceMix-4.0-documentation-
tf4573543s12049.html
-Trevor
rajdavies wrote:
thanks Trevor! - patch applied
cheers,
Rob
http://rajdavies.blogspot.com/
On Oct 11, 2007, at 10:55 PM, tpounds wrote:
I've submitted a path for JIRA ticket AMQ-358 that provides dynamic
network
configuration using LDAP. I will update the main ActiveMQ
configuration
documentation to include this network connector once the patch has
been
merged into the trunk. The patch is implemented such that almost any
directory server structure and layout can be used so long as the
following
conditions are met: 1) the directory server provides an LDAP
protocol
binding, 2) the directory server supports the ipHost and ipService
objectClasses as defined in RFC2307, 3) and the servers you wish to
list in
the directory server implement both the ipHost and ipService
objectClasses.
If all 3 of these conditions are met then LDAP network connector
should be
able to successfully connect to the listed server so long as it is
found
within the bounds of the user specified search filter.
see: https://issues.apache.org/activemq/browse/AMQ-358
The patch adds a new network connector element that provides
dynamic lookup
throuhg an LDAP server. Below is an example configuration.
<networkConnectors>
<ldapNetworkConnector uri="ldap://163.181.70.133:10389";
base="ou=servers,ou=activemq,o=apache"
user="uid=admin,ou=system"
password="secret"
searchFilter="(cn=myuniquename*)"
searchScope="ONELEVEL_SCOPE"
/>
</networkConnectors>
see below for more references on the implementation.
LDAP ApacheDS & Directory Studio: http://directory.apache.org/
LDAP Search Filters: http://www.rfc-editor.org/rfc/rfc2254.txt
NIS objectClass definitions: http://www.rfc-editor.org/rfc/
rfc2307.txt
JNDI Search Scope:
http://java.sun.com/j2se/1.5.0/docs/api/javax/naming/directory/
SearchControls.html
-Trevor
--
View this message in context: http://www.nabble.com/-Patch--Added-
Dynamic-Network-Configuration-using-LDAP--AMQ-358--
tf4610211s2354.html#a13165559
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
--
View this message in context: http://www.nabble.com/-Patch--Added-
Dynamic-Network-Configuration-using-LDAP--AMQ-358--
tf4610211s2354.html#a13170141
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
