Ok. I got past that error of the login.config file not being found.
Another issue that popped out is as below:
*WARN | Failed to add Connection ID:HP10007131-55187-1354108717336-1:1,
reason: java.lang.SecurityException: User name [system] or password is
invalid. No user for client
certificate: CN
Yes, you can define a system property
-Djava.security.auth.login.config= for where to pickup the
login.conf file.
On Wed, Nov 28, 2012 at 5:06 AM, joesan wrote:
> I have made some progress, but terribly stuck with the following error:
>
> WARN | Failed to add Connection ID:HP10007131-54558-
I have made some progress, but terribly stuck with the following error:
WARN | Failed to add Connection ID:HP10007131-54558-1354103802934-1:1,
reason: java.lang.SecurityException: User name [null] or password is
invalid. Unable to load user
properties file .\users.properties
It does not respect
I found the following information from Fuse source documentation.
http://fusesource.com/docs/broker/5.5/security/Auth-JAAS-CertAuthentPlugin.html
I export the certificate from the Broker's key store, view the contents and
get the Subject DN. I copy this Subject DN and use it in my users.propertie
The only difference is that with LDAP authorization your clients would
need to provide username/password, to identify themselves. With cert
plugin, the certificate is used for that (and mapped to the
appropriate user that can be later authorized).
Regards
--
Dejan Bosanac
--
R
When I still need the key store and trust store, why will I use this JAAS
plug in for authentication? I can very well use SSL Authentication in the
form of certificates stored in the trust store of the broker and my client.
I understand that I can plug in authorization rules, but for that I could
Hi,
this plugin doesn't have to do anything with ssl. It's a way to
authenticate your clients based on the certificate. After that you can
also authorize clients based on this information. So you need your
certificates in both cases. The plugin just adds you more flexibility
as you can do authoriz
xecuting the Java clas
> s. null: InvocationTargetException: Could not connect to broker URL:
> ssl://localhost:61617. Reason: java.net.SocketException: Software caused
> connection abort: socket wri
> te error -> [Help 1]*
>
>
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-SSL-Client-tp4659805.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ge in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-SSL-Client-tp4659805.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.