Re: [cobalt-users] Passwords change by themselves?

["Steven Werby" <steven-lists@xxxxxxxxxxxx>]

Mike Johnston <mike.johnston@xxxxxxxxxx> wrote:
> Steven
>
> I am afraid that I can't completely agree with you.

I never said the *only* possible explanation was user error and I just speculated
that your fix may have been coincidental.  Obviously, you know the users and the
circumstances better than I do.  I suspect that you can completely agree with that.
<grin>

>  We have the same
> intermittent problem and all of my end users are set up with Outlook and the
> username and password are stored.  They never have to enter it.  At least
> once a week I will have a trouble call because of the password not working.
> Re-entering the password fixes it every time.  In addition it has happened
> to my own account and I a pretty sure I didn't "accidentally" change my
> password :-)

That changes everything now that I know it happened to you since you're obviously not
a technological neophyte user.  Are you the only server admin?  Could another
[disgruntled] server admin be manipulating the passwords?  Do you create user
accounts through the GUI?  If you are using Linux's "useradd" program to create users
I suppose you could be adding an expire date to the account which could be preventing
them from logging in.  Honestly, I don't know what the effects of setting the -e
option on useradd are on the RaQs, but you may want to investigate further.  "man
useradd" from the shell prompt.  If there seems to be a pattern in the length of time
b/w an account being created and the login first failing it's pretty likely.  Also,
if you're on a RaQ3 I believe the user data is stored in PostgreSQL so maybe there's
a chance there's a date field that is not being updated or resolved properly.

> I wish I could offer a fix but all I can do is reinforce that
> ti is not an end user problem.

Let us know what you find out.  If it's a bug I'm sure Cobalt will be interested so
they can patch it.  If it's something you did, I'm sure the rest of us would like to
know so we can learn from your mistake.

Steven Werby {steven-lists@xxxxxxxxxxxx}