Seems like the credentials you're using in login.config are not
matching your Ldap server.
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action:
Hi Dejan,
Thanks for the input.
This is what I did
I uninstalled the OpenDS 2.2.1 because I cant easily re-import the
LDIF if an existing OpenDS already has a root DN.
I re-installed the OpenDS and had it import from the LDIF on the
http://activemq.apache.org/security.html, and I also changed
I havent tried that yet.
But I think I am getting closer.
I took a vanilla activemq 5.6.0 bundle zip and expanded it on a
windows7 machine, and added only this section for the LDAP.
The OpenDS 2.2.1 is also running on the same machine.
Now, when I made my non-ssl producer connect to the
And then on the broker side, here is the log that I snipped out --
I turned up the logging level in the logging.properties to DEBUG from
INFO level.
I see the userName that I passed from my camel producer bean when I
instantiate the ActiveMQConnectionFactory.
I re-read the
Still not resolved but I left out an important piece:
In the activemq.xml, I forgot to put in:
plugins
jaasAuthenticationPlugin configuration=LdapConfiguration /
authorizationPlugin
etc...
And I forgot to put the login.config into the conf directory.
Here is
Hi
Have you tried with the ActiveMQ 5.7.0 release?
On Wed, Oct 17, 2012 at 2:09 AM, Sean K sk92...@gmail.com wrote:
Hi,
I am working with the documentation on the activemq site for
configuring the LDAP.
http://activemq.apache.org/security.html -- almost everything is
copied verbatim
Hi,
I am working with the documentation on the activemq site for
configuring the LDAP.
http://activemq.apache.org/security.html -- almost everything is
copied verbatim except for hostnames and there were a few parameters
that were not writable by the current bean so I remove them -- for
example
