In UD we don't have the VOC/user option so our LOGIN VOC item calls a program. This program takes the user (@logname) and determines the SB user, it then data's the user and password to SB.LOGIN. You could easily apply encryption to the passwords (they are encrypted in DMSECURITY as well).
Note, you have to watch out for phantom processes if you do this. This is also how we run an 'overnight' process. We use the NT command scheduler (or crontab) to start a phantom process which our login program deals with. hth -- Colin Alfke Calgary, Alberta Canada "Just because something isn't broken doesn't mean that you can't fix it" Stu Pickles -----Original Message----- From: Bruce Lunt [mailto:[EMAIL PROTECTED] Is there a way to do this so that MYPASSWORD is encrypted? R. Bruce Lunt >From: Dianne Ackerman <[EMAIL PROTECTED]> > >Jason Theis wrote: > >>All, >> >>We use UniVerse/NT and SB+. It seems redundant to have to login to >>UniVerse >>with a valid user and password, then choose an account, and then login to >>SB+ with a user and password. What options do we have to avoid this >>redundant entry. Is there a way to pass the user's authentication >>information to UniVerse, or the Universe information to SB+? Thanks. >> >You can put an entry in the VOC of the SB+ account for the user's name >which looks like the following: > >dianne >001 PA >002 SB.LOGIN >003 DATA DIANNE >004 DATA MYPASSWORD > >The DIANNE on line 3 is the System Builder user and the MYPASSWORD on line >4 is the user's password. > >-Dianne > -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
