Conference utrop1::linkworks_v3

2261.0. "Users seemed to be getting disabled" by TROOA::TROTTI (VAX..more than just a vacuum cleaner) Wed May 28 1997 19:32

    Hello,
    
    We are having trouble with some Linkworks Users receiving an "Invalid
    login error" when trying to login to Linkworks.  These are NOT new
    users.  These users all have OSLOGIN set in Linkworks and we have no
    problem Logging in from a Telnet session directly into UNIX.
    
    Things we tried in order to resolve the problem.
    1. reset the password -- doesn't work
    2. move the user higher in the password file -- doesn't work
    3. reduce the number of users in the password file -- doesn't work 
    
    We have 2 workarounds that have been successful: 
    1. Remove the UNIX id and Recreate it.
    2  Modify /tcb/files/auth/w/worsini from
    
    worsini:u_name=worsini:u_id#434:\
            :u_pwd=Nologin:\
            :u_suclog#864120804:u_suctty=:u_unsuclog#864295869:u_unsuctty=:\
            :u_numunsuclog#7:u_lock@:chkent:
    
    to
    
    worsini:u_name=worsini:u_id#434:\
            :u_pwd=Nologin:\
            :u_suclog#864120804:u_suctty=:u_unsuclog#864295869:u_unsuctty=:\
            :u_lock@:chkent:
    
    However, I don't see why Linkworks is referencing this file. We are not
    using upgraded or enhanced security. Is that a problem with Linkworks
    - wrong reference to enhanced security password file - or a problem
    with passwd utility - does not reset u_numunsuclog count.
    
    Anyway, the customer does not find either of these workarounds
    acceptable any ideas what's causing the problems.
    
    UNIX 3.2
    Linkworks 3.08
    Oracle 7.1.6
    
    Regards
    Mike Trotti
    Bank of Montreal Team, Canada
    

    Mike,
    
    I think you hit a problem that has been solved in later versions of the
    PWMD. 
    LinkWorks would check the password in the wrong location if enhanced
    security has ever been enabled ( don't remember the exact text).
    I think this PWMD can be found in one of the patches directories on
    ijsapl:disk$lnx:[kits.patches.308].......
    
    
    Han

    Mike,
    
    Just found out that the patches won't help you since the fix was not
    implementes for version prior to 3.2.2.
    
    
    The problem can be bypassed by removing the security database!
    
    However this does not sound like a good idea, please send us an
    NICE/IPMT on this issue.
    
      
    Han

    Thanks Han,
    
    just submitted it today.
    
    
    Regards,
    
    Mike