IMHO sounds like a job for pam_mkhomedir
(https://linux.die.net/man/8/pam_mkhomedir) and not for puppet.
- Thomas
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
Thanks for the idea.
I will tinker and report back.
"Sometimes I think the surest sign that intelligent life exists elsewhere in
the universe is that none of it has tried to contact us."
Bill Waterson (Calvin & Hobbes)
> On Feb 6, 2017, at 9:58 AM, Christopher Wood
> wrote:
>
> The defined
The defined function is more about whether something is defined in the catalog,
if I recall correctly.
https://docs.puppet.com/puppet/latest/function.html#defined
This sounds like something for a custom fact which returns a list of users
found on the system. You may have to do an ldapsearch fro
I am trying to figure out if I can do any user management from Puppet for users
initially managed by Red Hat's Identity Manager (freeipa / ldap)
Here is a code snippet I tried:
# Class: wtf
#
class wtf {
if defined( User["dewhite"] ) {
$foo = User["dewhite"]["home"]
notify { "->${foo}
On 22/08/14 02:45, Garrett Honeycutt wrote:
Here[1] is the code that I use to manage local users. You could use it
for your scenario by placing users in different levels in Hiera and
keying off the profile.
Thanks, I'll give that idea a try and see if it works out any better for
this setup.
On 8/20/14 11:45 PM, Gregory Orange wrote:
> How do people manage users? I'm slowly marching toward LDAP (someone
> recently suggested FreeIPA, not sure if it's relevant), but trying to
> stave it off for the time being. I've read a few blogs and posts on the
> topic, but nothing clear comes out -
How do people manage users? I'm slowly marching toward LDAP (someone
recently suggested FreeIPA, not sure if it's relevant), but trying to
stave it off for the time being. I've read a few blogs and posts on the
topic, but nothing clear comes out - except that if one gets too
complicated, one sh
> The data in LDAP is really more like database data, not so much as system
information
I guess the question really evolves around this: despite the system
configuration being stored in a datastore that provides infinitely amount
of flexibility, do you continue to consider your system configuratio
Puppet is really meant for managing systems, not data. The data in LDAP is
really more like database data, not so much as system information, even
though many system services use it to get information.
Consider if you would use Puppet to manage data (like web site content) in
a MySQL database. Y
Hi,
I'm faced with the question if we should be doing user management directly
using freeipa (an integrated LDAP, Kerberos, CA, etc) or by manipulating
freeipa using Puppet.
Installation and configuration of the service is already performed through
Puppet so this only concerns the data stored
Hi Johan,
thank you for the hint with virtual resources.
Here is my solution
cat init.pp
class accounts {
@accounts::virtual {'test1':
comment => "test1",
uid => "1056",
gid => "880",
group => "baader",
shell => "/bin/bash",
password => '$1$6hsRON8i7w5JncJ
Have a look at virtual resources. When needed, you can realize them.
The puppet cookbook has a chapter explaining this
On 10/08/2013 01:15 PM, Andreas Dvorak wrote:
Dear all
I am looking for a solution for a module to define alle possible user
and then install the one or more user from that m
Dear all
I am looking for a solution for a module to define alle possible user and
then install the one or more user from that module if needed on a server,
but not all of them.
My idea is something like this. Can I define a user in the nodes.pp at a
special Server to install that user?
init.p
On 14 Dec 2011, at 07:10, Marek Dohojda wrote:
> I am wondering what would be a good way of managing users. I need to add
> user to some host and ensure that they are absent on another box. so for
> instance, I want Bob to be present on server A but absent on server B. as
> far as I know, y
I am wondering what would be a good way of managing users. I need to add user
to some host and ensure that they are absent on another box. so for instance,
I want Bob to be present on server A but absent on server B. as far as I know,
you can only have one defined object. so I could have Bob
Hey
I'm having a problem getting my user management module to work. I can
create users and groups without any problems, but if I need to
override group memberships on a single node, I get the "Error 400 on
SERVER: Only subclasses can override parameters"
This is what I have setup:
usermgmt modul
Hi people.
After some reading, I think I have some sort of coherent thought about how to
handle users and groups, being a first time Puppet user though I figured I'd
ask for some criticism before I go ahead.
I'll use the /modules/user module as per the BP-doc, and store all the users
and groups
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry for the double post...been out of it today.
Personally, I wouldn't bother with a CSV, I'd just use a flat file with
two columns since it's a single map.
If you're going to get complicated, you'll probably want to use a local
MySQL database or t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sukh,
To do this, I would recommend a cron job that populates a file on the
Puppet server readable by the puppet user.
I would then have a server function that uses the user name or uid to
collect the appropriate value from the file.
The main issue
We're using local passwd/shadow files on all our linux hosts for
authentication and manage them by defining virtual resources like the
following and realizing them in the appropriate classes based on
authorization requirements.
@user {
"username":
comment => "User Name"
20 matches
Mail list logo
