Security
cancel
Showing results for 
Search instead for 
Did you mean: 

Remnant local account info causing NIS password problems

Phillip Smith_1
Occasional Visitor

Remnant local account info causing NIS password problems

I have a problem on a C2 configured environment. NIS is configured as MASTER on a 3 node cluster (5.1B PK3) and configured as CLIENT on a single node host (BBB). I have one NIS user account (which used to be local to BBB) which responds to one password on BBB and an entirely different password on the cluster members. There is most definitely no local account left on BBB. After some analysis I have found that there is
an entry in BBB's /var/tcb/files/auth.db file even though the account was deleted from the local DB. Any advise as to how to remove that entry from BBB's auth.db? Are there any other remedial steps that needs to be taken to clean up?
4 REPLIES
Mark Poeschl_2
Honored Contributor

Re: Remnant local account info causing NIS password problems

Have you tried:
# /usr/tcb/bin/edauth -d p -r
Ann Majeske
Honored Contributor

Re: Remnant local account info causing NIS password problems

Also, check out the "authck" command. You can use it to see if there are any other dangling accounts out there.
Phillip Smith_1
Occasional Visitor

Re: Remnant local account info causing NIS password problems

Mark - Spot on! It was right in front of me and I couldn't see it. Cheers.

Anne - authck verification also good advice. System checks out OK.
Phillip Smith_1
Occasional Visitor

Re: Remnant local account info causing NIS password problems

Thanks to all