Very Computer

Hi,

We always retire persons when they leave.
However no a person comes back so I want to re-enstate him.

However I when I remove *Retired from the password field en even after I
run convuser (which can sometimes also be problemtatic :) )
It still is listed as Riteried in the accountmanager GUI and the user
is'nt allowed to login also.
I even deleted that account and build it up the way it was before and
still it is retired. How can I re-enstate him???

I use Encahnced security features.

Raymond

: Hi,
:
: We always retire persons when they leave.
: However no a person comes back so I want to re-enstate him.
:
: However I when I remove *Retired from the password field en even after I
: run convuser (which can sometimes also be problemtatic :) )
: It still is listed as Riteried in the accountmanager GUI and the user
: is'nt allowed to login also.
: I even deleted that account and build it up the way it was before and
: still it is retired. How can I re-enstate him???
:
: I use Encahnced security features.

/tcb/bin/edauth user-name

Remove the "u_retired" field.  Exit the editor.  Set the password.

        Stu

I would suggest rebuilding him with a different UID ..

Quote:> Hi,

> We always retire persons when they leave.
> However no a person comes back so I want to re-enstate him.

> However I when I remove *Retired from the password field en even after I
> run convuser (which can sometimes also be problemtatic :) )
> It still is listed as Riteried in the accountmanager GUI and the user
> is'nt allowed to login also.
> I even deleted that account and build it up the way it was before and
> still it is retired. How can I re-enstate him???

> I use Encahnced security features.

> Raymond

:-)  Phooey.  *Shouldn't* do it, according to the C2 spec.  You *can*
do it, though.  The magic bit that says the account is retired is in the
C2 entry for that user.  Just use `edauth' to look through that person's entry,
and find the field that specifies it's a retired account.

        man 4 prpasswd

may help.  Now if only `userdel' could be taught to actually delete users
under C2. Even if it required you to specify an option like

 -x i_dont_care_about_c2_requirements_just_delete_them

it would still be better than the current situation.

Tim
--

Information Technology Services         (701) 231-1076 (Voice)
Room 242-J1, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164