search for: securityprovider

...collective/mcollective.log -loglevel = info -daemonize = 1 +collectives = mcollective +libdir = /opt/puppet/libexec/mcollective/ +logfile = /var/log/pe-mcollective/mcollective.log +loglevel = info +daemonize = 1 +identity = testnix.home.lan # Plugins -securityprovider = psk -plugin.psk = unset +securityprovider = ssl +plugin.ssl_server_private = /etc/puppetlabs/mcollective/ssl/mcollective-private.pem +plugin.ssl_server_public = /etc/puppetlabs/mcollective/ssl/mcollective-public.pem +plugin.ssl_client_cert_dir = /etc/puppetlabs/mcollective/ssl/cl...

...a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details --> <import resource="jetty.xml"/> </beans> ---------- client.cfg main_collective = mcollective collectives = mcollective libdir = /usr/libexec/mcollective logger_type = console loglevel = debug # Plugins securityprovider = psk plugin.psk = mcopwd connector = activemq direct_addressing = 1 plugin.activemq.pool.size = 1 plugin.activemq.pool.1.host = puppet.test.italy.cloudlabcsi.local plugin.activemq.pool.1.port = 61613 plugin.activemq.pool.1.user = mcollective plugin.activemq.pool.1.password = mcopwd # Facts facts...

...ch pluggable interface would allow projects like openssh-lpk and SSSD to build pluggable providers for those crucial pieces of information. Is there any interest of pursuing such path together? I see it as creating an interface that can be enabled through a specific config value. For example "SecurityProvider". This option would have to be a path to a .so that should provide a defined agreed to interface. If the configuration option is not given the current rules are respected. If it is given then the openssh will call API functions to get keys, fingerprints or do host checks implemented by this .s...

Hi, I deployed MCollective to our Puppet clients. approx. ~ 200. Our platform requires the most secure setup possible, so PSK as securityprovider is not an option. Therefor I changed the security provider to aes_security reusing puppets certificates in the server.cfg as found in the docs (1) Our goal is to use mcollective to offload event-driven actions to agents running on designated nodes from a webapplication. e.g: send out a message to...

I am currently trying to get mcollective 2.2.4 up and running on RHEL 6 activeqm appears to be running and bound to the correct port, I see the server and client connections to the activemq box. However when I run mco ping all "seems to go well" except I get "No responses recieved" and above that I get the following log messages, debug 2013/05/29 17:02:12: activemq.rb:233:in

Hi, I have looked all over the place and can''t seem to find a complete answer to my query I am setting up MCollective to run alongside my puppet deployment and am having some problems getting it to play as I want it to Basically, I need to make sure that puppet NEVER makes any changes without them being triggered by someone (I honestly can''t see how anyone would ever want