Ken Barber wrote:
Its just using the Ruby Etc library to do the lookup according to
puppet/util/posix.rb. Which won't match NIS accounts. So I'd raise a
feature request if you want this support.
its #8081
You can work around this by using something like:
$username = "bob"
ssh_authorized_key
Its just using the Ruby Etc library to do the lookup according to
puppet/util/posix.rb. Which won't match NIS accounts. So I'd raise a
feature request if you want this support.
You can work around this by using something like:
$username = "bob"
ssh_authorized_key { "keyfor-${username}":
key =>
I'm wondering if the User provider has the capability to look up accounts
via NIS. It's been a long time since I've used NIS, however, so I don't know
if this is the problem for sure.
--
Nathan Clemons
http://www.livemocha.com
The worlds largest online language learning community
On Fri, Jun 24
I'm wondering if my description was not clear enough or nobody knows an answer
to this. Did I stumble across a bug here and should open a ticket?
regards, Andreas
Andreas Kuntzagk wrote:
Hi,
I have this resource definition:
ssh_authorized_key { "nagios@login2":
key => [REDACTED]
use
Hi,
I have this resource definition:
ssh_authorized_key { "nagios@login2":
key => [REDACTED]
user=> "nagios",
type=> "ssh-dss",
require => Service['nis'],
}
This nagios user comes from NIS, yp.conf and nsswitch.conf are handled by puppet
and configured before the key. I
