The Service Bus for the Connected Business
We are evaluating the security model of Neuron ver 3.5. I protected a publisher by choosing a access control list under "Windows Integrated" , in the Security tab page of the publisher.
After doing this, an existing client connector that is mapped to this publisher, failed to start up, and I could see from the log as follows:
Exception : Party xxx is not authorized to connect
Let me explain our requirement a bit more: we plan to publish messages via client connector. As such , we need to prevent people from connecting to the ESB as the publisher from any host. People can only send message via the client connector.
Tags: client, connector, publisher, security
Views: 199
Jack - in your access control list that you created, did you add the service account that the Neuron ESB Service is running under? That's the user context the client connector will be running under, so it needs to be included in the ACL.
Joe
Hi Joe
We happened to have chosen the default option during installation of Neuron ESB service, of setting the service account as the built-in local system account NT AUTHORITY\SYSTEM.
However, I found that ACL does not support such built-in account.
the easiest is to create a local user, place that user in the local administrators group...
you can lock down even further with a general user if you want...the directions for that are in the readme.html file that ships with the install
Neuron ESB Product Support Forums and Communities
© 2024 Created by Neuron Admin.
Powered by
