[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference abbott::teamlinks_windows

Title:TeamLinks for Windows
Notice:Kit and ECO locations: See replies to note 8.o note 8.
Moderator:ORION::chayna.zko.dec.com::tamara::eppesAN
Created:Mon Aug 28 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2238
Total number of notes:9650

2071.0. "Another Password Cache question" by WOTVAX::HILLIS () Wed Mar 19 1997 07:57

    Hi and Thanks in Advance
    
    Teamlinks 2.7-1
    
    When using WFW password caching under Windows 95, is it possilbe to
    have the Teamlinks Setup Set Password utility, populate the Persistent
    Cache (user.pwl) so that when the user next opens up Information
    Manager they are not prompted for a password
    
    
    regards
    Andy Hillis
T.RTitleUserPersonal
Name		DateLines
2071.1It would take a programming change in TLSETUP.XANADU::cascobay.zko.dec.com::TAMARA::STJEANBob St.JeanWed Mar 19 1997 12:0414
Andy,

The Set Password function in TLSETUP actually clears all passwords
that TL has cached.  It seems like overkill, but that's what it's
been doing since V1.0.

To answer your question, I guess it could save the new password into
the cache.  Off the top of my head I can't think of any technical
reason why it couldn't do it.

Enter a suggestion PTR if you want someone to look at it.

Bob
2071.2help with pass syncWOTVAX::HILLISWed Mar 19 1997 16:1110
    Bob,
    
    Thanks for the quick reply. It just seems common sense to me, that if
    the user is using WFW cache functionality, that if they change their
    password via tlsetup, that they would  want the cache populated given a
    success message from the server. This would be a great help from a
    point of view of syncing Mailworks + NT domain passwords.
    
    
    Regards Andy
2071.3Password behaviour in memory cacheWOTVAX::HILLISMon Mar 24 1997 10:4427
    Hi I entered a PTR on the last point thanks for the suggestion.
    
    Can anyone shed some light on this behaviour also related to password
    caching (in memory this time).
    
    If I disable WFW caching in the office.ini and decide to go for a
    single teamlinks password. First I logon to InfoMan then starting
    Russell Calendar Notifier takes that password ok (without a dialogue)
    as does Calendar Notices. 
    
    Fine, if I then through Teamlinks setup set password change my
    password, exit all Teamlinks components, restart InfoMan I get prompted
    for my password as expected, however then when I start Calendar
    Notifier/Notices I also have to enter the password for them.
    
    If however after changing my password I start a Russell component first
    I enter my password as expected, and when I start InfoMan it seems to
    read the in memory cache and lets me in without a further password.
    
    Yet another scenario is, if after changing my password I simply reboot,
    then as InfoMan starts I am prompted for a password, which then the
    Russell components can seem to use !
    
    Is this expected behaviour or am I missing something obvious ?
    
    Any help greatly appreciated.
    Andy
2071.4I guess as to how something like that could happen.XANADU::cascobay.zko.dec.com::TAMARA::STJEANBob St.JeanTue Mar 25 1997 10:0912
RE: .4

It could be possible that Russell is saving the password which has
become invalid.  Then they go to use it and it doesn't work so they
recall GetConnectInfo causing Connect to effectively delete it's
good password.  At that point it has to display the Login dialog box.

The above is just a guess.  I've seen lots of strange problems 
with Russell's handling of logins and passwords.  At least that was
so in the past.

Bob