User inactive option with solaris and informix
The original poster asked whether Solaris useradd -f 30 inactivity applies to users who only connect via onsoctcp. Colin Dawson said Informix only authenticates the password, not a login, so even expired passwords may work. Claus Samuelsen advised not using the informix group and using GRANT/REVOKE CONNECT. Superboer said a disabled user produces an error logged in online.log.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hi, I'm searching an opinion about user inactive option with useradd command. If I execute useradd with 30 days of inactivation option, that is "useradd -g informix -d /opt/users/userex -m -s /bin/ksh -f 30 userex" Operating System help says. User will be inactive if he/she doesn't log into system in 30 days since last log in. But my question is, is it valid when I only use onsoctcp user access? In other words, Users only log into system via tcp trough client/server INFORMIX SDK This OS option detects that user logs into system? Thanks in advance.
Informix only authenticates the password for a user it is not the same as logging into the server, I think I'm right in saying even an expired password will work. If you do "last <userid>" then connect to Informix then run the last command again it should be the same. Regards Colin There are 10 types of people in the world, those that understand binary and those that don't >From: rafapadilla@yahoo.com >To: informix-list@iiug.org >Subject: User inactive option with solaris and informix >Date: 5 May 2006 16:07:55 -0700 > >Hi, > >I'm searching an opinion about user inactive option with useradd >command. > >If I execute useradd with 30 days of inactivation option, that is >"useradd -g informix -d /opt/users/userex -m -s /bin/ksh -f 30 userex" >Operating System help says. User will be inactive if he/she doesn't log >into system in 30 days since last log in. > >But my question is, >is it valid when I only use onsoctcp user access? In other words, Users >only log into system via tcp trough client/server INFORMIX SDK >This OS option detects that user logs into system? > >Thanks in advance. > >_______________________________________________ >Informix-list mailing list >Informix-list@iiug.org >http://www.iiug.org/mailman/listinfo/informix-list _________________________________________________________________ Be the first to hear what's new at MSN - sign up to our free newsletters! http://www.msn.co.uk/newsletters
rafapadilla@yahoo.com wrote: > Hi, > > I'm searching an opinion about user inactive option with useradd > command. > > If I execute useradd with 30 days of inactivation option, that is > "useradd -g informix -d /opt/users/userex -m -s /bin/ksh -f 30 userex" > Operating System help says. User will be inactive if he/she doesn't log > into system in 30 days since last log in. Don't create users with group 'informix'. Only Informix Server administraters should have informix group. > But my question is, > is it valid when I only use onsoctcp user access? In other words, Users > only log into system via tcp trough client/server INFORMIX SDK > This OS option detects that user logs into system? Informix uses the operating system's login validation routines (userid, password) to authorize the user, but the user doesn't need to be able to login. If you want to permit/deny access to IDS you should use GRANT/REVOKE CONNECT. > > Thanks in advance. >
> Informix uses the operating system's login validation routines (userid, password) to authorize the user, but the user doesn't need to be > able to login. Yes; that means that if a user is disabled then the routines used will produce an error and the engine will puke -951 (hope the # is correct). and will put this also in the online.log file with what user is expired. check it please. Superboer.
Thank you for all your advices... I'm going to test them...