Fwd: Re: [clapf-users] webui + ldap user auth backend
sorry, the original went to your personal address... Original Message Subject: Re: [clapf-users] webui + ldap user auth backend Date: Tue, 21 Sep 2010 10:21:59 +0200 From: pete p...@teamlupus.hu To: Janos SUTO s...@acts.hu I think it would be better to ship the original qmail.schema file, and create a clapf specific schema which adds like objectClass: clapfUser i agree, this would make things more clear Note 2: the password field is the crypt()'ed password of the given Actually the webui uses MD5 for passwords. To verify it, I recommend you to change a password in the webui for user xy, then try to access his other services with the new password. It should work. I recompiled clapf, did a new install, purged both mysql databases (token, history), imported the sql initializator scripts, did a training, copied clapf init.d script to /etc/init.d/, copied config to the new installation. I also copied the webui from the sources to the place from where the webserver can serve it, re-did setup from zero. I manually created the clapfadmin user, by creating a new object from scratch, adding the necessary objectclasses and attributes as the example ldif file said. Now it is working... Mystery (or i was a bit tired). Thanks for the support on this. Clapf does not have currently write access to the directory. I plan to use the webui for the sole purpose for letting users traint their own part of the token database. Apart from this, everybody will have the very same setting for mail filtering (no policy groups, no admins etc.). I do not plan to use the passwd change function (it is handled elsewhere, with logging, enforcing password policies and notifying admins and the account owner about this event), and if it become possible in the future then i will disable these fields in the ui. -- Péter XMPP, MSN: peter.laszlo.sz...@gmail.com
Re: Fwd: Re: [clapf-users] webui + ldap user auth backend
On Tue, 21 Sep 2010 10:23:00 +0200, pete p...@teamlupus.hu wrote:
sorry, the original went to your personal address...
No problem.
Original Message
I think it would be better to ship the original qmail.schema file,
and create a clapf specific schema which adds like
objectClass: clapfUser
i agree, this would make things more clear
I have mad this change, and created a new ldap schema file
(ldap/clapf-user.schema) which can be added to slapd.conf.
I will release a nigthly build soon which includes this new
schema, and the reverted qmail.schema file as well.
Now it is working... Mystery (or i was a bit tired). Thanks for the
support on this.
Glad to hear this.
Clapf does not have currently write access to the directory. I plan to
use
the webui for the sole purpose for letting users traint their own part
of
Ok, however the webui creates an sqlite3 file in the users queue directory
for faster quarantine access.
the token database. Apart from this, everybody will have the very same
setting for mail filtering (no policy groups, no admins etc.). I do not
plan to use the passwd change function (it is handled elsewhere, with
logging, enforcing password policies and notifying admins and the
account
owner about this event), and if it become possible in the future then i
will disable these fields in the ui.
You can set define('PASSWORD_CHANGE_ENABLED', 0); in your config.php, and
the webui will hide this field on the 'Home' tab.
Janos
Re: Fwd: Re: [clapf-users] webui + ldap user auth backend
Clapf does not have currently write access to the directory. I plan to
use
the webui for the sole purpose for letting users traint their own part
of
Ok, however the webui creates an sqlite3 file in the users queue
directory
for faster quarantine access.
Not a problem, perfectly fine.
You can set define('PASSWORD_CHANGE_ENABLED', 0); in your config.php,
and
the webui will hide this field on the 'Home' tab.
And yes, future is here :)
Thanks!
--
Péter
XMPP, MSN: peter.laszlo.sz...@gmail.com
