My Kolab 2.4 experience on Centos 6

[Jeroen van Meeuwen]

On Wednesday, July 18, 2012 09:42:51 AM Troy Carpenter wrote:
> On Wednesday, July 18, 2012 10:17:00 AM you wrote:
> > Hi Troy,
> > 
> > On Tuesday, July 17, 2012 09:42:11 PM Troy Carpenter wrote:
> > > After wasting my time with installing Kolab 2.4 in a Centos container
> > > under
> > > Proxmox, I finally switched to installing under a full KVM version of
> > > Centos. The install went as expected when following the instructions,
> > > with
> > > the following additions:
> > > 
> > > 1. I had to manually create the localhost.pem file that was expected by
> > > postfix to initiate TLS connections.
> > 
> > I've created ticket #886 for this issue[1].
> 
> The commands, which I don't think was included in the online docs:
> 
> cd etc/pki/tls/certs
> make localhost.pem
> cp localhost.pem ../private
> 

Upcoming releases of pykolab, as a fix for ticket #886, will be calling 
/etc/pki/tls/certs/make-dummy-cert /etc/pki/tls/private/localhost.pem during 
the setup process.

> > For the sake of record keeping, I've created a ticket for this as well -
> > #887[2] - it is not an uncommon deployment scenario, after all.
> 
> In 2.3.4, setting a smarthost was done from the webadmin tool.  However,
> adding the part for sasl authentication was not:
> 
> 1. (...snip...)
> 2. (...snip...)
> 3. (...snip...)
> 

Thanks for the information, I'll add this to the documentation as soon as I 
have a chance.

> > Z-Push requires you to login with your uid attribute value (the default is
> > to use the surname of a user). I know this is somewhat confusing, as
> > Kolab 2.3 installations used the email address as the uid attribute
> > value.
> 
> That's too bad.

Yes, with our Z-Push replacement Syncroton, we seek to implement 
authentication along the lines of what we've defined in our documentation[1].

[1] http://docs.kolab.org/en-
US/Kolab_Groupware/2.4/html/Architecture_and_Design/chap-
Architecture_and_Design-Authentication_amp_Authorization.html#sect-
Architecture_and_Design-Authentication_amp_Authorization-
The_User_Supplied_Login

> My system is setup mainly for my family, so my uid is
> "carpenter", and every other user has the same with a number appended.
> Very annoying. I did figure out how to unlock the fields in the new user
> screen and I did see that uid can be modified that way, but I never figured
> out where the uid was being automatically generated.  I will experiment
> with some custom UIDs to see what happens.

As of today it's actually being generated using a hard-coded routine in the 
API (see /usr/share/kolab-webadmin/lib/api/kolab_api_service_form_value.php, 
private function generate_uid()).

We have an outstanding feature request to allow specifying how the uid should 
be generated - #677[2] - see the attachment[3] for a test implementation that 
you could execute from the command-line.

[2] https://bugzilla.kolabsys.com/show_bug.cgi?id=677
[3] https://bugzilla.kolabsys.com/attachment.cgi?id=143

Kind regards,

Jeroen van Meeuwen

-- 
Systems Architect, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/users/attachments/20120719/0d79959f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/users/attachments/20120719/0d79959f/attachment.sig>