Kolab POSIX Users/Groups default uidNumber/gidNumber
Eric Renfro
psi-jack at linux-help.org
Wed Oct 28 01:07:12 CET 2015
Thank you Jan!
That's exactly what I needed. Changed things up, and even split up my configuration
for websites into vhosts per this example useful github puppet concept:
https://github.com/kolab-groupware/puppet-module-kolab/tree/development/templates/webserver/sites
Now I'm just about ready to finally move the rest of my migrations over.
Eric Renfro
On Monday, October 26, 2015 08:41:21 PM Jan Kowalsky wrote:
> Hi Eric,
>
> look here:
>
> https://git.kolab.org/diffusion/WAP/browse/master/lib/api/kolab_api_service_
> form_value.php;8eff748533a7b47d1d8156bbb3212647ca0f5d1f$885
>
> $highest_uidnumber = $conf->get('uidnumber_lower_barrier');
> if (!$highest_uidnumber) {
> $highest_uidnumber = 999;
> }
>
>
> similar for gid-numbers.
>
> So, if there is neither an existing posix user entry in your ldap the
> 1000 nor configuration value in kolab.conf 1000 is choosen.
>
> so just add
>
> uidnumber_lower_barrier = YOUR_NUMBER
> gidnumber_lower_barrier = YOUR_NUMBER
>
>
> to kolab.conf
>
> this should do it ...
>
> Best Regards
> Jan
>
> Am 23.10.2015 um 18:33 schrieb Eric Renfro:
> > Right now Kolab 3.4 seems to default generation of default uidNumber and
> > gidNumber at 1,000, which is generally considerable as bad practice with
> > LDAP stored user information, dis-allowing, or more so conflicting local
> > users vs LDAP users.
> >
> > How do you change the generation to start at a higher number, for example
> > 2000?
> >
> > I've found an alternative way to get around this by setting the attributes
> > of them to use generated, but not read-only values so I can manually put
> > the numbers in, but this is... Not very wise to keep up. ;)
> >
> > Eric Renfro
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20151027/f5312814/attachment-0001.html>
More information about the users
mailing list