With the webpass=no option, the userdb can easily be maintained from a
central password file.
I was surprised to find recently that the userdb password is cached
somehow. Normally in the past, updating the userdb was enough for
sqwebmail to recognise the new password so long as it hadn't been
changed through the sqwebmail preferences. Now I have to remove the user
entirely and re-enter with new password.
Any suggestions on that one, without specifying webpass=no ... would be
appreciated.
Sarton
Jim Steele wrote:
>
> Maybe I'm just confused, but sqwebmail's change-password feature seems
> counter-intuitive to me. What am I misunderstanding here?
>
> I looked, and can't seem to find the text "--disable-webpass" in the
> INSTALL document. I assume it's different than "--enable-webpass=no"
> which in fairness I do see described, but it's not clear how so.
>
> Here's what I'm after.
>
> I'd really like to let the user, using the easy sqwebmail interface,
> change his/her single system-wide password, not a cached one. After
> doing so, he/she would expect, for example, to telnet into a shell
> account using the same newly changed password.
>
> It doesn't seem to work this way - after the first sqwebmail login,
> user passwords seem inextricably forked.
>
> One password per user is plenty, please. If you let users log in
> using a given authentication mechanism (e.g. authpam, mysql, etc), I'd
> expect to see functions of that same mechanism used when changing the
> password.
>
> If it already works, please explain. If not, please correct.
>
> JS
>
> On Tue, Jun 05, 2001 at 01:52:13AM +0000, Sam Varshavchik wrote:
> >
> > Use the --disable-webpass option to the configure script. See INSTALL.
> >
> > --
> > Sam
> >
